I believe this article addresses the questions you have. Depending on the configuration of the connector Exchange will resolve or not resolve the sender address.
http://technet.microsoft.com/en-us/library/bb232021.aspx Thanks, Peter Dahl. From: Campbell, Rob [mailto:[email protected]] Sent: Tuesday, October 20, 2009 12:31 PM To: MS-Exchange Admin Issues Subject: RE: SMTP oddities with Exchange 2007 I'm not sure if I'm following all that exactly, but it sounds like you should be able to create a new receive connector that you can test (via telnet, PS script, etc) from one of your existing application servers by adding an additional IP address to the Exchange server, and binding the new receive connector to just that IP address. From: Doug Gallimore [mailto:[email protected]] Sent: Tuesday, October 20, 2009 11:21 AM To: MS-Exchange Admin Issues Subject: SMTP oddities with Exchange 2007 I have this weird issue with email sent from application boxes through the SMTP relay in a receive connector I setup with 2k7. The sending address is an alias/proxy address on a public folder. When the mail is received, the "from" address is "resolved" if you will to the public folder name, and not the proxy address, unless you view the header. Apparently, a bunch of folks used to have rules that processed the messages based on the from address, and another application automatically creates tickets based on the from address, and it can't examine the header. If I do a manual SMTP message through the hub server, I get the correct from, but the to, is blanked. If I include the To:/From: in the DATA portion of the SMTP message it's all good, however, if I use the same test from telnet on one of the application servers, the from address gets "resolved" again. I think it's a setting in my receive connector that is doing this, but I've no idea which one, my connector is pretty open to lots of internal application servers (mostly monitoring applications) which I have little control over. So I was just going to create a new receive connector and lock it down to just one auth and one permissions group until I find it, but I'm having trouble isolating a test application server that isn't "critical". Any suggestions? Douglas ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **************************************************************************************************
