Delivery to the following recipients has been delayed

Hi Experts,

It appears (aka  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;

Final-Recipient: accountID ;
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 7 Feb 2008 10:35:36 -0500
X-Display-Name: User Name(
Who is Participating?
easyworksConnect With a Mentor Commented:
Bellsouth might have blocked you from sending mail to them (You can send mail to other people and just not bellsouth accounts right?).  If you fill out this form  (starts at  in about 2 days they send you an email saying they have unblocked you.  This has happened to several different companies we work with and this has been the fix for us, but it is still unknown to us why this just all of a sudden is happening to everyone.
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!
gws226Author Commented:
Let me also add, that I can ping bellsouths mail servers ( 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: 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 - resolves to
GeoCode Info: Geocoding server is unavailable
Session Transcript: HELO - DIAGNOSTIC TEST - See 
501 5.5.4 Invalid Address [5078 ms]
250 Hello [] [78 ms]
250 2.1.0 OK [47 ms]
550 5.7.1 Unable to relay for [5078 ms]
221 2.0.0 Service closing transmission channel [47 ms]
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

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?
gws226Author Commented:
That was a guess as well.  I tried telneting to 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?
gws226Author Commented:
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 (At&T) account.  Have you been able to determine a fix for this?  I cannot get AT&T to respond to my email.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.