On 25 Sep 2019, at 5:18, Simon Lyall via mailop wrote:
Just had a bunch of people at a domain get unsubscribed from this
list.
Something is very wrong there...
4xx failures, even persistent ones that ultimately fail the message for
queue timeout, should not cause an instant unsub from one message
failure. Are your bounce handling settings extra-strict?
Appears to be some weird Google rule (which probably made sense with
they were not the MX for 30% of all active domains)
Any chance of them fixing it
It's not broken. It's functionally identical to sites that enforce a
one-RCPT-per-DATA rule.
The right behavior when a MX gives a 4xx response to RCPT is for the
sending MTA to continue with any remaining recipients, remove the
successful ones from the envelope, and requeue the message with the
4xx-ed recipients later. Repeat as necessary to clear the envelope or
until you hit a maximum queue lifetime.
(or failing that a quick work-around for mailman)?
Enable VERP?
It's not actually Mailman at fault. Mailman hands mail to a friendly MTA
for working out delivery details. Most MTAs split RCPTs by domain, but
Exim is always a fun exception to "most MTAs."
Enabling VERP forces each copy of a message to be sent with a single
recipient, because the envelope sender is unique per-recipient. No MTA
shenanigans can undo that.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
