On 5/31/24 22:23, hansen via Mailman-users wrote:
Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists.
DMARC mitigation action ‘Replace From: with list address’ will also
place the poster's address in Reply-To: (or Cc: depending on list
configuration), so a simple reply from a reasonable MUA should go just
to the poster.
For example, say the mail client captures my address as
“Allan Hansen via <listname>” <listaddress>
then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field:
“Allan Hansen via <listname>”
and, to make it worse, the actual email address, <listaddress>, is often hidden.
If this is the result of a reply and not reply-all the client is not
behaving reasonably.
The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information.
That is a problem with the client, but I suppose such clients are not uncommon.
Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e.,
"Allan Hansen via <listname>"
You could add a header filter on the To header with a regexp like
^.*via <listname> and the desired action.
Should I get onto the other list to request this as an enhancement?
I don't think that's necessary in this case, as Header filters should do it.
In general, the best way to request an enhancement is to file an issue
with the appropriate GitLab project at https://gitlab.com/mailman
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan