On 7/17/26 11:00, Dave Nathanson via Mailman-Users wrote:
Hi,
I'm familiar with Mailman v2 at DreamHost, and now setting up & learning
Mailman v3 with Affinity at EMWD.com (EMWD is looking good so far, review coming
later).
One setting I'd like to check in about is MUNGE . What should I be doing with
Munge?
My gut feeling is to use; "Explicit Reply-To header set". But I'm here to ask,
not to tell.
The drawback is that after Munging the "From", it is no longer trivial to see
who sent the message to the group. Sort of good. Sort of bad, depending. I mostly prefer
to easily see the poster's email address. And the big mail providers would mostly accept
this From format if it matched the Mailman sending server.
It has been a long time since I have had anything to do with Affinity so
I'm not familiar with the web UI, but it seems the above is conflating
two settings. One of these is the Reply goes to list setting which has
to do with munging the Reply-To: and has nothing to do with munging the
From:. This corresponds roughly to the MM 2.1 setting
reply_goes_to_list. We generally recommend `No Munging` for this
setting, at least for discussion lists. However, it seems that your MM
2.1 lists are set for reply_goes_to_list = This list and the
corresponding MM 3 setting is Reply goes to list.
I don't know what Affinity's help for Reply goes to list says, but
Postorius says
Where are replies to list messages directed? No Munging is strongly
recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in
messages flowing through this mailing list. When set to No Munging, no
Reply-To: header is added by Mailman, although if one is present in the
original message, it may be stripped depending on First strip Reply-To.
Setting this value to Reply to List or either of the Explicit Reply
settings causes Mailman to insert a specific Reply-To: header in all
messages, either adding to or overriding the header in the original
message depending on First Strip Reply-To. Explicit Reply inserts the
value of Explicit reply-to_address, Reply goes to list inserts the list
posting address. Explicit Reply-to set; no Cc added is useful for
announce-only lists where you want to avoid someone replying to the list
address. There are many reasons not to introduce or override the
Reply-To: header. One is that some posters depend on their own Reply-To:
settings to convey their valid return address. Another is that modifying
Reply-To: makes it much more difficult to send private replies. See
`Reply-To' Munging Considered Harmful
<http://marc.merlins.org/netrants/reply-to-harmful.html> for a general
discussion of this issue. See `Reply-To' Munging Considered Useful
<http://marc.merlins.org/netrants/reply-to-useful.html> for a dissenting
opinion. Some mailing lists have restricted posting privileges, with a
parallel list devoted to discussions. Examples are `patches' or
`checkin' lists, where software changes are posted by a revision control
system, but discussion about the changes occurs on a developers mailing
list. To support these types of mailing lists, select Explicit Reply and
set the Reply-To: address option to point to the parallel list.
The main issue with setting this to Reply goes to list is it makes it
easy to inadvertently send a private reply to the list which can be a
serious and irreversible error whereas inadvertently replying to the
poster instead of the list is easily correctable. You should read the
articles linked in the above help for additional information.
The other setting is for DMARC mitigations. Our recommendation for this
setting is `Replace From: with list address`. This does not hide the
sender. We take greate pains to expose the sender. For example assume a
post From: Jane User <[email protected]> to [email protected]. The munged
From: will be
From: Jane User via List Display Name <[email protected]>
and [email protected] will be added to either Reply-To: or Cc: depending
on list settings. See
<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc.py?ref_type=heads#L67-87>
I have set up everything I can think of to try for good delivery; SPF, DKIM,
DMARC, and a SSL certificate on the server.
My discussion group lists all work best with any reply being sent to the list,
not to the poster directly. And it is helpful to somehow indicate who wrote the
message.
The Munging options I see are:
No Munging
Reply goes to list
Explicit Reply-To header set
Explicit Reply-To header set, no CC added.
And there are some similar DMARC Mitigations.
Anyway, are we still doing Munging with MailMan v3 with Affinity?
What is the v3 best setting for handling the From address?
If you are talking about From: munging, yes - it is the recommended
option for DMARC mitigation which must be done for reliable delivery.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/[email protected]/
https://mail.python.org/archives/list/[email protected]/
Member address: [email protected]
