WinDeveloper IMF Tune
WinDeveloper IMF Tune
  • Home
  • Anti-Spam
  • Connection Filtering IP Accept List in Exchange SP2

Connection Filtering IP Accept List in Exchange SP2

Alexander Zammit [MVP - MS Exchange]

Alexander Zammit [MVP - MS Exchange] Photo

Alexander Zammit is an MS Exchange MVP. He has been developing server applications for over 10 years. Most of his works involve Exchange integrated applications, including a FAX server, a mail security product and two anti-spam products.

  • Published: Jan 24, 2006
  • Category: Anti-Spam
  • Votes: 4.8 out of 5 - 6 Votes
Cast your Vote
Poor Excellent

Getting the Connection Filtering IP Accept List to work became trickier since Exchange SP2. IPs configured to bypass the Intelligent Message Filter, sometimes have no effect. Luckily the solution is around the corner.

Accept List Configuration

Finally, for those discovering IP Accept lists for the fist time, here is a configuration walkthrough.

  1. From the Exchange System Manager open the properties for Global Settings | Message Delivery.

  2. Select the Connection Filtering property page.

    Connection Filtering Properties

  3. Click on the Accept button

    IP Accept List

  4. Click on the Add button to specify the IPs for hosts whose emails are to be accepted without further Connection Filtering or IMF processing.

  5. Save and close all dialogs.

Next enable Connection Filtering at each SMTP Virtual server where the Accept list is to be enforced:

  1. Browse the left pane tree and open the properties for:
    <Organization> | Servers | <Exchange Server> | Protocols | SMTP | <SMTP Virtual Server>

  2. From the General property sheet click on Advanced.

    SMTP Virtual Server Properties

  3. In the Advanced dialog that opens select the IP on which Connection Filtering is to be enabled and click on the Edit button.

    Advanced Dialog

  4. Set the 'Apply Connection Filter' checkbox.

    Apply Connection Filter

  5. Save changes.

User Comments - Page 1 of 1

Add New Comment...

Alexander Zammit 2 Jul 2009 02:52
The solutions I know of, are listed in the article.

That list should only include the hosts that are involved in the routing of internet email to the first Exchange Server in your organization.

Normally you will only have very few machines involved in this routing and only those should be listed.
SimonG 2 Jul 2009 02:12
Thanks for this article - it's certainly allowed me to understand why our internal devices are being processed by the IMF and hence categorised as potential spam.
In the article you mention that the 'trivial solution' to solving this issue is by ensuring the device IP's are not inserted in the local IP list - our list contains a subnet which contains the IP's of these devices - how do we handle this?
Copyright © 2009 All rights reserved. ExchangeInbox.com is not affiliated with Microsoft Corporation