On 19/02/2014 17:15, Viktor Dukhovni wrote:
On Wed, Feb 19, 2014 at 03:00:25PM +0200, Birta Levente wrote:
With 2.12.20140209 I get hundreds defferals because:
Feb 19 05:21:59 srv2 postfix-slow/smtp[14313]: Untrusted TLS
connection established to mta5.am0.yahoodns.net[98.138.112.38]:25:
TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)
Feb 19 05:21:59 srv2 postfix-slow/smtp[14313]: 3fTNdZ6PdBz7xxb: host
mta5.am0.yahoodns.net[98.138.112.38] said: 421 4.7.0 [GL01] Message
from (81.196.63.20) temporarily deferred - 4.16.50. Please refer to
http://postmaster.yahoo.com/errors/postmaster-21.html (in reply to
MAIL FROM command)
Feb 19 05:21:59 srv2 postfix-slow/smtp[14313]: 3fTNdZ6PdBz7xxb: lost
connection with mta5.am0.yahoodns.net[98.138.112.38] while sending
RCPT TO
This is too narrow a view of the events (insufficient logging from
smtp(8) posted). What happens when the SMTP client reconnects?
Yahoo has multiple MX hosts, show *all* logging from:
postfix-slow/smtp[14313]:
up and including to the logging of the 'dsn=[245]' log entries when
the delivery attempt is complete, and starting from the first log
entry for the process (or, if it handled previous deliveries, from
the first log entry after the last 'dsn=[245]' log entry that
precedes the yahoo failure in question).
Throttling or non-throttling is based on a complete delivery attempt,
not a connection to an individual host. Yahoo has many MX hosts,
Postfix will try up to two transactions per delivery, with TLS
plaintext retries possibily raising this to four.
We had considered special-casing "4XX" replies as a reason to not
retry plaintext when TLS connections are lost. If your more complete
logs demonstrate a need to do that, we may add the requisite logic.
Please post *complete* logging from smtp(8) showing *all* events for
the session in question.
I sent yesterday the logs, but now I just realized that my message was
to big.
Here is:
http://pastebin.com/ghBLBDGP
Thanks
--
Levi
