List adds information to sender's name
Hi
On a list using Mailman 2.1.23 (on cpanel 66.0.23) I have noticed the following effects:
Most messages appear with the author's name and in the "From:"-field in the same form as the author has set up in his mail application. However, some show additional information like "Realname via Listname".
I have analyzed some of those messages, and it appears that this only happens when the author puts his own address in the "Cc:"-field (= sends a copy to himself). Then I have tried to double-check the behaviour and put my own address in a message to the list.
Surprisingly, the message was delivered directly to me, but the list never sent it to me so I could not check whether "...via listname" was also appended to my "From:"-address. I have seen the message in the list's archive; there it is without "...via listname".
Is this normal behaviour? Can the list be configured to not append the "...via listname" information to these messages? And why do I not receive my message via the list but only directly?
Thank you for all ideas, Christian
--
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe für Strassenkinder in Ghana: http://www.chance-for-children.org
.
At Tue, 19 Sep 2017 19:37:49 +0200 luscheina@yahoo.de wrote:
Hi
On a list using Mailman 2.1.23 (on cpanel 66.0.23) I have noticed the following effects:
Most messages appear with the author's name and in the "From:"-field in the same form as the author has set up in his mail application. However, some show additional information like "Realname via Listname".
I have analyzed some of those messages, and it appears that this only happens when the author puts his own address in the "Cc:"-field (=3D sends a copy to himself). Then I have tried to double-check the behaviour and put my own address in a message to the list.
Surprisingly, the message was delivered directly to me, but the list never sent it to me so I could not check whether "...via listname" was also appended to my "From:"-address. I have seen the message in the list's archive; there it is without "...via listname".
Is this normal behaviour? Can the list be configured to not append the "...via listname" information to these messages? And why do I not receive my message via the list but only directly?
This latter is controled by a subscriber option (last option):
"Avoid duplicate copies of messages? Avoid duplicate copies of messages?
When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select Yes to avoid receiving copies from the mailing list; select No to receive copies.
If the list has member personalized messages enabled, and you elect to receive copies, every copy will have a X-Mailman-Copy: yes header added to it. "
Default for this option is "Yes".
The From: munging is part of the DMARC handling (General Admin Options):
"Replace the sender with the list address to conform with policies like ADSP and DMARC. It replaces the poster's address in the From: header with the list address and adds the poster to the Reply-To: header, but the anonymous_list and Reply-To: header munging settings below take priority. If setting this to Yes, it is advised to set the MTA to DKIM sign all emails. If this is set to Wrap Message, just wrap the message in an outer message From: the list with Content-Type: message/rfc822. (Edit from_is_list)"
You are seeing the "Mung From" option behaviour.
Thank you for all ideas, Christian
-- =
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) =
Hilfe f=FCr Strassenkinder in Ghana: http://www.chance-for-children.org
.
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/heller%4= 0deepsoft.com
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
Hello Robert Heller. On Tue, 19 Sep 2017 15:37:50 -0400 (EDT), you wrote:
The From: munging is part of the DMARC handling (General Admin Options):
"Replace the sender with the list address to conform with policies like ADSP and DMARC. It replaces the poster's address in the From: header with the list address and adds the poster to the Reply-To: header, but the anonymous_list and Reply-To: header munging settings below take priority. If setting this to Yes, it is advised to set the MTA to DKIM sign all emails. If this is set to Wrap Message, just wrap the message in an outer message From: the list with Content-Type: message/rfc822. (Edit from_is_list)"
You are seeing the "Mung From" option behaviour.
Strange. Settings for the list are:
Replace the From: header address with the list's posting address to mitigate issues stemming from the original From: domain's DMARC or similar policies. NO
Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) NO
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explict Reply-To: header is added by Mailman or not. YES
Where are replies to list messages directed? Poster is strongly recommended for most mailing lists. THIS LIST
Explicit Reply-To: header. (FIELD IS EMPTY)
To my understanding, this should not cause any of the effects described in my previous message. Every list subscriber should see who wrote a message (so the From should not be replaced by the list address) and we want to keep the discussions on the list (it is a discussion list for technical issues with the MacOS operating system), so we do not select "reply to poster".
What happens, if I set the list not to add/change the Reply-To header, and still set the list address in the Explicit Reply-To header field? I guess Mailman will just ignore that field - or not?
If there are better settings to accomplish the goals, this would be very helpful.
Thank you, Christian
--
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org
.
On 09/20/2017 09:32 AM, Christian F Buser via Mailman-Users wrote:
On Tue, 19 Sep 2017 15:37:50 -0400 (EDT), you wrote:
You are seeing the "Mung From" option behaviour.
Strange. Settings for the list are:
Replace the From: header address with the list's posting address to mitigate issues stemming from the original From: domain's DMARC or similar policies. NO
This is the from_is_list setting which controls DMARC mitigations applied to ALL messages.
You also need to look at Privacy options... -> Sender filters settings dmarc_moderation_action and dmarc_quarantine_moderation_action which control the mitigations applied to messages From: domains that publish DMARC policies of reject and quarantine.
What happens, if I set the list not to add/change the Reply-To header, and still set the list address in the Explicit Reply-To header field? I guess Mailman will just ignore that field - or not?
If reply_goes_to_list is Explicit address, mailman will add reply_to_address to Reply-To: and if that's the list posting address, it's no different from setting reply_goes_to_list to This list.
If reply_goes_to_list is Poster, Mailman won't add anything to Reply-To: for this reason, but it will still honor first_strip_reply_to and add the original From: to Reply-To: if the From: is munged.
If there are better settings to accomplish the goals, this would be very helpful.
You need to do something to mitigate DMARC or all posts to the list From: domains that publish DMARC p=reject will be bounced by many recipients ISPs. For advice on what you can do, see <https://wiki.list.org/x/17891458>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 09/19/2017 10:37 AM, Christian F Buser via Mailman-Users wrote:
Surprisingly, the message was delivered directly to me, but the list never sent it to me so I could not check whether "...via listname" was also appended to my "From:"-address. I have seen the message in the list's archive; there it is without "...via listname".
From: header munging is not done in archives or digests because it isn't necessary there. (Also see <https://mail.python.org/pipermail/mailman-users/2017-September/082470.html>)
Is this normal behaviour? Can the list be configured to not append the "...via listname" information to these messages?
In short, it can but we won't because it would cause your posts to be rejected by every recipient whose ISP honors DMARC.
And why do I not receive my message via the list but only directly?
Because your list option "Avoid duplicate copies of messages?" for this list is set to Yes (the default). If you don't like that, go to<https://mail.python.org/mailman/options/mailman-users>, log in and change it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Christian F Buser -
Mark Sapiro -
Robert Heller