Solved

Exchange Server - 4.4.7 - Error Code

Posted on 2010-09-03
10
744 Views
Last Modified: 2012-05-10
Exchange Server 2007

Please can someone explain the below error code to me. An external party has been trying to send an email to some of my users but they get the below 4.4.7 - Error Code.

I beleive it to be that the number of hops the message has to take is greater than the number of hops set on the external partys emaill server??

Thanks


Reporting-MTA: dns;s01map03exch.allianzcornhill.co.uk
Received-From-MTA: dns;S01CMP03EXCH.allianzcornhill.co.uk
Arrival-Date: Wed, 1 Sep 2010 14:15:56 +0100

Final-Recipient: rfc822;leah.usher@nahl.co.uk
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100

Final-Recipient: rfc822;steve.walpole@nahl.co.uk
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100
0
Comment
Question by:Smartin
  • 3
  • 2
  • 2
  • +2
10 Comments
 
LVL 6

Expert Comment

by:nettek0300
ID: 33597326
The email is delayed because rfc822 is not a valid email.
0
 
LVL 12

Expert Comment

by:FDiskWizard
ID: 33597342
A delayed error can mean several things. check to make sure you aren't dropping/blocking their emails on your SPAM filter. If it is just dropped without an NDR it may cause the delayed error.
Maybe you have their company or even country blacklisted?
Can they get ANY email to you?
0
 
LVL 5

Expert Comment

by:pbeirne
ID: 33597410
This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly.
0
 
LVL 12

Expert Comment

by:FDiskWizard
ID: 33597441
If I'm not mistaken the RFC822 is just saying that it is being recognized as a proper RFC822 formatted email address. That doesn't appear to be the error, just info.
0
 

Author Comment

by:Smartin
ID: 33597648
That RFC822 seems to appear after all those email address? So is it nothing to do with the number of hopes the message is trying to take to my exchange server?

It appears that the sender has succesfully sent messages to users on my domain before, its just this random time?
0
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 

Expert Comment

by:chakrikolla
ID: 33597945
This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly.
0
 

Expert Comment

by:chakrikolla
ID: 33597947
This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly.
0
 
LVL 5

Expert Comment

by:pbeirne
ID: 33599201
Unfortunately the error is somewhat generic.  Since you receive most other mail as far as you know, it probably does not have to do with the number of hops to your server. It indicates that it is timing out for some reason.  What that reason is, however is the answer you are looking for.  The delay could occur at your mail server, your spam appliance, somewhere on the internet.  

Can this sender send mail to ANYONE in your domain.  Have them try sending to just a single user instead of multiple users at once.
0
 

Author Comment

by:Smartin
ID: 33611880
Yes pbeire, they can send to single users on the domain. I think its when there are multiple users that this message happens
0
 

Accepted Solution

by:
Smartin earned 0 total points
ID: 33671268
The error can also be caused by having too many recipients in the header.

This is from Microsoft’s Knowledgebase

Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This NDR may also indicate that a message header limit has been reached on a remote server or that some other protocol timeout occurred during communication with the remote server.
Troubleshooting: This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly. You may have to reduce the number of recipients in the header of the message for the host that you are receiving this NDR from. If you resend the message, it is placed in the queue again. If the receiving server is on line, the message is delivered.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now