On 1/9/25 11:05, Taber, Douglas R via Mailman-users wrote:
Still stumped on this one, is there a way to increase the lmtp logging beyond 
debug?

I’m trying to figure out what is causing the hang for incoming messages here:


Jan 09 13:38:32 2025 (342305) ('127.0.0.1', 48466) << b'250 OK'

Jan 09 13:38:32 2025 (342305) _handle_client readline: b'RCPT 
TO:mail...@lists.renci.org<mailto:mail...@lists.renci.org>\r\n'

Jan 09 13:38:32 2025 (342305) ('127.0.0.1', 48466) >> b'RCPT 
TO:mail...@lists.renci.org<mailto:mail...@lists.renci.org>'

Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) recip: 
mail...@lists.renci.org<mailto:mail...@lists.renci.org>

Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) << b'250 Ok'

Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) EOF received

Jan 09 13:54:22 2025 (342305) ('127.0.0.1', 48466) connection timeout

It just hangs there until a timeout, then retries and immediately succeeds


All those messages are actually logged by aiosmtpd which does the bulk of the work of lmtp runner. There are multiple modules involved here. Mailman's lmtp runner uses the aiosmtpd LMTP class which is a subclass of the aiosmtpd SMTP class which in turn is a subclass of asyncio.StreamReaderProtocol which is reading data from the socket connecting to the incoming MTA. It seems that after the MTA sends the `250 Ok` response to the `RCPT TO:` command the MTA closes the connection and asyncio.StreamReaderProtocol calls the eof_received method resulting in the `EOF received` log message and ultimately the timeout.

Have you looked at the MTA logs? If there's not an answer there, that's where you should look to increase logging.

--
Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/QGNPGR4VMV7GJKEOHKSPT5YRYDH2L74V/

This message sent to arch...@mail-archive.com

Reply via email to