On 7/9/22 9:51 AM, Andy Smith wrote:
Over in Exim's mainlog I then see that delivered out to list members. One of them rejects it at SMTP time, which I think causes this:
Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces@mailman.bitfolk.com>' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces@mailman.bitfolk.com Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client()
The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address.
…and I think that bounce message somehow incremented the bounce score for andy@bitfolk.com even though that address was only present in the original post's Cc: and body.
If the original post was the message delivered to users-bounces@mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body.
Is there a good way to further debug this? Maybe by being able to see the full content of the DSNs that Mailman generates?
As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin..., but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message.
If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces.
You might also be able to find the fake dsn and/or the message received
via SMTP to users-bounces@mailman.bitfolk.com in Mailman's var/messages/
directory, although these are pickles and need to be examined with
mailman qfile.
I think I've seen this before in the last couple of weeks so I'm sure it'll crop up again soon. I've seen it mention about bounce score for users-leave before, but I only really paid attention today when it also listed my own address.
users-leave probably is parsed out of the message footer.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan