netcomp
asked on
Exchange NDR in outlook (#4.0.0 smtp;451 and lrschumann@mmcanby.com)
One of my users ( CEO) has informed me that he got 4 bounced emails from system administrator in his outlook. 3 of the bounced email are to the same domain but the forth one is to a diffrent user. The bad part is that all the emails were sent about 3 or 4 weeks ago ( diffrent dates), but it took this long to get the bounced back error email.
Your message did not reach some or all of the intended recipients.
Subject: Attn: - limestone replacement
Sent: 1/30/2009 10:27 AM
The following recipient(s) could not be reached:
recipient3@recipient2.edu on 2/18/2009 7:10 PM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient3@recipient2.edu
Your message did not reach some or all of the intended recipients.
Subject: Attn: Ann bylie H. Smith
Sent: 1/22/2009 1:57 PM
The following recipient(s) could not be reached:
recipient2@recipientdomain
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient2@recipientdomai
Your message did not reach some or all of the intended recipients.
Subject: retirement agreement
Sent: 2/14/2009 11:03 AM
The following recipient(s) could not be reached:
recipient@recipient.com on 2/18/2009 7:10 PM
The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator.
<ourdomain.com #4.2.0 smtp;450 4.2.0 <recipient1@recipientdomai
Your message did not reach some or all of the intended recipients.
Subject: Attn: - limestone replacement
Sent: 1/30/2009 10:27 AM
The following recipient(s) could not be reached:
recipient3@recipient2.edu on 2/18/2009 7:10 PM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient3@recipient2.edu
Your message did not reach some or all of the intended recipients.
Subject: Attn: Ann bylie H. Smith
Sent: 1/22/2009 1:57 PM
The following recipient(s) could not be reached:
recipient2@recipientdomain
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient2@recipientdomai
Your message did not reach some or all of the intended recipients.
Subject: retirement agreement
Sent: 2/14/2009 11:03 AM
The following recipient(s) could not be reached:
recipient@recipient.com on 2/18/2009 7:10 PM
The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator.
<ourdomain.com #4.2.0 smtp;450 4.2.0 <recipient1@recipientdomai
Your message did not reach some or all of the intended recipients.
Subject: Attn: - limestone replacement
Sent: 1/30/2009 10:27 AM
The following recipient(s) could not be reached:
recipient3@recipient2.edu on 2/18/2009 7:10 PM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient3@recipient2.edu>... Requested mail action not taken: mailbox unavailable>
Your message did not reach some or all of the intended recipients.
Subject: Attn: Ann bylie H. Smith
Sent: 1/22/2009 1:57 PM
The following recipient(s) could not be reached:
recipient2@recipientdomain2.edu on 2/18/2009 7:10 PM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<ourdomain.com #4.0.0 smtp;451 <recipient2@recipientdomain2>... Requested mail action not taken: mailbox unavailable>
Your message did not reach some or all of the intended recipients.
Subject: retirement agreement
Sent: 2/14/2009 11:03 AM
The following recipient(s) could not be reached:
recipient@recipient.com on 2/18/2009 7:10 PM
The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator.
<ourdomain.com #4.2.0 smtp;450 4.2.0 <recipient1@recipientdomain1.com>: Recipient address rejected: The Postgrey server on this AutumnTECH E-mail Messaging Security Appliance says there is 2 seconds left before you can send e-mail to mmcanby.com>
ASKER
Will this happened another time when I rebooted the server about a month ago with another user, but I had not rebooted the server the past few weeks.
More important, Can you tell whey those emails were rejected the first place, or not gone out based on the NDR???????????????? My boss wants the answer asap :-),,,,,,,,,,
More important, Can you tell whey those emails were rejected the first place, or not gone out based on the NDR???????????????? My boss wants the answer asap :-),,,,,,,,,,
The NDR says why the message was rejected, the mailbox wasn't available.
However the error codes are 4.x.x which is temporary failure, usually that means greylisting, but the error doesn't say that. That isn't to say it WASN'T greylisting, but I would expect a site using greylisting to say.
Greylisting is antispam measure, which is usually pretty effective. It is just unfortunate that some implementations of greylisting cause Exchange to react in a negative way. I had hoped that Microsoft would push the hotfix out in automatic updates, but it wasn't to be.
-M
However the error codes are 4.x.x which is temporary failure, usually that means greylisting, but the error doesn't say that. That isn't to say it WASN'T greylisting, but I would expect a site using greylisting to say.
Greylisting is antispam measure, which is usually pretty effective. It is just unfortunate that some implementations of greylisting cause Exchange to react in a negative way. I had hoped that Microsoft would push the hotfix out in automatic updates, but it wasn't to be.
-M
ASKER
Should I contactthe recepient IT team and ask them to white list us. Are you saying that the update will let them get our emails.
ASKER
O My God Simon lives. I thank God, I thought you had left or you just hated me and did not want to respond to my questions in E.E. You have no idea how happy I am. I started having trust issues in EE after I did not see you around. LOL
It depends on whether the recipient is using greylisting or not. If they are not then it may well have been a temporary failure. Not all errors are down to antispam measures.
Yes I do live.
-M
Yes I do live.
-M
ASKER
Mestha,
I installed the patch from microsoft. So, do we need to somehow contact the recepients and ask them to put us in their white list now. I am not still sure if this solves the problems of the emails bouncing back or does this only fix the issue of getting the messages back after a month.??
I installed the patch from microsoft. So, do we need to somehow contact the recepients and ask them to put us in their white list now. I am not still sure if this solves the problems of the emails bouncing back or does this only fix the issue of getting the messages back after a month.??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If so, sounds like the greylisting bug.
http://support.microsoft.com/kb/950757/
-M