[Mailman-Users] Re: DMARC Wrap Message doesn't preserve addressees

On Mon, Feb 28, 2022 at 9:23 PM Mark Sapiro wrote: > > message characteristics. See remarks beginning at > https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L193 > and >

[Mailman-Users] DMARC Wrap Message doesn't preserve addressees

We've noticed that with DMARC moderation set to "Wrap Message", the rewritten header doesn't preserve the original addressee list. In the particular case that I'm looking at right now, the list address itself is removed from the Cc header. We've had a few complaints that this results in

[Mailman-Users] Re: Manually incrementing bounce counters

On Thu, 17 Dec 2020 at 18:19, Mark Sapiro wrote: > > See , mirrored at > > Thanks! -- Mailman-Users mailing list -- mailman-users@python.org

[Mailman-Users] Manually incrementing bounce counters

I occasionally get "Uncaught bounce notifications" where mailman has been unable to figure out which user/list to increment the bounce counters for, but where it's blindingly obvious to me. If it's just one or two bounces I'm happy to leave it alone, but in other cases I'd like to manually

[Mailman-Users] Re: mailman v2.x

On Sat, 19 Sep 2020 at 13:07, Mark Sapiro wrote: > >> I'm pretty sure that at least for now I[1] can configure a system to > >> run Mailman 2 so that none of the above matters (eg, have the web > >> server and MTA speak TLS so that Mailman doesn't have to), but I'm not > >> confident that will

[Mailman-Users] Re: mailman v2.x

I'm probably going to regret getting involved in this conversation, but ... On Sat, 19 Sep 2020 at 08:48, Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > I'm pretty sure that at least for now I[1] can configure a system to > run Mailman 2 so that none of the above matters

[Mailman-Users] Re: mailman v2.x

On Thu, 17 Sep 2020 at 10:14, Mark Sapiro wrote: > On 9/17/20 6:54 AM, Matthew Pounsett wrote: > > > > If someone was going to undertake a rewrite of Postorius, using a > different > > web development framework (e.g. Flask, but pretty much anything that > isn't > &

[Mailman-Users] Re: mailman v2.x

On Thu, 17 Sep 2020 at 07:22, Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > Replacing Postorius with a Mailman 2 lookalike would probabaly be a > nearly complete rewrite. Of course you can reuse the HTML and perhaps > the page-generating code, but all of the "business

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 25 Nov 2019 at 05:04, Johannes Rohr wrote: > The obvious big showstopper is that there is no supported upgrade path > from Mailman 2.* yet, according to > > http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x > and so you certainly don't

Re: [Mailman-Users] DMARC message wrapping not working

On Tue, 21 May 2019 at 20:21, Mark Sapiro wrote: > On 5/21/19 6:41 AM, Matthew Pounsett wrote: > > > > Ah, I see. I think that would be worth calling out in the documentation. > > I think the way it's currently written strongly implies that it will > bring >

Re: [Mailman-Users] DMARC message wrapping not working

On Mon, 20 May 2019 at 11:35, Mark Sapiro wrote: > On 5/19/19 1:13 PM, Matthew Pounsett wrote: > > I've got a mailman 2.1.26 install I've taken over. I've attempted to > turn > > on DMARC message wrapping by setting DEFAULT_DMARC_MODERATION_ACTION in > my > > mm_cfg.p

[Mailman-Users] DMARC message wrapping not working

I've got a mailman 2.1.26 install I've taken over. I've attempted to turn on DMARC message wrapping by setting DEFAULT_DMARC_MODERATION_ACTION in my mm_cfg.py file, but it doesn't seem to have had the desired effect. I'm still seeing messages from p=reject domains going out with their original