Spam block lists for exchange 2010 and 2007
Fed up with spam.. Why not enable a block list in exhchange.
Adding the IP Block List provider to Exchange is very simple, just open up the Exchange Management Shell and run the command below:
Add-IPBlockListProvider -Name SORBIS -LookupDomain dnsbl.sorbs.net -AnyMatch $True -Enabled $True -RejectionResponse “Your IP is on the SORBS block list“
Add-IPBlockListProvider -Name SpamCop -LookupDomain bl.spamcop.net -AnyMatch $True -Enabled $True -RejectionResponse “Your IP is on the SpamCop block list“
Add-IPBlockListProvider -Name SpamHaus -LookupDomain zen.spamhaus.org -AnyMatch $True -Enabled $True -RejectionResponse “Your IP is on the spamhaus.org block list“
After you add a IP block list provider you can run get-ipblocklistprovider to list all installed. If you want to delete a provider run Remove-IPBlockListProvider -identity <name> and hit enter.
The following table lists the SMTP commands that are provided by the Microsoft Windows® SMTP service (SMTPSVC).
||Sent by a client to identify itself, usually with a domain name.
||Enables the server to identify its support for Extended Simple Mail Transfer Protocol (ESMTP) commands.
||Identifies the sender of the message; used in the form MAIL FROM:.
||Identifies the message recipients; used in the form RCPT TO:.
||Allows the client and server to switch roles and send mail in the reverse direction without having to establish a new connection.
||The ATRN (Authenticated TURN) command optionally takes one or more domains as a parameter. The ATRN command must be rejected if the session has not been authenticated.
||Provides a mechanism by which the SMTP server can indicate the maximum size message supported. Compliant servers must provide size extensions to indicate the maximum size message that can be accepted. Clients should not send messages that are larger than the size indicated by the server.
||An extension of SMTP. ETRN is sent by an SMTP server to request that another server send any e-mail messages that it has.
||Provides the ability to send a stream of commands without waiting for a response after each command.
||An ESMTP command that replaces the DATA command. So that the SMTP host does not have to continuously scan for the end of the data, this command sends a BDAT command with an argument that contains the total number of bytes in a message. The receiving server counts the bytes in the message and, when the message size equals the value sent by the BDAT command, the server assumes it has received all of the message data.
||Sent by a client to initiate the transfer of message content.
||An ESMTP command that enables delivery status notifications.
||Nullifies the entire message transaction and resets the buffer.
||Verifies that a mailbox is available for message delivery; for example,
vrfy ted verifies that a mailbox for Ted resides on the local server. This command is off by default in Exchange implementations.
||Returns a list of commands that are supported by the SMTP service.
||Terminates the session.
Extended SMTP commands
|Extended SMTP command
||A method that is used by Microsoft Exchange Server 2003 and Exchange 2000 Server servers to authenticate.
||A method that is used by Exchange 2000 and Exchange 2003 servers to authenticate.
||Provides the ability to propagate message properties during server-to-server communication.
||Adds support for link state routing in Exchange.
Ports used by Exchange
||The SMTP service uses TCP port 25.
||DNS listens on port 53. Domain controllers use this port.
||The Microsoft Exchange Routing Engine service (RESvc) listens for routing link state information on this port.
||Lightweight directory access protocol (LDAP) used by Microsoft Active Directory® directory service, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory use this port.
||LDAP over Secure Sockets Layer (SSL) uses this port.
||The Site Replication Service (SRS) uses this port.
||This is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on an Active Directory domain controller.
||Global catalog. The Windows 2000 and Windows Server 2003 Active Directory global catalog (a domain controller "role") listens on TCP port 3268.
||Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data.
||Internet Message Access Protocol (IMAP) uses this port.
||IMAP4 over SSL uses this port.
||Post Office Protocol version 3 (POP3) uses this port.
||POP3 over SSL uses this port.
||Network News Transfer Protocol (NNTP) uses this port.
||NNTP over SSL uses this port.
||HTTP uses this port.
||HTTP over SSL uses this port.