Exchange 2013, Recipient Validation. CAS/MBX ROle.

Hey Team,

I realize that enabling recipient validation on a mailbox server / CAS server (multirole) causes any invalid recipient to block the whole message and pretty much make recipient validation useless for exchange 2013 unless an edge server is used.

Here is my question:

We are using mcafee saas but for a few different reasons we are not able to get LDAP/S working correctly (original plan) so we are not able to use Mcafees recipient validation, the idea then was to use Exchange's recipient validation but of course there is the known issue of it not working correctly.

Can I just have Mcafee SaaS send all email traffic to port 2525 and bypass the "CAS Server's port 25" completely?

This link here: Is where I got the bright idea from: https://helpdesk.spamtitan.com/support/solutions/articles/4000003763-dynamic-recipient-verification-using-exchange-2013

Thanks,

R

August 27th, 2015 8:04pm

Maybe you should ask a question in Mcafee SaaS forum. In Microsoft, I find this article:

https://technet.microsoft.com/en-us/library/Bb125187(v=EXCHG.150).aspx

The recipient filtering is used on Edge server to filter inbound messages that come from the Internet but aren't authenticated. Since you are using a third-party produce for Recipient Validation, ask a question in Mcafee SaaS forum for better solution.

Free Windows Admin Tool Kit Click here and download it now
August 31st, 2015 10:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics