Exchange 2010 Edge Transport Server: Configuring IP Block List Providers

The Exchange Server 2010 Edge Transport server role is automatically enabled for the built-in anti-spam features when it is installed. However some of the features require configuration before they can begin blocking spam.

The IP Block List Providers anti-spam feature is one example. It is enabled by default, but no block list providers are included in the configuration.

IP block list providers are an effective way to block the majority of spam, because they maintain comprehensive databases of IP addresses on the internet that are known and suspected spam sources. This allows an Exchange server to determine whether or not to block an incoming email during the initial stages of the SMTP connection, based on the IP address of the sending host.

Blocking spam at such an early stage of the communication sequence uses less bandwidth and processor resources than email content filtering, because the full email message is never transmitted to the Exchange server.

One of the best IP block list providers is Spamhaus. You can configure an Edge Transport server to use Spamhaus as an IP block list provider by following these steps.

Log on to your Edge Transport server and launch the Exchange Management Console. In the Anti-spam tab right-click IP Block List Providers and select Properties.

Select the Providers tab and then click Add.

Enter the Provider Name of Spamhaus and the Lookup Domain of zen.spamhaus.org.

Click OK and OK again to apply the change.

The Edge Transport server will now lookup the IP address of connecting hosts to determine whether or not to accept mail from them.

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. would you recommend always putting this on the edge server or is it just as fine on the cas and hib server etc as seen here

    • It can go on either, whichever one is receiving internet mail for your org. If you’re putting it on a Hub Transport you’ll need to install the antispam agents first using the script Microsoft supplies.

  2. Bill Driver says:

    Is there a cost associated with using Spamhaus in this configuration?

  3. Hi Paul,
    After the configuration of Spamhaus on our Edge Server, all incoming mail traffic was blocked and all the senders received an undeliverable message from our server…

    Franco

  4. Jirik Haselgrove says:

    Hi Paul,

    Just pondering whether it is possible to set a condition or process up that automatically removes values from a block list a certain time after creating, either through automatically settiong an expiry value, or through automatic deletion.

    Cheers,

    Jirik

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.
Loading...

Still running Exchange 2003? Time to get moving and start your upgrade. Find out how - Click Here