[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 781
  • Last Modified:

Exchange Server - 4.4.7 - Error Code

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
Smartin
Asked:
Smartin
  • 3
  • 2
  • 2
  • +2
1 Solution
 
nettek0300Commented:
The email is delayed because rfc822 is not a valid email.
0
 
FDiskWizardCommented:
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
 
pbeirneCommented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
FDiskWizardCommented:
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
 
SmartinAuthor Commented:
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
 
chakrikollaCommented:
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
 
chakrikollaCommented:
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
 
pbeirneCommented:
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
 
SmartinAuthor Commented:
Yes pbeire, they can send to single users on the domain. I think its when there are multiple users that this message happens
0
 
SmartinAuthor Commented:
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

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!

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now