Wietse Venema via Postfix-users:
> Greg Sims via Postfix-users:
> > May 22 03:13:22 mail01.raystedman.org t123/smtp[46725]:
> > 604BE30A4ACA: to=<<deleted>@gmail.com>,
> > relay=gmail-smtp-in.l.google.com[142.251.2.26]:25, conn_use=2,
> > delay=1576, delays=0.05/1550/25/0.84, dsn=2.0.0, status=sent (250
> > 2.0.0 OK 1716372802 41be03b00d2f7-6578166a383si2117154a12.283 -
> > gsmtp)
>
> These 25s are unexpected.
>
> - When Postfix saves/reuses a connection it does not rmember the
> time spent setting up the connection. Technically, there is no
> msg_stats_print() call in the code path that saves a connection to
> the connection cache, and there is no msg_stats_scan() call in the
> code path that retrieves a connection from cache.
>
> That means it took the Postfix SMTP client 25s to:
>
> - Receive a delivery request from the queue manager,
>
> - Retrieve a connection from the connection cache,
>
> - Send the RSET command to the remote SMTP server,
>
> - Retrieve the RSET server response.
>
> That is, the clock for 'connection setup' stops when the Postfix
> SMTP client builds the MAIL FROM command. This is also when he
> clock is started for the time spent delivering the message.
If the delay is with snding or receiving RSET, then the SMTP client
log "conversation with XXX timed out". I don't know if hat has a
queue ID logged with thata, though. Just grep for 'conversation with'.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
