Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge
![](https://secure.gravatar.com/avatar/a66e05f54765bbac4a8f86c86af21755.jpg?s=120&d=mm&r=g)
Upgrade to 2.1.18
Toute connaissance est une réponse à une question.
On May 16, 2014, at 20:43, "Bob Puff" <bob@nleaudio.com> wrote:
So guys... Is there a simple little hack we can do within MM 2.1 to try to mitigate this issue, by adding .invalid or some other extension? I've got a few lists that are getting to the point where MM sends the probe email, and then figures it is not a bouncing address, but a lot of emails are not being delivered.
Bob
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/franck%40peachyma...
Security Policy: http://wiki.list.org/x/QIA9
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 05/16/2014 09:27 PM, Franck Martin wrote:
Upgrade to 2.1.18
If one is going to upgrade, one should upgrade to Mailman 2.1.18-1, but presumably the OP knows that and wants a different mitigation.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Franck Martin
-
Mark Sapiro