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.
> Another 25 seconds by google without conn_use:
>
> May 22 03:12:57 mail01.raystedman.org t121/smtp[47173]:
> 4224D30C1817: to=<<deleted>@gmail.com>,
> relay=gmail-smtp-in.l.google.com[142.250.141.27]:25, delay=1543,
> delays=0.01/1517/25/0.79, dsn=2.0.0, status=sent (250 2.0.0 OK
> 1716372777 41be03b00d2f7-66d4526311dsi4920983a12.891 - gsmtp)
Yup.
Wiets
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
