You may already know that Exchange 2003 SP2 includes a new feature for SenderID support. SenderID (http://www.microsoft.com/senderid) is the e-mail authentication framework that targets one of the...
Published Oct 14, 2005
Version 1.0
Blog Post
Hello, I'm thinking on Sender ID in infrastructure based on:
Msg. Screener ->Exchange Front-end -> Exchange back-end cluster
It uses split brain DNS. Public and private. All LAN servers (also Exchange) use private DNS with forwarding option.
I can publish also public TXT records in my private DNS, and it can work I think
My own domain's TXT records are enough in private DNS.
The problem is Message Screener:-(
In such scenario I cannot use blacklists of SMTP servers on Exchange front-end, because all mails come from Msg. Screener server (private address). They have common, private IP address of sending SMTP server.
Is it possible to use Sender ID in above configuration?
Do I remove Message Screener and simply publish Exchange to work with Sender ID?
Thanks.
Msg. Screener ->Exchange Front-end -> Exchange back-end cluster
It uses split brain DNS. Public and private. All LAN servers (also Exchange) use private DNS with forwarding option.
I can publish also public TXT records in my private DNS, and it can work I think
My own domain's TXT records are enough in private DNS.
The problem is Message Screener:-(
In such scenario I cannot use blacklists of SMTP servers on Exchange front-end, because all mails come from Msg. Screener server (private address). They have common, private IP address of sending SMTP server.
Is it possible to use Sender ID in above configuration?
Do I remove Message Screener and simply publish Exchange to work with Sender ID?
Thanks.