Hi,
Im trying to set up a TLS connection between my corporate exchange server (Exchange 2003) and a remote corporate mail server.
Ive followed directions on Microsofts web-site and created a separate IP address and SMTP virtual server on our exchange server *solely* for communication between us and the remote mail server.
However, when we send mail to the remote domain, it is immediately bounced back with the following error:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator. <ms1.abc.com #5.3.5>
Ive googled this error and the closest thing that resembles a possible fix is this article from computerworld:
http://www.computerworld.com.au/index.php/id;1808495145;pp;10;fp;2;fpid;37in the article, the author states the following:
[Lets say that your] domain, test.com, has two Virtual SMTP Servers one is called default-test and has IP address 192.168.2.1 the other is called secure-tls-test and has the IP address 192.168.2.2.
You try to send an encrypted e-mail to a remote SMTP server called remote-tls-server.com. The TLS message will be sent from your secure-tls-test Virtual SMTP Server.
It will start the STARTTLS service on remote-tls-server.com which in turn will send the negotiation request back to a default virtual server for your domain based on the MX record.
So if the MX record for your domain test.com points to 192.168.2.1, the TLS negotiation will fail because the acknowledgment was sent to a wrong server. It was sent to an IP address of the server that did not initiate TLS negotiations.
This all makes sense, but the article doesnt explain how to *fix* the issue.
i.e. how do I get the response negotiation request to go back to the newly created TLS-specific SMTP virtual server?
Any ideas?
TIA!
Start Free Trial
