From ian at iankelling.org Fri Sep 27 20:58:31 2019 From: ian at iankelling.org (Ian Kelling) Date: Sat, 28 Sep 2019 00:58:31 -0000 Subject: [Bug 1845751] [NEW] cc modification due to nodup setting breaks DKIM & thus DMARC Message-ID: <156963231161.15808.17034191154411525924.malonedeb@gac.canonical.com> Public bug reported: Keeping DKIM signature intact allows passing DMARC without from munging (I have references all about this if needed). However, mailman modifies the cc header when a subscriber has the nodup setting and someone sends to the list with that subscriber cced. Mailman doesn't email them and removes them from the cc, presumably so for further replies mailman can email them without it being a duplicate and they get all the good mailman headers instead of a plain email from the cc. Anyways, best if Mailman just not modify the cc if we are in the situation where it matters for passing DMARC. The attached patch does that. Note, I'm sending this as an employee of the Free Software Foundation and my copyright is already going to them. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "nodup-dkim.patch" https://bugs.launchpad.net/bugs/1845751/+attachment/5292024/+files/nodup-dkim.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1845751 Title: cc modification due to nodup setting breaks DKIM & thus DMARC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1845751/+subscriptions From ian at iankelling.org Fri Sep 27 22:03:24 2019 From: ian at iankelling.org (Ian Kelling) Date: Sat, 28 Sep 2019 02:03:24 -0000 Subject: [Bug 1832740] Re: init script / mailmanctl fails to stop mailman 2, reports success References: <156044220339.2385.3922595287292981602.malonedeb@wampee.canonical.com> Message-ID: <156963620474.2881.14427977020846238620.malone@soybean.canonical.com> Sorry, I didn't get around to replying earlier. You are right, smtp is going slow and it seems thats causing the problem. Sep 26 06:33:30 2019 (22952) <20190926102614.28999-8-vsementsov at virtuozzo.com> smtp to qemu-devel for 1053 recips, completed in 328.854 seconds It looks like messages go through much much faster when exim isn't already busy with a lot of other messages. But generally, I can't expect to get exim to reliably accept 1000 messages much faster. So, I think the init script/settings needs to wait longer and not report success when its actually failed. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1832740 Title: init script / mailmanctl fails to stop mailman 2, reports success To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1832740/+subscriptions