From 9281bc8160fd31d5029e1244a9c88f873308f334 Mon Sep 17 00:00:00 2001 From: Mark Sapiro Date: Fri, 2 May 2014 10:05:20 -0700 Subject: Revised the documentation for from_is_list. --- Mailman/Gui/General.py | 72 +++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 59 insertions(+), 13 deletions(-) (limited to 'Mailman/Gui') diff --git a/Mailman/Gui/General.py b/Mailman/Gui/General.py index a917642c..2d9acfda 100644 --- a/Mailman/Gui/General.py +++ b/Mailman/Gui/General.py @@ -156,19 +156,65 @@ class General(GUIBase): ('from_is_list', mm_cfg.Radio, (_('No'), _('Munge From'), _('Wrap Message')), 0, - _("""Replace the sender with the list address to conform with - policies like DMARC."""), - _("""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.""") + - _("""

If This has resulted + in members being unsubscribed despite being perfectly able to + receive mail. +

+ The following actions are applied to all list messages when + selected here. To apply these actions only to messages where the + domain in the From: header is determined to use such a protocol, + see the + dmarc_moderation_action settings under Privacy options... + -> Sender filters. +

Settings:

+

+
No
+
Do nothing special. This is appropriate for anonymous lists. + It is appropriate for dedicated announcement lists, unless the + From: address of authorized posters might be in a domain with a + DMARC or similar policy. It is also appropriate if you choose to + use dmarc_moderation_action other than Accept for this list.
+
Munge From
+
This action replaces the poster's address in the From: header + with the list's posting address and adds the poster's address to + the addresses in the original Reply-To: header.
+
Wrap Message
+
Just wrap the message in an outer message with the From: + header containing the list's posting address and with the original + From: address added to the addresses in the original Reply-To: + header and with Content-Type: message/rfc822. This is effectively + a one message MIME format digest.
+
+

The transformations for anonymous_list are applied before + any of these actions. It is not useful to apply actions other + than No to an anonymous list, and if you do so, the result may + be surprising. +

The Reply-To: header munging actions below interact with these + actions as follows: +

first_strip_reply_to = Yes will remove all the incoming + Reply-To: addresses but will still add the poster's address to + Reply-To: for all three settings of reply_goes_to_list which + respectively will result in just the poster's address, the + poster's address and the list posting address or the poster's + address and the explicit reply_to_address in the outgoing + Reply-To: header. If first_strip_reply_to = No the poster's + address in the original From: header, if not already included in + the Reply-To:, will be added to any existing Reply-To: + address(es). +

These actions, whether selected here or via + dmarc_moderation_action, do not apply to messages in digests + or archives or sent to usenet via the Mail<->News gateways. +

If dmarc_moderation_action applies to this message with an action other than Accept, that action rather than this is -- cgit v1.2.3