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.allianzco
Received-From-MTA: dns;S01CMP03EXCH.allianzco
Arrival-Date: Wed, 1 Sep 2010 14:15:56 +0100
Final-Recipient: rfc822;leah.usher@nahl.co.
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100
Final-Recipient: rfc822;steve.walpole@nahl.
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100
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.allianzco
Received-From-MTA: dns;S01CMP03EXCH.allianzco
Arrival-Date: Wed, 1 Sep 2010 14:15:56 +0100
Final-Recipient: rfc822;leah.usher@nahl.co.
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100
Final-Recipient: rfc822;steve.walpole@nahl.
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 3 Sep 2010 14:15:56 +0100
The email is delayed because rfc822 is not a valid email.
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?
Maybe you have their company or even country blacklisted?
Can they get ANY email to you?
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.
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.
ASKER
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?
It appears that the sender has succesfully sent messages to users on my domain before, its just this random time?
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.
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.
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.
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.
ASKER
Yes pbeire, they can send to single users on the domain. I think its when there are multiple users that this message happens
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.