Letterpart
asked on
Sending to greylisting servers sometimes fails, delayed message appears on Exchange reboot
Hi,
we recently had to reboot our Exchange (Exchange 2003 running GFI mail Essentials) server and one of my users received a 4.7.1 Delayed message.
He also said that the recipient never received his message.
The message was:
Reporting-MTA: dns;mail.letterpart.com
Final-Recipient: rfc822;user@domain.co.uk
Action: delayed
Status: 4.7.1
Diagnostic-Code: smtp;450 4.7.1 <user@domain.co.uk>: Recipient address rejected: Greylisted for 5 minutes
Will-Retry-Until: Wed, 14 Apr 2010 12:42:44 +0100
X-Display-Name: 'user@domain.co.uk'
We have the GlitchRetrySeconds set to 0x00000078 (120 seconds)
The recipient in question is using a smarthost.
I have attached a screenshot of our Message Tracking Center which shows the message as only being sent once.
Can anyone shed any light on this please?
thanks
message-history.gif
we recently had to reboot our Exchange (Exchange 2003 running GFI mail Essentials) server and one of my users received a 4.7.1 Delayed message.
He also said that the recipient never received his message.
The message was:
Reporting-MTA: dns;mail.letterpart.com
Final-Recipient: rfc822;user@domain.co.uk
Action: delayed
Status: 4.7.1
Diagnostic-Code: smtp;450 4.7.1 <user@domain.co.uk>: Recipient address rejected: Greylisted for 5 minutes
Will-Retry-Until: Wed, 14 Apr 2010 12:42:44 +0100
X-Display-Name: 'user@domain.co.uk'
We have the GlitchRetrySeconds set to 0x00000078 (120 seconds)
The recipient in question is using a smarthost.
I have attached a screenshot of our Message Tracking Center which shows the message as only being sent once.
Can anyone shed any light on this please?
thanks
message-history.gif
ASKER
Right,
just to confuse matters I sent an email to this user before applying the hotfix so I could see if the issue was resolved and it arrived after 3 resends.
Doesn't help with my testing!
message-history-02.gif
just to confuse matters I sent an email to this user before applying the hotfix so I could see if the issue was resolved and it arrived after 3 resends.
Doesn't help with my testing!
message-history-02.gif
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm going to continue testing as this still isn't resolved 100% but I haven't had a repeat of the issue.
We may look at a smarthost but to be honest Exchange is expensive enough and it should be man enough for the job.
We may look at a smarthost but to be honest Exchange is expensive enough and it should be man enough for the job.
ASKER
I have given a C grade as it was not so much a solution but more a suggestion.
Hope you're not offended.
Hope you're not offended.
ASKER
http://support.microsoft.com/kb/950757/