Solved

SMTP call-ahead for recipient validation

Posted on 2014-02-12
2
2,291 Views
Last Modified: 2014-02-21
We have two Cisco IronPort C360 appliances doing antispam and antivirus filtering before mail makes its way into Exchange. These have not been in a DMZ, and we're now making the effort to move these into a DMZ.

We use our corporate AD servers for LDAP recipient validation (so that invalid recipients are dropped). We were planning to move an LDAP server into the DMZ with the appliances, with email addresses pushed to it from production, for recipient validation. *BUT* I came across SMTP call-ahead, which seems like it would suit our needs better since we wouldn't need a dedicated LDAP server and our architecture would be more secure...

IronPort would open an SMTP session to Exchange to verify the recipient. Exchange hub servers don't do this out of the box, antispam agents need to be installed. This fellow has a good guide: This fellow has a good guide: http://www.jjclements.co.uk/2010/09/23/exchange-2010-recipient-filtering-on-a-hub-transport-server/

I'm wondering if what we're doing is a terrible idea. Does anyone have any experience with SMTP call-ahead? I would appreciate any thoughts, validation, or feedback.
0
Comment
Question by:msghydron
2 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39854028
I enable recipient filtering on all servers that I deploy and it is something I think should be on all email servers.
The problem you will have is that Exchange has tarpit enabled by default, which can cause email delivery days. It will depend on whether the appliances are able to cache the results or not (I haven't used them myself, so don't know). If they are able to cache results then it shouldn't be a problem, as they will only have the tarpit delay the first time they connect. However if they are doing it "live" each time, then you may well have to reconfigure Exchange to remove the tarpit.

Simon.
0
 

Author Closing Comment

by:msghydron
ID: 39878382
We are proceeding with SMTP call-ahead on the IronPort C360 appliances, switching from LDAP recipient validation. We've removed the 5-second tarpit delay. I think this is a better configuration, when the C360's are in a DMZ.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you thought ransomware was bad, think again! Doxware has the potential to be even more damaging.
It’s the first day of March, the weather is starting to warm up and the excitement of the upcoming St. Patrick’s Day holiday can be felt throughout the world.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question