Re: Temporary delivery failures not being retried

On Mon, 24 Jul 2006 11:47:58 -0500, Marten <absolute88@xxxxxxxxxxx>
wrote:

I've inherited looking after an Exchange server and am in need of some
assistance. Suggestions are most welcome.

AS I started to readt this, I was betting they recipient was using
greylisting and sure enough...
I think this is a bug with Exch 2003. I take it you deliver mail
directly from the the Exch Server to the Internet?

If so, I would think about a SMTP gateway for outbound mail.

We will send an email with a large number of recipients (20-30). One
receiving mail server is accepting from 3 domains. Only one message
got through it.

We talked to the admin and this is what they replied:

There were indeed three separate copies of the message sent to
our e-mail server. That would be because of the different
e-mail address types of the recipients. Only one was
delivered successfully.

The other two were rejected by our e-mail server with a
temporary delivery failure code (452). The SMTP standard
states that on receipt of a 452 code, an e-mail server is to
retry delivery after approximately 30 minutes. However, your
e-mail server never did the retry. That's why the messages
disappeared.

I've only seen this problem once before with Microsoft
Exchange. This suggests to me that it's not a generic
Exchange problem, but something specific to this
installation. It might be, for example, that somebody has
disabled delivery retries. It could also be that it needs a
patch or service pack to fix this problem. Could you have
somebody check into that?

As for the one message that did get through, I assume that it
was not subject to our greylist embargo because of a previous
successful delivery to that recipient. There's a database of
sender-recipient pairs that ensures that the temporary
failure only happens for the first e-mail message.


Here's a clip from the logfile:
14:13:55 x.x.x.x RCPT - TO:<d@xxxxxxxxxxx> 0
14:13:55 x.x.x.x - - 250+2.1.5+<p@xxxxxxxxxxx>...+Recipient+ok 0
14:13:55 x.x.x.x RCPT - TO:<r@xxxxxxxxxxx> 0
14:13:56 x.x.x.x - - 250+2.1.5+<e@xxxxxxxxxxx>...+Recipient+ok 0
14:13:56 x.x.x.x RCPT - TO:<f@xxxxxxxxxxx> 0
14:13:56 x.x.x.x - -
452+4.2.1+id+k6BEDtqW013770+from+64.42.218.122+temporary+embargo.+See+http://mail.cc.umanitoba.ca/grey/
0
14:13:56 x.x.x.x - - 250+2.1.5+<r@xxxxxxxxxxx>...+Recipient+ok 0
14:13:56 x.x.x.x DATA - - 0
14:13:56 x.x.x.x QUIT - - 0


Where do I need to go to confirm our settings? That the delivery
retires has not been disabled. Any other settings to check?

Just to add to the interest, our Exchange software recently restarted
itself.Looks like a batch of Windows updates had been installed. After
that, the user who initially noticed that the messages hadn't gotten
out finally received delivery failure notification. I don't know if
the problem has been rectified, but I still would appreciate
suggestions on settings to check in the Exchange server.

Marten
.

Relevant Pages

  • Re: Email forwarding.
    ... the recipient it's looking for. ... When I tell exchange to forward all Undeliverable mail to my account, ... headers when it is forwarding from an external source. ... Click the Delivery Options button. ...
    (microsoft.public.exchange.admin)
  • Re: Email Receipts
    ... >> The recipient gets the same options that you do. ... > from First Class to Exchange 2003. ... You could try to use delivery notification instead of read notification. ... their mail server, and if the mail server didn't bounce back an NDR ...
    (microsoft.public.outlook.general)
  • Re: Reject email
    ... Exchange 2003 does provide the ability to "filter recipients who are ... Message Delivery Properties, Recipient filtering tab. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange SA and users sending to this account
    ... This only started when we migrated from Exchange 2000 to Exchange 2003. ... of my fix below is that if a spammer is actually using a legitimate server he ... Right click on Delivery options and choose Properties. ... Click on the tab for "Recipient Filtering". ...
    (microsoft.public.exchange.admin)
  • Temporary delivery failures not being retried
    ... I've inherited looking after an Exchange server and am in need of some ... The other two were rejected by our e-mail server with a ... retry delivery after approximately 30 minutes. ...
    (microsoft.public.exchange.admin)