The list moderators have more limited permissions; they are not able to change any list configuration variable, but they are allowed to tend to pending administration requests, including approving or rejecting held subscription requests, and disposing of held postings. Of course, the list administrators can also tend to pending requests.
In order to split the list ownership duties into administrators and moderators, you must set a separate moderator password, and also provide the email addresses of the list moderators. Note that the field you are changing here specifies the list administrators.''')), ('moderator', mm_cfg.EmailList, (3, WIDTH), 0, _("""The list moderator email addresses. Multiple moderator addresses, each on separate line is okay."""), _('''There are two ownership roles associated with each mailing list. The list administrators are the people who have ultimate control over all parameters of this mailing list. They are able to change any list configuration variable available through these administration web pages.
The list moderators have more limited permissions; they are not able to change any list configuration variable, but they are allowed to tend to pending administration requests, including approving or rejecting held subscription requests, and disposing of held postings. Of course, the list administrators can also tend to pending requests.
In order to split the list ownership duties into administrators and moderators, you must set a separate moderator password, and also provide the email addresses of the list moderators in this section. Note that the field you are changing here specifies the list moderators.''')), ('description', mm_cfg.String, WIDTH, 0, _('A terse phrase identifying this list.'), _('''This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is.''')), ('info', mm_cfg.Text, (7, WIDTH), 0, _('''An introductory description - a few paragraphs - about the list. It will be included, as html, at the top of the listinfo page. Carriage returns will end a paragraph - see the details for more info.'''), _("""The text will be treated as html except that newlines will be translated to <br> - so you can use links, preformatted text, etc, but don't put in carriage returns except where you mean to separate paragraphs. And review your changes - bad html (like some unterminated HTML constructs) can prevent display of the entire listinfo page.""")), ('subject_prefix', mm_cfg.String, WIDTH, 0, _('Prefix for subject line of list postings.'), _("""This text will be prepended to subject lines of messages posted to the list, to distinguish mailing list messages in mailbox summaries. Brevity is premium here, it's ok to shorten long mailing list names to something more concise, as long as it still identifies the mailing list. You can also add a sequential number by %%d substitution directive. eg.; [listname %%d] -> [listname 123] (listname %%05d) -> (listname 00123) """)), ('from_is_list', mm_cfg.Radio, (_('No'), _('Munge From'), _('Wrap Message')), 0, _("""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."""), _("""Several protocols now in wide use attempt to ensure that use of the domain in the author's address (ie, in the From: header field) is authorized by that domain. These protocols may be incompatible with common list features such as footers, causing participating email services to bounce list traffic merely because of the address in the From: field. 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:
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 applied""")), ('anonymous_list', mm_cfg.Radio, (_('No'), _('Yes')), 0, _("""Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields)""")), _('''Reply-To: header munging'''), ('first_strip_reply_to', mm_cfg.Radio, (_('No'), _('Yes')), 0, _('''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.''')), ('reply_goes_to_list', mm_cfg.Radio, (_('Poster'), _('This list'), _('Explicit address')), 0, _('''Where are replies to list messages directed? Poster is strongly recommended for most mailing lists.'''), # Details for reply_goes_to_list _("""This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to Poster, no Reply-To: header is added by Mailman, although if one is present in the original message, it is not stripped. Setting this value to either This list or Explicit address causes Mailman to insert a specific Reply-To: header in all messages, overriding the header in the original message if necessary (Explicit address inserts the value of reply_to_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 for a general discussion of this issue. See Reply-To Munging Considered Useful 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 address and set the Reply-To: address below to point to the parallel list.""")), ('reply_to_address', mm_cfg.Email, WIDTH, 0, _('Explicit Reply-To: header.'), # Details for reply_to_address _("""This is the address set in the Reply-To: header when the reply_goes_to_list option is set to Explicit 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 for a general discussion of this issue. See Reply-To Munging Considered Useful 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, specify the explicit Reply-To: address here. You must also specify Explicit address in the reply_goes_to_list variable.
Note that if the original message contains a Reply-To: header, it will not be changed.""")), _('Umbrella list settings'), ('umbrella_list', mm_cfg.Radio, (_('No'), _('Yes')), 0, _('''Send password reminders to, eg, "-owner" address instead of directly to user.'''), _("""Set this to yes when this list is intended to cascade only to other mailing lists. When set, meta notices like confirmations and password reminders will be directed to an address derived from the member\'s address - it will have the value of "umbrella_member_suffix" appended to the member's account name.""")), ('umbrella_member_suffix', mm_cfg.String, WIDTH, 0, _('''Suffix for use when this list is an umbrella for other lists, according to setting of previous "umbrella_list" setting.'''), _("""When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No".""")), _('Notifications'), ('send_reminders', mm_cfg.Radio, (_('No'), _('Yes')), 0, _('''Send monthly password reminders?'''), _('''Turn this on if you want password reminders to be sent once per month to your members. Note that members may disable their own individual password reminders.''')), ('welcome_msg', mm_cfg.Text, (4, WIDTH), 0, _('''List-specific text prepended to new-subscriber welcome message'''), _("""This value, if any, will be added to the front of the new-subscriber welcome message. The rest of the welcome message already describes the important addresses and URLs for the mailing list, so you don't need to include any of that kind of stuff here. This should just contain mission-specific kinds of things, like etiquette policies or team orientation, or that kind of thing.
Note that this text will be wrapped, according to the following rules:
However, not all mail readers are standards compliant yet, and if you have a large number of members who are using non-compliant mail readers, they may be annoyed at these headers. You should first try to educate your members as to why these headers exist, and how to hide them in their mail clients. As a last resort you can disable these headers, but this is not recommended (and in fact, your ability to disable these headers may eventually go away).""")) ) # Suppression of List-Post: headers rtn.append( ('include_list_post_header', mm_cfg.Radio, (_('No'), _('Yes')), 0, _('Should postings include the List-Post: header?'), _("""The List-Post: header is one of the headers recommended by RFC 2369. However for some announce-only mailing lists, only a very select group of people are allowed to post to the list; the general membership is usually not allowed to post. For lists of this nature, the List-Post: header is misleading. Select No to disable the inclusion of this header. (This does not affect the inclusion of the other List-*: headers.)""")) ) # Suppression of Sender header modification if mm_cfg.ALLOW_SENDER_OVERRIDES: rtn.append( ('include_sender_header', mm_cfg.Radio, (_('No'), _('Yes')), 0, _("""Should the Sender header be rewritten for this mailing list to avoid stray bounces? Yes is recommended."""), _("""RFC 2822 defines the Sender header and defines it as "the mailbox of the agent responsible for the actual transmission of the message." Mailman replaces this header by default with the list's bounce address.
While it is debatable if Mailman is such an agent, setting this header helps directing bounces from some broken MTAs to the right destination. On the other hand, some mail readers show unexpected behaviour if this header is set (like missing addresses in forwarded mails and copies sent to the bounce address on reply-to-all), so it can be disabled here.""")) ) # Do we munge Cc: in AvoidDuplicates.py rtn.append( ('drop_cc', mm_cfg.Radio, (_('No'), _('Yes')), 0, _('Should duplicate avoidance drop addresses from Cc: headers'), _("""The process which avoids sending a list copy of a message to a member who is also directly addressed in To: or Cc: can drop the address from Cc: to avoid growing a long Cc: list in long threads. This can be undesirable as it can break DKIM signatures and possibly cause confusion. To avoid changes to Cc: headers, set this to No.""")) ) # Discard held messages after this number of days rtn.append( ('max_days_to_hold', mm_cfg.Number, 7, 0, _("""Discard held messages older than this number of days. Use 0 for no automatic discarding.""")) ) return rtn def _setValue(self, mlist, property, val, doc): if property == 'real_name' and \ val.lower() <> mlist.internal_name().lower(): # These values can't differ by other than case doc.addError(_("""real_name attribute not changed! It must differ from the list's name by case only.""")) elif property == 'new_member_options': # Get current value because there are valid bits not in OPTIONS. # If we're the admin CGI, we then process the bits in OPTIONS, # turning them on or off as appropriate. Otherwise we process all # the bits in mm_cfg.OPTINFO so that config_list can set and reset # them. newopts = mlist.new_member_options if isinstance(doc, Document): opts = OPTIONS else: opts = mm_cfg.OPTINFO for opt in opts: bitfield = mm_cfg.OPTINFO[opt] if opt in val: newopts |= bitfield else: newopts &= ~bitfield mlist.new_member_options = newopts elif property == 'subject_prefix': # Convert any html entities to Unicode mlist.subject_prefix = Utils.canonstr( val, mlist.preferred_language) elif property == 'info': if val <> mlist.info: if Utils.suspiciousHTML(val): doc.addError(_("""The info attribute you saved contains suspicious HTML that could potentially expose your users to cross-site scripting attacks. This change has therefore been rejected. If you still want to make these changes, you must have shell access to your Mailman server. This change can be made with bin/withlist or with bin/config_list by setting mlist.info. """)) else: mlist.info = val elif property == 'admin_member_chunksize' and (val < 1 or not isinstance(val, IntType)): doc.addError(_("""admin_member_chunksize attribute not changed! It must be an integer > 0.""")) elif property == 'host_name': try: Utils.ValidateEmail('user@' + val) except Errors.EmailAddressError: doc.addError(_("""host_name attribute not changed! It must be a valid domain name.""")) else: GUIBase._setValue(self, mlist, property, val, doc) else: GUIBase._setValue(self, mlist, property, val, doc) def _postValidate(self, mlist, doc): if not mlist.reply_to_address.strip() and \ mlist.reply_goes_to_list == 2: # You can't go to an explicit address that is blank doc.addError(_("""You cannot add a Reply-To: to an explicit address if that address is blank. Resetting these values.""")) mlist.reply_to_address = '' mlist.reply_goes_to_list = 0 def getValue(self, mlist, kind, varname, params): if varname <> 'subject_prefix': return None # The subject_prefix may be Unicode return Utils.uncanonstr(mlist.subject_prefix, mlist.preferred_language)