
Re: Re: Changing name on mailbox
I experienced this problem as well. My client's Exchange 2003 server could send email to every other mail server that was tried except for Earthlink and Mindspring accounts (which are basically the same company from what I understand).
For some reason a default Exchange 2003 install using the Windows DNS ends up attempting to send to the EarthLink 'A' record. The earthlink.net 'A' record, however, forwards port 25 connections to their outbound SMTP servers which only allow earthlink connected customers to relay email. Thus, the error message is received.
Something about the Exchange 2003 and Windows DNS setup is different than it was in the 2000 version as I have never experienced this with well over 75 other Exchange 2000 installs.
This behavior is also not standard. According to RFC 2821, "Address Resolution and Mail Handling":
"If one or more MX RRs are found for a given name, SMTP systems MUST NOT utilize any A RRs associated with that name unless they are located using the MX RRs; the "implicit MX" rule above applies only if there are no MX records present. If MX records are present, but none of them are usable, this situation MUST be reported as an error."
While setting up a smart host can resolve the problem (it worked for me as a temporary measure) I would assume most companies may not have a smart host that will relay email for them.
You may find this to be a better solution.
Open the properties of the SMTP virtual server. Click the Delivery tab, click Advanced, and then click Configure to configure external DNS servers. Specify the address of one or more DNS servers with external name resolution. Then the Exchange server will query the specified DNS servers to route outbound mail through this SMTP virtual server.
Using external DNS servers for the Exchange server will avoid the problems with the internal Windows DNS and should completely resolve the problem. I wouldn’t be surprised to see a fix for this in a future service pack.