Unsent emails after 4xx response
- Windows Server 2003 and Exchange Server 2003We are having a strange problem with email server.Once a month a newsletter is sent. This newsletter is sent to aprox. 900 addresses in BCC.Until the newsletter is sent, the serve runs normally, all emails go out as expected.After the newsletter is sent, all emails for which the remote server gets a 4xx response, the emails never gets sent, and the emails vanish, i.e. they are not in the queues.Here is an example of the log:10:25:15 89.109.64.193 OutboundConnectionResponse - 25 - - 220+mail.madeiratecnopolo.pt+Microsoft+ESMTP+MAIL+Service,+Version:+5.0.2195.6713+ready+at++Wed,+9+May+2007+11:25:15++0100+ 0 0 123 0 16 SMTP 10:25:15 89.109.64.193 OutboundConnectionCommand - 25 EHLO - mail.newmadeira.com 0 0 4 0 16 SMTP 10:25:15 89.109.64.193 OutboundConnectionResponse - 25 - - 250-mail.madeiratecnopolo.pt+Hello+[213.190.197.7] 0 0 50 0 31 SMTP 10:25:15 89.109.64.193 OutboundConnectionCommand - 25 MAIL - FROM:<from-add@newmadeira.com>+SIZE=2168 0 0 4 0 47 SMTP 10:25:15 89.109.64.193 OutboundConnectionResponse - 25 - - 250+2.1.0+from-add@newmadeira.com....Sender+OK 0 0 53 0 62 SMTP 10:25:15 89.109.64.193 OutboundConnectionCommand - 25 RCPT - TO:<to-add@madeiratecnopolo.pt> 0 0 4 0 62 SMTP 10:26:05 89.109.64.193 OutboundConnectionResponse - 25 - - 451+4.7.1+Temporarily+rejected.+Try+again+later. 0 0 48 0 50094 SMTP 10:26:05 89.109.64.193 OutboundConnectionCommand - 25 RSET - - 0 0 4 0 50094 SMTP 10:26:05 89.109.64.193 OutboundConnectionResponse - 25 - - 250+2.0.0+Resetting 0 0 19 0 50141 SMTP 10:26:05 89.109.64.193 OutboundConnectionCommand - 25 QUIT - - 0 0 4 0 50141 SMTP 10:26:05 89.109.64.193 OutboundConnectionResponse - 25 - - 221+2.0.0+mail.madeiratecnopolo.pt+Service+closing+transmission+channel 0 0 71 0 50141 SMTPAnd no other log is detected for this particular email, i.e no retrys are ever done.If I just restart the SMPT service, all missing emails (about 50 where missing) start getting sent out, and the server goes back to running normally.This behavior happens every month when the newsletter is sent. Can anybody help me?
May 10th, 2007 2:49pm

Hi! I have seen this problem with alot of customers that use Exchange (2003 SP2) to send emails directly to hosts with greylisting implemented. In all cases no modifications have been done to the smtp-server (for example glitchretryseconds that some lists recommend). The most worrying is as you say no retrys, no mails in outgoing queue and no NDR sent back to the sender, until you restart server/smtp-service. The only thing I have been able to do to resolve thoose problems is to smarthost all outgoing mails through a sendmail-server. If someone (Microsoft?) could respond with their view of the problem it would be nice. Best regards, Fredrik Lundqvist
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2007 12:29pm

I keep hearing a rumor of a "fix" for E2K3 SP2 that will allow it to more correctly deal with greylisting rejections. I'll nudge someone and see if there is an update. AFAIK, there is no fix currently.
June 7th, 2007 11:36pm

It is nice to know that what I suspected is true, it is a bug.Hopefully there will be a fix soon.Thank for the info.
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2007 11:26am

Have you check this http://support.microsoft.com/kb/934709/en-us
August 27th, 2007 1:44am

This seems to be a very common problem, but Microsoft seems to more or less ignore it. They have not yet come with any real fixes for this. See: http://groups.google.com/group/microsoft.public.exchange.admin/browse_thread/thread/2ac7d5cfc8719427/063bc0ca0ffb6fa4?hl=en for more information about it. The most common solutions used today seems to be: 1. Restart smtp regularely. ..... or 2. Configure "Glitch Retry" .... or 3. Use Forwarding to smarthost. My suggestion is using a smarthost, I have been doing it at a lot of customers, and it seems to work in most cases.
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2008 4:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics