Link to home
Start Free TrialLog in
Avatar of tdantona
tdantonaFlag for United States of America

asked on

Action: failed...Remote-MTA: DNS; sdamail.amerysd.k12.wi.us

Looking for a meaningful diagnosis (translation) of this failure. We are having similar failures with a few domains. Here is the extended failure info..I have put xxx in place of personal email info to protect the users privacy:

The original message was received at Thu, 05 Dec 2002 21:17:36 -0600

  ----- The following addresses had permanent fatal errors -----
<xxxxxxxx@amerysd.k12.wi.us>

  ----- Transcript of session follows -----
... while talking to sdamail.amerysd.k12.wi.us
<<< 501 RDNS failure
... connection error: connection reset by peer/timeout

THE DAT FILE RETURNED WITH THE FAILURE CONTAINED THE FOLLOWING:

Reporting-MTA: dns; mail.AvalonHelpDesk.com
Arrival-Date: Thu, 05 Dec 2002 21:17:26 -0600

Final-Recipient: RFC822; <xxxxxxx@amerysd.k12.wi.us>
Action: failed
Remote-MTA: DNS; sdamail.amerysd.k12.wi.us
Last-Attempt-Date: Thu, 05 Dec 2002 21:17:37 -0600
ASKER CERTIFIED SOLUTION
Avatar of Jamie McKillop
Jamie McKillop
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tversi
tversi

change the helo domain of your mailserver to what it should be, for instance, if your domain is yourdomain.com and your mx record is mail.yourdomain.com then enter mail.yourdomain.com as your helo domain. Some mailservers look up your domain (reverse lookup) and will mismatch your inforamtion, consider its not from the right place and reject the connection. What mailserver are you using?
Godd Luck.
as well as jjmck's there is a registry key which you can set which sends a copy of the FQDN along with the message which prevents the requirement for the RDNS lookup.

Need to know the version of email your exchange to give correct reg key.
Avatar of tdantona

ASKER

Looks like SPRINT had screwed up the reverse DNS and we were not being properly ID'd on RDNS lookup. Much better now, thanks.

Tom