gws226
asked on
Delivery to the following recipients has been delayed
Hi Experts,
It appears Bellsouth.net (aka Att.net) has made some further adjustments to their mail security that are causing more a few of my clients to have mail bounceback issues. These are not new installs, One exchange server has been up for 4 years with no changes of note.
We are not receiving a specific error message in return to help obtain the exact issue. Currently the affected clients are all on Exchange 2003, REV DNS is configured, No special firewall router/spam filtering.
Error message is as follows
Delivery to the following recipients has been delayed
Reporting-MTA: dns;mycompany.com
Final-Recipient: accountID ;username@bellsouth.net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 7 Feb 2008 10:35:36 -0500
X-Display-Name: User Name(lusername@bellsouth.n et)
It appears Bellsouth.net (aka Att.net) has made some further adjustments to their mail security that are causing more a few of my clients to have mail bounceback issues. These are not new installs, One exchange server has been up for 4 years with no changes of note.
We are not receiving a specific error message in return to help obtain the exact issue. Currently the affected clients are all on Exchange 2003, REV DNS is configured, No special firewall router/spam filtering.
Error message is as follows
Delivery to the following recipients has been delayed
Reporting-MTA: dns;mycompany.com
Final-Recipient: accountID ;username@bellsouth.net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 7 Feb 2008 10:35:36 -0500
X-Display-Name: User Name(lusername@bellsouth.n
Hmm, have you tried flushing your DNS on your mailservers and trying again - perhaps a stale record with a long TTL is causing issues? Bit of a long shot, but stranger things have happened!
ASKER
Let me also add, that I can ping bellsouths mail servers (mail.bellsouth.net) but I cannot telnet to it.... Actually I can no longer telnet to them from ANY of my client networks.
Here is my record tests
Banner: mycompany.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 6 Feb 2008 10:43:54 -0500 [47 ms]
Connect Time: 0.047 seconds - Good
Transaction Time: 10.421 seconds - Not good!
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 33.33.33.34 resolves to mail.mycompany.com
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO mxtoolbox.com - DIAGNOSTIC TEST - See http://www.mxtoolbox.com/Policy.aspx
501 5.5.4 Invalid Address [5078 ms]
HELO mxtoolbox.com
250 mycompany.com Hello [64.20.227.131] [78 ms]
MAIL FROM: <test@mxtoolbox.com>
250 2.1.0 test@mxtoolbox.com....Send er OK [47 ms]
RCPT TO: <test@mxtoolbox.com>
550 5.7.1 Unable to relay for test@mxtoolbox.com [5078 ms]
QUIT
221 2.0.0 mycompany.com Service closing transmission channel [47 ms]
Here is my record tests
Banner: mycompany.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 6 Feb 2008 10:43:54 -0500 [47 ms]
Connect Time: 0.047 seconds - Good
Transaction Time: 10.421 seconds - Not good!
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - 33.33.33.34 resolves to mail.mycompany.com
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO mxtoolbox.com - DIAGNOSTIC TEST - See http://www.mxtoolbox.com/Policy.aspx
501 5.5.4 Invalid Address [5078 ms]
HELO mxtoolbox.com
250 mycompany.com Hello [64.20.227.131] [78 ms]
MAIL FROM: <test@mxtoolbox.com>
250 2.1.0 test@mxtoolbox.com....Send
RCPT TO: <test@mxtoolbox.com>
550 5.7.1 Unable to relay for test@mxtoolbox.com [5078 ms]
QUIT
221 2.0.0 mycompany.com Service closing transmission channel [47 ms]
Hmm, sounds like they are actively blocking your IP range. Have you tried phoning there support and enquiring? Is your mail server sending RFC compliant commads?
ASKER
That was a guess as well. I tried telneting to mail.bellsouth.net over 5 different networks... all with the same result. There is no traffic warning, I've already gone ahead a petitioned for IP reinstatement, but wouldn't I expect a 5.5.x fail if it was an IP block?
Not necessarily, 4.4.7 is just it giving up - and remember, who said the block was on the the host? It could be on their border devices.
The 5 different networks, are they on different netblocks?
The 5 different networks, are they on different netblocks?
ASKER
All unique.... even picked a few different ISPs, nuvox, paetech, TimeWarner etc etc
I'm having the exact same problem with a client not being able to send mail to a bellsouth.net (At&T) account. Have you been able to determine a fix for this? I cannot get AT&T to respond to my email.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.