Well isn't that funny, I just did the same thing, we were getting intermittent 550 saying they didn't recognize our computer as connecting from an EarthLink connection. The problem was just brought to my attention yesterday, after I made the change this morning it worked correctly. Any further insight is greatly appreciated. Thanks
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pascoe, Rick Posted At: Thursday, August 05, 2004 4:11 PM Posted To: Exchange-List Conversation: Fixed? - RE: 550 Relaying prohibited to Earthlink Subject: Fixed? - RE: 550 Relaying prohibited to Earthlink This only seems to occur on upgraded E2K3 and I'm not sure if this is a fix or a poor work around since it seems to indicate something's wrong with my internal DNS but to fix this, I went in to the SMTP virtual server and added our external DNS servers into the configure DNS servers for this server. Is this something normally done in E2K3 or is this something normally recommended not doing (can it create a security issue)? Rick Pascoe St. Anne School 949/487-2663 x232 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Brandt Sent: Wednesday, August 04, 2004 1:22 PM To: Exchange Discussions Subject: 550 Relaying prohibited to Earthlink Hi Everyone, Some of our users have been having trouble sending messages to the earthlink domain. I contacted them and they replied that it could be an incorrect configuration in my MTA: " the mailserver which attempted to deliver mail to the earthlink.net e-mail address was initially unable to successfully deliver the mail to the earthlink.net MX (more than likely due to high load on our end; no EarthLink MX host was available to accept the transaction at the moment of the delivery attempt), and so the EarthLink 'A' record was attempted by the sending mailserver. The earthlink.net 'A' record, however, forwards port 25 connections to our outbound SMTP servers. Unless the mailserver attempting the transaction maintains IP connectivity through the EarthLink network, delivery attempts through the 'A' record will consequently fail. The behavior exhibited by the sending mailserver, in this case, is 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." Currently the EarthLink.net mx record resolves as follows: mx4.earthlink.net mx5.earthlink.net mx6.earthlink.net mx7.earthlink.net mx8.earthlink.net mx9.earthlink.net mxa.earthlink.net mxb.earthlink.net mxc.earthlink.net mxd.earthlink.net mxe.earthlink.net mx1.earthlink.net mx2.earthlink.net mx3.earthlink.net You may wish to verify that you are able to successfully resolve this record through your nameservers, and that you can successfully route to these hosts. Assuming that the earthlink.net MX is resolvable, however, our engineers have informed us that if the sending mailserver cannot immediately establish a connection to deliver the intended e-mail, the MTA should attempt to retry a connection to the EarthLink MX, rather than defaulting to the earthlink.net 'A' record or smtp.earthlink.net." I can succesfully resolve these records through my nameserver, so my question is what on my MTA would be incorrectly configured? Thanks in advance for the help!! Sean ~~~~~~~~~~~~~~~~~~~~~~ Sean Brandt, MCSE US Network Manager Lonely Planet Publications, USA tel: 510.893.8556 x217 mobile: 510.541.2601 [EMAIL PROTECTED] *********************************************************************** This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not use, copy or disclose its content to anyone. You must not copy or communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
