On 01/30/2018 12:15 AM, Peter Münster wrote:
It seems, that mailman bounces the bounces, so that the list-owner never sees them:
--8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces@my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8---
There are a few things going on here. It appears that out04.smtpout.orange.fr has bounced a list post from the <test@my-domain.org> list and and sent a DSN back to Mailman at <test-bounces@my-domain.org>. It is this DSN that has no Message-ID:. Mailman's LMTP runner rejects such messages.
The underlying issue is the orange.fr domain is sending DSNs without a Message-ID: header.
What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses...
If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] section of your config), this log message
postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces@my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command))
would contain to=<test-bounces+user=example.com@my-domain.org> and you could identify the bouncing address (user@example.com in this case) that way.
Beyond that, there are still other issues, the biggest of which is currently, Mailman is not processing bounces other than storing them in the database. See <https://gitlab.com/mailman/mailman/issues/343>.
Also, the LMTP runner requires a Message-ID: at least in part because that is part of the algorithm for creating a unique ID for archiving. Given that messages to a -bounces address are handled differently and not archived, it would be possible to not require a Message-ID: for those messages, but arguing against that, if a recipient MTA can't create a DSN that has a Message-ID:, would you trust what else it does?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan