[ClusterLabs] @ maillist Admins - DMARC (yahoo)

[kgaillot at redhat.com]

On Wed, 2021-07-14 at 15:28 +0100, lejeczek wrote:
> 
> On 12/07/2021 15:50, kgaillot at redhat.com wrote:
> > On Sat, 2021-07-10 at 12:34 +0100, lejeczek wrote:
> > > Hi Admins(of this mailing list)
> > > 
> > > Could you please fix in DMARC(s) so those of us who are on
> > > Yahoo would be able to receive own emails/thread.
> > > 
> > > many thanks, L.
> > 
> > I suppose we should do something, since this is likely to be more
> > of an
> > issue as time goes on. Unfortunately, it's not as simple as
> > flipping a
> > switch. These are the two reasonable choices:
> > 
> > 
> > (1) Change the "From" on list messages so that they appear to be
> > from
> > the list, rather than the poster. For example, your posts would
> > show up
> > as "From: lejeczek via ClusterLabs Users <users at clusterlabs.org>"
> > rather than "From: lejeczek <peljasz at yahoo.co.uk>". This is less
> > intrusive but makes it more difficult to reply directly to the
> > sender,
> > add the sender to an address book, etc.
> > 
> > 
> > (2) Stop adding [ClusterLabs] to subject lines, setting ReplyTo: to
> > the
> > list instead of original author, and adding the list signature.
> > This is
> > more standards-compliant, since the List-* headers can still be
> > used
> > for filtering, unsubscribing, and replying to the list, but not all
> > mail clients make those easy to use.
> > 
> > 
> > Anyone have preferences for one over the other?
> > 
> > (Less reasonable options include wrapping every post in MIME, and
> > disallowing users from DMARC domains to post to the list.)
> 
> Ovirt admins/maintainers (also Redhat's) should have a 
> recipe ready. They have it sussed out.
> many thanks, L.

Either option is easy enough to configure, we just need to decide which
one we want.

After re-reading the documentation, I see mailman 2 will do option #1
("from" munging) only for domains with a strict DMARC policy, leaving
other senders' "from" untouched, so I'll go with that option for now,
and we can revisit if there are issues.
-- 
Ken Gaillot <kgaillot at redhat.com>