Ralf Hildebrandt:
[ Charset UTF-8 unsupported, converting... ]
> Sep 11 09:21:22 mail2 postfix/cleanup[23372]: 3cZZKZ2WvdzBt9C: 
> message-id=<f0cdc3dbf712aa448525e5dddc62b6f4039fe69d4...@exchange31.charite.de>
> Sep 11 09:21:22 mail2 postfix/qmgr[10759]: 3cZZKZ2WvdzBt9C: 
> from=<sen...@charite.de>, size=36991, nrcpt=1 (queue active)
> Sep 11 09:31:23 mail2 postfix/smtp[22134]: 3cZZKZ2WvdzBt9C: conversation with 
> mail.vivantes.de[62.220.2.98] timed out while sending end of data -- message 
> may be sent more than once
> Sep 11 09:31:23 mail2 postfix/smtp[22134]: 3cZZKZ2WvdzBt9C: 
> to=<recipi...@vivantes.de>, relay=mail1.vivantes.de[62.220.2.99]:25, 
> delay=601, delays=0.01/0/601/0.55, dsn=2.0.0, status=sent (250 2.0.0 
> r8B7VMsm013069 Message accepted for delivery)
> Sep 11 09:31:23 mail2 postfix/qmgr[10759]: 3cZZKZ2WvdzBt9C: removed
> 
> It seems the first delivery fails (after 10 minutes), and the
> subsequent retry succeeds immediately. It strikes me as odd that the
> mail is being retried in the very second the error message ist being
> logged.

Delivery fails to the primary MX host (mail.vivantes.de) and then
it succeeds to the secondary MX host. Why should Postfix wait when
it switches from primary to secondary MX?

        Wietse

Reply via email to