Mailman 3 options and results:
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice:
DMARC wrapped message text:
From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org>
Reply-To: Michael Paoli <[localpart](a)yahoo.com>
DMARC mitigation action: Reject the message
DMARC Mitigate unconditionally: Yes
DMARC rejection notice: Testing DMARC rejection
DMARC wrapped message text: DMARC wrapped message text: headers may be munged
(no munging when posted from @linuxmafia.com)
posting from @yahoo.com bounces:
Your message to the BALUG-test3 mailing-list was rejected for the following
reasons:
Testing DMARC rejection
DMARC mitigation action: Reject the message
DMARC Mitigate unconditionally: No
DMARC rejection notice: Testing DMARC rejection
DMARC wrapped message text: DMARC wrapped message text: headers may be munged
posting from @yahoo.com bounces:
Your message to the BALUG-test3 mailing-list was rejected for the following
reasons:
Testing DMARC rejection
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice: Rejected due to DMARC.
DMARC wrapped message text: Because of DMARC, headers may be munged
posting from @yahoo.com:
adds a first MIME section that has:
Because of DMARC, headers may be munged
From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org>
Reply-To: Michael Paoli <[localpart](a)yahoo.com>
DMARC mitigation action: Reject the message.
DMARC Mitigate unconditionally: Yes
DMARC rejection notice:
DMARC wrapped message text:
posting from @yahoo.com:
our message to the BALUG-test3 mailing-list was rejected for the following
reasons:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
balug-test3-owner(a)lists.balug.org.
Anyway, given the potentially non-ideal situation with DMARC, this seems best compromise:
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice:
DMARC wrapped message text:
And hyperkitty has at least some display/munging issues:
greater than symbol on at least end of email address
shows as as apersand gt semicolon
at symbol in at least email address show as (a)
Yay, looks like I got the archives working:
https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or…
On Fri, Jul 5, 2024 at 2:53 PM Michael Paoli <michael.paoli(a)berkeley.edu> wrote:
>
> Well, I don't know that there's a whole lot to do quite at this point -
> notably as it's not yet fully stabilized and configured (most notably
> still have to get hyperkitty/archiving working properly, then there's
> still quite a bit more testing to do), but if you note anything amiss
> ... particularly if consistently so, may want to point it out.
>
> I'm thinking/hoping that the other pieces of Mailman3 are at least
> meta-stable at this point.
>
> On Fri, Jul 5, 2024 at 10:39 AM <aaronco36(a)sdf.org> wrote:
> >
> > Hi,
> > Thanks for the ongoing status of the Mailman3 testing.
> > Here's hoping that the Mailman 2 --> Mailman 3 migrations continue to
> > proceed successfully and smoothly :-)
> > Further workable/practical/realistic ways to help out in the migration(s),
> > other than _not_ being a potential prodding nuisance about it ?
> > -A
> >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Thu, 4 Jul 2024 19:34:08 -0700
> > > From: Michael Paoli <michael.paoli(a)berkeley.edu>
> > > To: BALUG-test <balug-test(a)lists.balug.org>
> > > Subject: Re: [BALUG-Test] Mailman3 testing
> > > Message-ID:
> > > <CAPU_E+ds6dcKZm8rUU_gw8R9OEh5FP-7pMCRKtYhthvoJK3JgQ(a)mail.gmail.com>
> > > Content-Type: text/plain; charset="UTF-8"
> > >
> > > Still far from even being completely set up,
> > > let alone well tested, and
> > > Mailman 2 --> Mailman 3 migrations.
> > >
> > > But a bit further along, most notably:
> > > https://lists.balug.org/mailman3/
> > > So, at least some of the web stuff is working properly,
> > > but much of it still has to be properly configured,
> > > tested, etc.
> > >
> > > On Wed, Jun 19, 2024 at 9:55?PM Michael Paoli
> > > <michael.paoli(a)berkeley.edu> wrote:
> > >>
> > >> Have some very preliminary Mailman version 3 testing started on
> > >> the BALUG VM, notably for lists.balug.org
> > >> General plan (at least shorter term) is to replace the existing
> > >> soon to be unsupported Mailman 2 with Mailman 3.
> > >>
> > >> So, testing on Mailman3 - presently have one list set up:
> > >> balug-test3(a)lists.balug.org
> > >> Note that it might possibly wink in and out of existence,
> > >> and/or get reloaded, etc., but general intent is for it
> > >> to mostly persist and have continuity through testing,
> > >> And around/after completion of Mailman 2 to Mailman 3
> > >> migration, will probably fold it into existing
> > >> balug-test(a)lists.balug.org list (which will then be Mailman 3).
> > >>
> > >> At the moment, so far (probably) just email interface,
> > >> with other bits to come.
> > >>
> > >> So, subscribe, unsubscribe, etc.
> > >> balug-test3-subscribe(a)lists.balug.org
> > >> balug-test3-unsubscribe(a)lists.balug.org
> > >> balug-test3-request(a)lists.balug.org
> > >>
> > >> Note due to some limitations in how the MTA is
> > >> configured with anti-spam, it will generally
> > >> filter/reject/drop messages with empty bodies (presumed to be spam),
> > >> so, to work around that, don't have an empty body.
> > >> E.g. -request address, to send a command of help,
> > >> put it in the body, or if in the subject, include a body of:
> > >> end
> > >> so it makes it past the anti-spam and gets properly processed.
> > >> The existing Mailman 2 configuration has these MTA anti-spam
> > >> configuration
> > >> limitations noted on the relevant web pages, and the relevant help text,
> > >> etc.
> > >> ... but I haven't yet done any such customization on Mailman3.
Well, I don't know that there's a whole lot to do quite at this point -
notably as it's not yet fully stabilized and configured (most notably
still have to get hyperkitty/archiving working properly, then there's
still quite a bit more testing to do), but if you note anything amiss
... particularly if consistently so, may want to point it out.
I'm thinking/hoping that the other pieces of Mailman3 are at least
meta-stable at this point.
On Fri, Jul 5, 2024 at 10:39 AM <aaronco36(a)sdf.org> wrote:
>
> Hi,
> Thanks for the ongoing status of the Mailman3 testing.
> Here's hoping that the Mailman 2 --> Mailman 3 migrations continue to
> proceed successfully and smoothly :-)
> Further workable/practical/realistic ways to help out in the migration(s),
> other than _not_ being a potential prodding nuisance about it ?
> -A
>
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 4 Jul 2024 19:34:08 -0700
> > From: Michael Paoli <michael.paoli(a)berkeley.edu>
> > To: BALUG-test <balug-test(a)lists.balug.org>
> > Subject: Re: [BALUG-Test] Mailman3 testing
> > Message-ID:
> > <CAPU_E+ds6dcKZm8rUU_gw8R9OEh5FP-7pMCRKtYhthvoJK3JgQ(a)mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Still far from even being completely set up,
> > let alone well tested, and
> > Mailman 2 --> Mailman 3 migrations.
> >
> > But a bit further along, most notably:
> > https://lists.balug.org/mailman3/
> > So, at least some of the web stuff is working properly,
> > but much of it still has to be properly configured,
> > tested, etc.
> >
> > On Wed, Jun 19, 2024 at 9:55?PM Michael Paoli
> > <michael.paoli(a)berkeley.edu> wrote:
> >>
> >> Have some very preliminary Mailman version 3 testing started on
> >> the BALUG VM, notably for lists.balug.org
> >> General plan (at least shorter term) is to replace the existing
> >> soon to be unsupported Mailman 2 with Mailman 3.
> >>
> >> So, testing on Mailman3 - presently have one list set up:
> >> balug-test3(a)lists.balug.org
> >> Note that it might possibly wink in and out of existence,
> >> and/or get reloaded, etc., but general intent is for it
> >> to mostly persist and have continuity through testing,
> >> And around/after completion of Mailman 2 to Mailman 3
> >> migration, will probably fold it into existing
> >> balug-test(a)lists.balug.org list (which will then be Mailman 3).
> >>
> >> At the moment, so far (probably) just email interface,
> >> with other bits to come.
> >>
> >> So, subscribe, unsubscribe, etc.
> >> balug-test3-subscribe(a)lists.balug.org
> >> balug-test3-unsubscribe(a)lists.balug.org
> >> balug-test3-request(a)lists.balug.org
> >>
> >> Note due to some limitations in how the MTA is
> >> configured with anti-spam, it will generally
> >> filter/reject/drop messages with empty bodies (presumed to be spam),
> >> so, to work around that, don't have an empty body.
> >> E.g. -request address, to send a command of help,
> >> put it in the body, or if in the subject, include a body of:
> >> end
> >> so it makes it past the anti-spam and gets properly processed.
> >> The existing Mailman 2 configuration has these MTA anti-spam
> >> configuration
> >> limitations noted on the relevant web pages, and the relevant help text,
> >> etc.
> >> ... but I haven't yet done any such customization on Mailman3.