On 2/11/20 10:28 PM, Victoriano Giralt wrote:
I have recently migrated some lists from Mailman 2 to Mailman 3. Users have been added using the mailman client as pre-verified addresses so the migration happened "silently". Thus, there was a dozen "bad" addresses (domains that did not exist anymore).
It seems you rolled your own instead of using mailman import21. Is
there a reason for this?
Unfortunately, Mailman got some of the "bad" addresses in the first message batch for sending out, so, Postfix closed the connection because of "too many errors" and this stopped the process completely, i.e. Mailman did not continue sending messages to the rest of the list over 600 addresses.
Is the message shunted? Is there a traceback and a shunting message in mailman.log?
Normally, I would expect the message to be queued in Mailman's retry queue and retried by Mailman
There was no more information in the logs than the Postfix error messages in smtp.log.
What was in the smtp.log?
Nothing in mailman.log?
Nothing in var/queue/shunt?
Once the "bad" addresses were removed, the list started working as expected.
I consider this a bug. The bouncing addresses should have been marked as "non deliverable" and the subscriptions "paused" and the rest should have been delivered. Or, the list owner should have been notified that there was a problem with message distribution. None of these happened.
The HEAD of the https://gitlab.com/mailman/mailman master branch implements bounce processing. This will be in 3.3.1 which is not yet released.
The place for a bug report is <https://gitlab.com/mailman/mailman/issues>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan