!

Mailman: Advanced Preferences for List Administrators

Introduction to Mailman

This document describes the advanced preferences and options that are available to list administrators in Mailman.  Before using this document, you are encouraged to review the help sheet titled Getting Started with Mailman for List Administrators, which covers the basic preferences that will be used by most list administrators.

Mailman is software that lets you manage electronic mailing lists. It supports a wide range of mailing list types, such as general discussion lists and announce-only lists.  Mailman has extensive features for controlling the privacy of your lists, distributing your list as personalized postings or digests, and providing automatic bounce detection.  Mailman provides a built-in archiver, multiple natural languages, as well as advanced content and topic filtering.

Mailman provides several interfaces to its functionality. Most list administrators will primarily use the Web interface to customize their lists.  There is also a limited email command interface to the administrative functions.

A List’s Email Addresses

Every mailing list has a set of email addresses to which messages can be sent. There is always one address for posting messages to the list, one address to which bounces will be sent, and addresses for processing email commands. For example, for a mailing list called mylist@list.pitt.edu, you’d find these addresses:

  • mylist@list.pitt.edu – this is the email address people should use for new postings to the list.
  • mylist-join@list.pitt.edu – by sending a message to this address, a new member can request subscription to the list.  Both the Subject: header and body of such a message are ignored. Note that mylistsubscribe@list.pitt.edu is an alias for the -join address.
  • mylist-leave@list.pitt.edu – by sending a message to this address, a member can request unsubscription from the list. As with the -join address, the Subject: header and body of the message are ignored. Note that mylistunsubscribe@list.pitt.edu is an alias for the -leave address.
  • mylist-owner@list.pitt.edu – This address reaches the list owner and list moderators directly.
  • mylist-request@list.pitt.edu – This address reaches a mail robot which processes email commands that can be used to set member subscription options, as well as process other commands.
  • mylist-bounces@list.pitt.edu – This address receives bounces from members whose addresses have become either temporarily or permanently inactive. The -bounces address is also a mail robot that processes bounces and automatically disables or removes members as con figured in the bounce processing settings. Any bounce messages that are either unrecognized or do not seem to contain member addresses are forwarded to the list administrators.
  • mylist-confirm@list.pitt.edu – This address is another email robot. It processes confirmation messages for subscription and unsubscription requests.

An -admin address exists that also reaches the list administrators, but this address only exists for compatibility with older versions of Mailman.

Administrative Roles

There are two primary administrative roles for each mailing list, a list owner and a list moderator. A list owner is allowed to change various settings of the list, such as the privacy and archiving policies, the content filtering settings, etc. The list owner is also allowed to subscribe or invite members, unsubscribe members, and change any member’s subscription options.

The list moderator on the other hand, is only allowed to approve or reject postings and subscription requests. The list moderator can also perform actions such as clearing a member’s moderation flag, or adding an address to a list of approved non-member posters.

Normally, the list owner and list moderator is the same person. In fact, the list owner can always do all the tasks a list moderator can do. Access to both the owner’s configuration pages and the moderation pages are protected by the same password. However, if the list owner wants to delegate posting and subscription approval authority to other people, a separate list moderator password can be set, giving moderators access to the approval pages but not the configuration pages. In this setup, list owners can still moderate the list.

In the sections that follow, the terms “list owner” and “list administrator” are often used interchangeably.

A List’s Web Pages

Mailman provides a set of Web pages that list members use to get information about the list or manage their membership options.  There are also list archive pages for browsing an online Web-based archive of the list traffic.

Mailman also provides a set of pages for configuring an individual list, as well as a set of pages for disposing of posting and subscription requests.

For a mailing list called mylist hosted at the domain list.pitt.edu, you would access the administrative pages by going to https://list.pitt.edu/mailman/admin/mylist. The first time you visit this page, you will be presented with a login page, asking for the list owner’s password. When you enter the password, Mailman will store a session cookie in your browser so you don’t have to re-authenticate for every action you want to take. This cookie is stored only until you exit your browser.

To access the administrative requests page, you’d visit https://list.pitt.edu/mailman/admindb/mylist (note the admindbURL as opposed to the adminURL). Again, the first time you visit this page, you’ll be presented with a login page, on which you can enter either the list moderator password or the list owner password. Again, a session cookie is dropped in your browser. Note also that if you’ve previously logged in as the list owner, you do not need to re-login to access the administrative requests page.

Basic Architectural Overview

This section will outline the basic architecture of Mailman, such as how messages are processed by the system. This information will help you understand how the configuration options control Mailman’s functionality.

When mail enters the system from your mail server, it is dropped into one of several Mailman queues depending on the address to which the message was sent. For example, if your system has a mailing list named mylist and your domain is list.pitt.edu, people can post messages to your list by sending them to mylist@list.pitt.edu. These messages will be dropped into the incoming queue, which is also colloquially called the moderate-and-munge queue.  The incoming queue is where most of the approval process occurs, and it is also where the message is prepared for delivery to the list membership.

There are separate queues for the built-in archiver, the bounce processor, the email command processor, as well as the outgoing email and news queues. There’s also a queue for messages generated by the Mailman system.  Each of these queues typically has one queue runner (or “qrunner”) that processes messages in the queue. The qrunners are idle when there are no messages to process.

Every message in the queues is represented by two files, a message file and a metadata file. Both of these files share the same base name, which is a combination of a unique hash and the Unix time that the message was received. The metadata file has a suffix of ‘.db’ and the message file has a suffix of either ‘.msg’ if stored in plain text, or ‘.pck’ if stored in a more efficient internal representation (specifically, a Python pickle).

As a message moves through the incoming queue, it performs various checks on the message, such as whether it matches one of the moderation criteria, or contains disallowed MIME types. Once a message is approved for sending to the list membership, the message is prepared for sending by deleting, adding, or changing message headers, adding footers, etc. Messages in the incoming queue may also be stored for appending to digests.

The List Configuration Pages

After logging in to the list configuration pages, you’ll see the configuration options for the list grouped in categories. All   the administrative pages have some common elements. In the upper section, you’ll see two columns labelled “Configuration Categories”. Some categories have sub-categories that are only visible when you click on the category link. The first page you see after logging in will be the “General Options” category. The specific option settings for each category are described below.

On the right side of the top section, you’ll see a column labelled “Other Administrative Activities”. Here you will find some other actions you can perform, as well as convenient links to the list information page and the list archives. Note the large “Logout” link; use this if you are finished con figuring your list and don’t want to leave the session cookie active in your browser.

Below this common header, you’ll find a list of this category’s configuration variables, arranged in two columns. In the left column is a brief description of the option, which also contains a Details link. Clicking on the Details link brings up a page which contains more information about that option, as well as a button for submitting your setting, and a link back to the category page. The document you are reading contains much of the same information that can be found by clicking the “details” link.

On the right side of the two-column section, you’ll see the variable’s current value. Some variables may present a limited set of values, via radio button or check box arrays. Other variables may present text entry boxes of one or multiple lines. Most variables control settings for the operation of the list, but others perform immediate actions (these are clearly labelled).

At the bottom of the page, you’ll find a Submit button and a footer with some more useful links. Clicking the Submit button commits your list settings after they have been validated. Any invalid values will be ignored and an error message will be displayed at the top of the resulting page. The results page will always be the category page that you submitted.

The General Options Category

The General Options category allows you to set a variety of variables that affect basic behavior and public information. In the descriptions that follow, the variable name is given first, along with an overview and a description of what that variable controls.

General list personality

These variables, grouped under the general list personality section, control some public information about the mailing list.

real_name Every mailing list has both a postingnameand a real name. The posting name shows up in URLs and in email addresses, e.g. the mylist in mylist@list.pitt.edu. The posting name is always presented in lower-case, with alphanumeric characters and no spaces. The list’s real name is used in some public information and email responses, such as in the general list overview.

owner This variable contains a list of email addresses, one address per line, of the list owners. There are two ownership roles associated with each mailing list. The list owners (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 work with pending administration requests, including approving or rejecting held subscription requests, and disposing of held postings. Of course, the list administrators can also work with 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 in the owner option specifies the list administrators.

moderator This variable contains a list of email addresses, one address per line, of the list moderators. These addresses are often used in combination with the owner addresses (see above). For example, when you email mylist-owner@list.pitt.edu, both the owner and moderator addresses will receive a copy of the message.

description In the general list overview page, which shows you every available mailing list, each list is displayed with a short description. The content of this variable is that description. Note that in emails from the mailing list, this description is also used in the comment section of the To: address. This text should be relatively short and no longer than one line. In general, the text should be as succinct as you can make it, while still identifying what the list is.

info This variable contains a longer description of the mailing list. It is included at the top of the list’s information page, and it can contain HTML. Please note that blank lines will be automatically converted into paragraph breaks. Preview your HTML though, because unclosed or invalid HTML code can prevent display of parts of the list information page.

subject_prefix This is a string that will be prepended to the Subject: header of any message posted to the list to distinguish mailing list messages in mailbox summaries. For example, if a message is posted to the list with a Subject: like:

Subject: This is a message and the subject prefix is [My List] (note the trailing space), then the message will be received as follows:

Subject: [My List] This is a message

If you leave subject prefix empty, no pre fix will be added to the Subject:, Mailman is careful not to add a prefix when the header already has one, as is the case in replies for example. The prefix can also contain characters in the list’s preferred language. In this case, because of the vagaries of the email standards, you may or may not want to add a trailing space.

anonymous_list This variable allows you to turn on some features of Mailman that help create anonymity. When you set this option to Yes, Mailman will remove or replace the From:, Sender:, and Reply-To: fields of any message posted to the list.

Note that this option is simply an aid for maintaining anonymity; it doesn’t guarantee it. For example, a poster’s identity could be evident in their signature, or in other mail headers, or even in the style of the content of the message. There is little Mailman can do about this kind of identity leakage.

Reply-To header munging

This section controls what happens to the Reply-To: headers of messages posted through your list.

Reply-To: is a header that is commonly used to redirect replies to messages. Exactly what happens when your users reply to such a message depends on the mail readers your users use, and what functions they provide. Usually, there is both a “reply to sender” button and a “reply to all” button. If people use these buttons correctly, you will probably never need to munge Reply-To:, so the default values should be fine.

The three options in this section work together to provide enough flexibility to do whatever Reply-To: munging you might feel you need to do.

first_strip_reply_to This variable controls whether any Reply-To: header already present in the posted message should get removed before any other munging occurs. Stripping this header will be done regardless of whether or not Mailman will add its own Reply-To: header to the message.

If this option is set to No, then any existing Reply-To: header will be retained in the posted message. If Mailman adds its own header, it will contain addresses which are the union of the original header and the Mailman added addresses.

The mail standards specify that a message may only have one Reply-To: header, but that that header may contain multiple addresses.

reply_goes_to_list This variable controls whether Mailman will add its own Reply-To: header, and if so, what the value of that header will be (not counting original header stripping – see above).

When you set this variable to Poster, no additional Reply-To: header will be added by Mailman.  This setting is strongly recommended.

When you set this variable to This list, a Reply-To: header pointing back to your list’s posting address will be added.

When you set this variable to Explicit address, the value of the variable reply_to_address (see below) will be added. Note that this is one situation where Reply-To: munging may have a legitimate purpose. Say you have two lists at your site, an announce list and a discussion list. The announce list might allow postings only from a small number of approved users; the general list membership probably can’t post to this list. But you want to allow comments on announcements to be posted to the general discussion list by any list member, then you can set the Reply-To: header for the announce list to point to the discussion list’s posting address.

reply_to_address This is the address that will be added in the Reply-To: header if reply_goes_to_list is set to

Explicit address.

Umbrella list settings

Note that umbrella lists are deprecated and will be replaced with a better mechanism for Mailman 3.0.

umbrella_list (general): Send password reminders to, e.g., "-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.

Notifications

Mailman sends notifications to the list administrators or list members under a number of different circumstances. Most of these notifications can be configured in this section, but see the Bounce Processing and Auto-responder categories for other notifications that Mailman can send.

send_reminders By default Mailman sends all list members a monthly password reminder. This notice serves two purposes. First, it reminds people about all the lists they may be subscribed to on this domain, including the lists where their subscription may be disabled. Second, it reminds people about their passwords for these lists, as well as the URL for their personal options pages, so that they can more easily con figure their subscription options.

Some prefer not to receive these monthly reminders, and they can disable the reminders via their subscription options page. For some lists, the monthly reminders aren’t appropriate for any of the members, so you can disable them list- wide by setting the send_reminders variable to No.

welcome_msg When new members are subscribed to the list, either by their own action or the action of a list administrator, a welcome message can be sent to them. The welcome message contains some common boilerplate information, such as the name of the list, instructions for posting to the list, and the member’s subscription password. You can add additional information to the welcome message by typing the text into the welcome_msg text box. Note that because this text is sent as part of an email, it should not contain HTML.

send_welcome_msg This flag controls whether the welcome message is sent to new subscribers. Turn this off only if you plan on subscribing people manually and don't want them to know that you did so. This option is most useful for transparently migrating lists from some other mailing list manager to Mailman.

goodbye_msg Like the welcome_msg, a “goodbye” message can be sent to members when they unsubscribe from the list. Unlike the welcome message, however, there is no standard template for the goodbye message. Enter the entire goodbye message you would like unsubscribing members to receive into the goodbye_msg text box.

send_goodbye_msg This option controls whether the goodbye message is sent to unsubscribing members.

admin_immed_notify List moderators receive notifications of pending administrative actions, such as subscription or unsubscription requests that require moderator approval or posted messages that are being held for moderator approval. List moderators will always get a daily summary of such pending requests, but they can also get immediate notifications when such a request is made. The admin_immed_notify variable controls whether these immediate notifications are sent or not. It is generally a good idea to leave this set to Yes.

admin_notify_mchanges This variable controls whether the list administrators should get notifications when members join or leave the list.

respond_to_post_requests This variable controls whether the original sender of a posting gets a notice when his or her message is held for moderator approval. Approval notices are sent when mail triggers certain of the limits except routine list moderation and spam filters, for which notices are not sent. This option overrides ever sending the notice.

Additional settings

This section contains some miscellaneous settings for your mailing list.

emergency When this option is enabled, all list traffic is held for moderation. This option can be useful if subscribers to your list are exchanging a high volume of unconstructive, inflammatory messages. Turning this option on allows you to review all posts before they are distributed.

new_member_options All members have a set of subscription options which they can use to control how they receive messages and otherwise interact with the list. While the members can change these settings by logging into their personal options page, you might want to set the default for a number of the member options.

This variable presents a set of checkboxes that control the defaults for some of the member options. Conceal the member’s address specifies whether the address is displayed in the list roster. Acknowledge the member’s posting controls whether Mailman sends an acknowledgement to a member when they post a message to the list.  Do not send a copy of a member’s own post specifies whether a member posting to the list will get a copy of their own posting. Filter out duplicate messages to list members (if possible) specifies whether members who are explicitly listed as a recipient of a message (e.g., via the Cc: header) will also get a copy from Mailman.

Of course, members can always override these defaults by making changes on their Membership Options page.

administrivia This option specifies whether Mailman will search posted messages for administrivia, in other words, email commands which usually should be posted to the –request address for the list. Setting this to Yeshelps prevent such things as unsubscribe messages getting erroneously posted to the list. If a message seems to contain administrivia, it is held for moderator approval.

max_message_size This option specifies a maximum message size, in kilobytes, over which the message will be held for moderator approval. Use 0 for no limit.

host_name This option specifies the host name part of email addresses used by this list. For instance, this is the example.com part of the posting address mylist@example.com. It’s generally not a good idea to change this value, since its default value is specified when the mailing list is created. Changing this to an incorrect value could make it difficult to contact your mailing list. Also note that the URL used to visit the list’s pages can not be configured through the Web interface. This is because if you configured the URL incorrectly, you would have to have the site administrator correct it.

include_rfc2369_headers RFC 2369 is an Internet standard that describes a variety of headers that mailing list managers should add to messages to make it easier for people to interact with the list. Mail reading programs that support this standard may provide buttons for easy access to the list’s archives, or for subscribing and unsubscribing to the list. It’s generally a good idea to enable these headers as it provides for an improved user experience. These headers are often called the List-* headers.

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.

include_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 to such lists. 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.)

The Passwords Category

As mentioned above, there are two primary administrative roles for mailing lists. In this category you can specify the password for these roles.

The list owner has total control over the configuration of their mailing list (within some bounds as specified by the site administrator). Note that on this page, for historical reasons, the list owner role is described here as the list administrator.

You can set the list owner’s password by entering it in the password field on the left. You must type it twice for

confirmation. Note that if you forget this password, the only way for you to get back into your list’s administrative pages is to ask the site administrator to reset it for you (there are no password reminders for list owners).

If you want to delegate list moderation to someone else, you can enter a different moderator password in the field on the right (typed twice for confirmation). Note that if you aren’t going to delegate moderation, and the same people are going to both con figure the list and moderate postings to the list, do not enter anything into the moderator password fields. If you do enter a separate moderator password, be sure to fill in the moderator variable in the Generaloptionscategory page.

The Language Options Category

Mailman is multilingual and internationalized, meaning you can set up your list so that members can interact with it in any of a number of natural languages.

However, if your site administrator has enabled its support, you can set your list up to support any of about two dozen languages, such as German, Italian, Japanese, or Spanish. Your list members can then choose any of your supported languages as their preferred language for interacting with the list.  Such things as their member options page will be displayed in this language. Each mailing list also has its own preferred language, which is the language the list supports if no other language context is known.

These variables control the language settings for your mailing list:

preferred_language This is the list’s preferred language, which is the language that the list administrative pages will be displayed in. Also any messages sent to the list owners by Mailman will be sent in this language. This option is presented as a drop-down list containing the language enabled in the available_languages variable. If more than one language is supported, then users will be able to select their own preferences for when they interact with the list. All other interactions will be conducted in the default language. This applies to both Web-based and email- based messages, but not to email posted by list members.

available_languages This set of checkboxes contains all the natural languages that your site administrator has made available to your mailing lists. Select any language that you would either like your members to be able to view the list in, or that you’d like to be able to use in your list’s preferred_language variable. Note that the default language must be included.

encode_ascii_prefixes If your mailing list’s preferred language uses a non-ASCII character set and the subject_prefix contains non-ASCII characters, the prefix will always be encoded according to the relevant standards.  However, if your subject pre fix contains only ASCII characters, you may want to set this option to Neverto disable pre fix encoding. This can make the subject headers slightly more readable for users with mail readers that don’t properly handle non-ASCII encodings.

Note, however, that if your mailing list receives both encoded and unencoded subject headers, you might want to choose As needed. Using this setting, Mailman will not encode ASCII prefixes when the rest of the header contains only ASCII characters, but if the original header contains non-ASCII characters, it will encode the pre fi x. This avoids an ambiguity in the standards that could cause some mail readers to display extra or missing spaces between the prefix and the original header.

The Membership Management Category

The Membership Management category is unlike the other administrative categories. It doesn’t contain configuration variables or list settings. Instead, it presents a number of pages that allow you to manage the membership of you list. This includes pages for subscribing and unsubscribing members, searching for members, and changing various member-specific settings.

For details about the Membership Management options, please read the document titled Getting Started with Mailman for List Administrators, available on the technology.pitt.edu Documentation page.

The Non-digest Options Category

Mailman delivers messages to users via two modes. List members can elect to receive postings in bundles call digests one or a few times a day, or they can receive messages immediately whenever the message is posted to the list. This latter delivery mode is also called non-digest delivery.  There are two administrative categories available for separately controlling digest and non-digest delivery. You can even disable one or the other forms of delivery (but not both).

Both kinds of delivery can have list-specific headers and footers added to them which can contain other useful information you want your list members to see. For example, you can include instructions for unsubscribing, or a URL to the list’s digest, or any other information.

Non-digest deliveries can also be personalized, which means certain parts of the message can contain information tailored to the member receiving the message. For example, the To: header will contain the address of the member when deliveries are personalized. Footers and headers can contain personalized information as well, such as a link to the individual user’s options page.

In addition, personalized messages will contain extra information that Mailman can use to unambiguously track bounces from members. Ordinarily, Mailman does some pattern recognition on bounce messages to determine list members whose addresses are no longer valid, but because of the vagaries of mail systems, and the countless forwards people can put in place, it’s often the case that bounce messages don’t contain any useful information in them. Personalized messages avoid this problem by encoding information in certain headers that unambiguously identify the recipient of a message. If that message bounces, Mailman will know exactly for which member it was intended.

Note that because personalization requires extra system resources, it must be enabled by the site administrator before you can choose it.

Here are the variables that control non-digest delivery:

nondigestable This option controls whether members can receive immediate delivery.  If not, they will be forced to receive messages in digests. You can’t disable non-digest delivery if digests are already disabled.

msg_header This text box lets you enter information that will be included in the header of every non-digest message sent through the list.

See below for more information on what can go in the headers and footers.  If you leave this text box empty, no header will be added.

msg_footer Just like with the header, you can add a footer to every message.  The same rules apply to footers as apply to headers.

Headers and footers can contain any text you want. For non-English lists, the headers and footers can contain any character in the character set of the list’s preferred language. The headers and footers can also contain substitutionvariablesthat Mailman will fill in with information taken from the mailing list. These substitutions are in Python string interpolation format, where something like %(list_name)s is substituted with the name of the mailing list. Note that the trailing ‘s’ is required. (The site administrator can con fi gure lists to use a simpler interpolation format, where $list_name or

${list_name} would be substituted with the mailing list’s name. Ask your site administrator if they have con figured your list this way. )

For example, a footer containing the following text:

This is the \%(list_name)s mailing list Description: \%(description)s

might get attached to postings like so:

This is the Example mailing list

Description: An example of Mailman mailing lists

 

Here is the list of substitution variables available for your headers and footers:

real_name This is the value of the real_name configuration variable in the General options category.

list_name This is the name by which the mailing list is identified in URLs, where case is significant. In other words, it’s the posting address of the list.  (For backward compatibility, the variable internal_name is equivalent.)

host_name This is the fully qualified domain name part of the email address for this list.

web_page_url This is the base URL for contacting the list via the Web.  It can be appended with listinfo/%(list name)s to yield the general list information page for the mailing list.

descriptionThe brief description of the mailing list.

info This is the full description of the mailing list.

cgiext This is the extension added to CGI scripts.  It might be the empty string, .cgi, or something else depending on how your site is con figured.

Note that real_name, host_name, description, and info substitution variables take their values from the list configuration variables of the same name.

The Digest Options Category

Digest delivery is a way to bundle many articles together into one package, which can be delivered once per day (if there were any posted articles), or whenever the package is bigger than a specified limit. Some users may prefer this style of delivery for higher traffic lists since they will receive fewer messages.

Mailman supports two standard digest formats, and if digests are enabled, users can select which of the two formats they receive. One is MIME digests, where each message is an attachment inside a multipart/digest. This format also contains a summary table of contents, an optional header and footer, and it retains most of the headers of the original messages.

The second type is called “plaintext” digests because they are readable in mail readers that don’t support MIME. Actually, they adhere to the RFC 1153 digest standard. They retain some, but not all of the original messages, but can also include a summary and headers and footers.

Like non-digest delivery, you can enable or disable digest delivery, but you cannot disable both types of delivery. You can specify different headers and footers for digest and non-digest deliveries.

As list administrator, you may want to send an urgent message to all list members, bypassing the normal digest bundling. To do this, send the message with an Urgent: header, where the value of the header is the list administrator’s password. Non-digest members will receive the message like normal, but digest members will receive the message immediately.

They’ll also receive the message in the digest. Here are the variables that control digest delivery:

digestable The option controls whether members can receive digest deliveries or not.  If not, they will be forced to receive immediate deliveries. You can’t disable digests if non-digests are already disabled.

digest_is_default Controls which style of delivery is the default for new members.  You can choose Regular (nondigest) or Digest delivery.

mime_is_default_digest If a member is allowed to choose digests, this variable controls which is the default digest style they will receive. Plain digests are RFC 1153 format, a standard digest format.

digest_size_threshold Normally, digest members get at least one message per day if there have been any messages posted to the list. However, for high volume lists, you may want to send out digests when the size has reached a certain threshold, otherwise, the one digest they receive could be huge. This variable controls the size threshold by specifying the maximum digest size in kilobytes. Note that this threshold isn’t exact. Set this variable to zero to specify that there is no size threshold, in which case no more than one digest will be sent out per day.

digest_send_periodic This variable actually controls whether or not a digest is sent daily when the size threshold has not yet been met. If this variable is set to No, then digests will only be sent when they are bigger than the digest_size_threshold.

digest_header This text box lets you enter information that will be included in the header of every digest message sent through the list. The same information can go in this header as can go in the msg_header, except for the personalization variables.

digest_footer Just like with the header, you can add a footer to every message. The same rules apply to digest footers as apply to digest headers.

digest_volume_frequency Each digest is numbered with a volume and an issue. This variable controls how often a new digest volume is sent. When the digest volume number is incremented, the issue number is reset to 1.

_new_volume This is an action variable, which forces an increment of the volume number as soon as you submit the form.

Setting this option instructs Mailman to start a new volume with the next digest sent out.

_send_digest_now This action variable sends a digest immediately. Select Yes, submit the form, and the current digest is packaged up and sent to digest members, regardless of size (there has to be at least one message in the digest).

The Privacy Options Category

The Privacy category lets you control how much of the list’s information is public, as well as who can send messages to your list. It also contains some spam detection fi lters. Note that this section is not used to control whether your list’s archives are public or private.

There are four sub-categories:

  • Subscription rules – the rules for joining and leaving your mailing list
  • Sender filters – the rules for who may post messages to your list
  • Recipient filters – moderation rules based on the recipient of the message
  • Spam filters – some regular expression-based rules for header matching

The sender, recipient, and spam filtering rules are part of the general list moderation features of Mailman. When a message is posted to the list, it is matched against a number of criteria, the outcome of which determines whether the message is

re flected to the membership or not. In general, the outcome is one of four states:

  • Approved or Accepted – the message may be sent on to the members of the mailing list.
  • Hold – the message will be held for moderator approval. The list owners and moderators will then have to explicitly approve the message before the list members will see it.
  • Reject – the message is bounced back to the original sender, often with a notice containing the reason the message was rejected. The list members never see rejected messages.
  • Discard – the message is simply thrown away without further processing.

Many of the fields in this section are text boxes accepting addresses, one per line. Unless otherwise noted, these also accept regular expressions that will be matched against an address if the line begins with a ˆ(caret) character.

Subscription rules

This subcategory controls the rules for exposing the existence of this list, and for what new members must do in order to subscribe to the list.

advertised This option controls whether this list will show up in the list overview for the site. Normally, an overview contains the name and short description of every mailing list in the virtual domain. By setting this variable to No, it will not show up in this overview, nor will it show up in the administrative overview. The only way then to find the list is to know its name.

subscribe_policy This option controls the steps that a new member must take to join the list. The available options may differ based on some defaults that the site administrator chooses. They are as follows:

  • Confirm – An email confirmation step is required before the address is added to the list. When a member requests subscription, Mailman will send a confirmation message to the requesting address. This mail-back confirmation contains a unique identifier, which the requester can present to Mailman in order to con firm their subscription. This can be done either by replying to the mail-back, or by visiting the URL in the mail-back message. The URL points to a page that lets the user either discard or confirm their request.
  • Require approval – All subscription requests are held for approval of the list moderator. No mail-back confirmation is sent, but the list admins will receive a message indicating that approval is pending.
  • Confirm and approve – Here, a mail-back notice must first be confirmed by the requester. Once confirmed, the list moderator must then approve the request. This is the most secure method for users to subscribe since it both

verifies the requesting address and forces the list moderators to approve the request.

unsubscribe_policy Specifies whether the list moderator’s approval is required for unsubscription requests. Nois highly recommended, since it is standard practice to allow people to leave a mailing list whenever they want (i.e., opt-out). Yes is useful in some specialized contexts. For example, you may not want to allow employees to unsubscribe from the company newsletter.

ban_list This contains a list of addresses (or regular expressions), one per line, that are banned from ever subscribing to your mailing list. If a match occurs during the subscription process, the request will be automatically rejected, and the requester will get a rejection notice. You can use this to permanently ban troublesome posters to a members-only list.

private_roster This specifies who is allowed to view the roster of member addresses. If you choose Anyone, then the list membership is completely public. You can limit exposure of the roster to just list members, or just to the list administrators. In the former case, a user must enter a valid member’s address and password before they can view the roster. In the latter case, a list administrator’s password must be entered.

obscure_addresses Controls whether some simple steps are taken to disguise addresses when member addresses are included on Web pages. This should reduce the opportunity for email address harvesting by spammers, although it probably does not eliminate it.

Sender filters

When a message is posted to the list, a series of moderation criteria are applied to determine the disposition of the message. This section contains the moderation controls for postings from both members and non-members.

default_member_moderation Member postings are held for moderation if their moderationfl agis turned on. Note that only the list administrators can change the value of a member’s moderation flag.

You can control whether new members get their moderation flag turned on or off by default when they subscribe to the list. By turning this flag off by default, postings by members will be allowed without further intervention (barring other restrictions such as size or implicit recipient lists – see below).  By turning the flag on, you can quarantine new member postings to make sure that they meet your criteria for netiquette, topicality, etc. Once you determine that the new member understands the community’s posting rules, you can turn off their moderation flag and let their postings go through unstopped.

E-newsletter style lists can also be set up by using the moderation flag. By setting the member_moderation_action to Reject, and by turning off the moderation flag for just the few approved senders, your list will operate in essentially a one-way direction. Note that you’d also need to reject or discard postings from non-members.

member_moderation_action This is the action to take for postings from a member whose moderation flag is set. For typical discussion lists, you’ll likely set this to Holdso that the list moderator will get a chance to manually approve, reject, or discard the message. For e-newsletter and announcement lists, you might want to set this to Rejector Discard.

Note that when a moderated member posts to your list, and the member_moderation_action is set to Hold, the message will appear on the administrative requests page. When you dispose of the message, you will be given an opportunity to clear the moderation flag at the same time. If you’re quarantining new posts, this makes it very convenient to both approve a new member’s post and de-moderate them at the same time.

member_moderation_notice When a member’s moderation flag is turned on and member_moderation_action is

Reject, this variable contains the text sent in the rejection notice.

The next batch of variables controls what happens when non-members post messages to the list. Each of these accepts one email address per line; regular expressions are allowed if the line starts with the ˆ(caret) character. These address lists are always consulted in the order in which they’re presented on this page (i.e., accepts first, followed by holds, rejections, and discards).

accept_these_nonmembers Postings from non-members whose addresses match this list are accepted, barring other list restrictions due to size, implicit recipients, etc. You might want to add alternative addresses of approved posters to this list.

hold_these_nonmembers Postings from non-members whose addresses match this list are held for moderator approval.

reject_these_nonmembers Postings from non-members whose addresses match this list are rejected, i.e. bounced back to the original sender.  There currently is no way to add additional text to the rejection message.

discard_these_nonmembers Postings from non-members whose addresses match this list are discarded, with no bounce back message. You might want to add the addresses of known spammers to this list.

generic_nonmember_action This variable controls what happens to non-member posts when the address of the sender doesn’t match any of the above four lists. If you set this to Hold, the posting will appear on the administrative requests page, and you will be given an opportunity to add the non-member to one of the above four lists at the same time you dispose of the held message.

forward_auto_discards When messages from non-members are discarded, either because the sender address matched discard_these_nonmembers, or because generic_nonmember_action is Discard, you can choose whether such messages are forwarded to the list administrators.

Recipient Filters

The variables in this section control various filters based on the recipient of the message.

require_explicit_destination This controls whether the mailing list posting address must be explicitly named in the To: or Cc: recipient lists. The main reason why it wouldn’t is if the message was blind-carbon-copied (i.e., Bcc:’d) to the list. Spammers like to do this, but sometimes legitimate messages are forwarded to the list this way.

If the list is not explicitly addressed and this setting is turned on, the message will be held for moderator approval.

 

acceptable_aliases This is the list of alternative addresses that are acceptable as a list posting address when require_explicit_destination is enabled. This is useful for times when there are aliases for the main posting address (e.g.,  help@list.pitt.edu may be an alias for help-list@list.pitt.edu).

max_num_recipients This is the maximum number of explicit recipients that are allowed on the posted  message. Spammers sometimes send messages with lots of explicit recipients, so setting this number to a reasonable value may cut down on spam. If a posting has or exceeds this number of recipients, it is held for admin approval. Use 0 for no ceiling.

Spam Filters

This section provides some adjuncts to spam fighting tools; it doesn’t replace dedicated anti-spam tools such as Ad-Aware or Spybot Search & Destroy.

bounce_matching_headersThis variable contains header regular expressions, one per line, and if any of a message’s headers matches one of these patterns, it will be held for moderation. The format is a colon-separated header and value, where the header is case insensitive and the value is any valid Python regular expression.  Lines that start with

# are ignored.

This variable can be used to catch known spammers by writing regexps that match against To: or Cc: lines, or known- bad Message-ID:s. Perhaps more useful, though, are patterns that match headers added by spam detection tools higher up in the tool chain. For example, you might configure SpamAssassin to add an X-Spam-Score: header with between zero and 5 stars depending on the spam score. Then you can add a line to this variable like:

X-Spam-Score: [*]{3,5}

This line will match from 3 to 5 stars in the value of this field.

The Bounce Processing Category

These policies control the automatic bounce processing system in Mailman. Here’s an overview of how it works:

When a bounce is received, Mailman tries to extract two pieces of information from the message: the address of the member for whom the message was intended, and the severity of the problem causing the bounce. The severity can be either hard  for fatal errors, or soft for transient errors. When in doubt, a hard severity is used.

If no member address can be extracted from the bounce, then the bounce message is usually discarded. Every member has a bounce score, initialized at zero, and every time we encounter a bounce from a member we increment that member’s score. Hard bounces increment by 1 while soft bounces increment by 0.5. We only increment the bounce score once per day, so even if we receive ten hard bounces from a member per day, their score will increase by only 1 for that day.

When a member’s bounce score is greater than the bounce score threshold (see below), the member’s subscription is disabled. Once disabled, the member will not receive any postings from the list until their membership is explicitly re- enabled, either by the list administrator or the user. However, they will receive occasional reminders that their membership has been disabled, and these reminders will include information about how to re-enable their membership. You can control both the number of reminders the member will receive and the frequency with which these reminders are sent.

There is one other important configuration variable; after a certain period of time – during which no bounces from the member are received – the bounce information is considered stale and discarded. Thus by adjusting this value and the score threshold, you can control how quickly bouncing members are disabled. You should tune both of these to the frequency  and traf fi c volume of your list.

bounce_processing Specifies whether this list should do automatic bounce processing.

bounce_score_threshold This is the bounce score above which a member’s subscription will be automatically disabled. When the subscription is re-enabled, their bounce score will be reset to zero. This value can be a floating point number.

bounce_info_stale_after The number of days after which a member’s bounce information is considered stale. If no new bounces have been received in the interim, the bounce score is reset to zero. This value must be an integer.

bounce_you_are_disabled_warnings The number of notices a disabled member will receive before their address is removed from the mailing list’s roster. Set this to 0 to immediately remove an address from the list once their bounce score exceeds the threshold. This value must be an integer.

bounce_you_are_disabled_warnings_interval The number of days between each disabled notification.

bounce_unrecognized_goes_to_list_owner This variable controls whether unrecognized bounces are discarded or forwarded on to the list administrator. The bounce detector isn’t perfect, although personalization can make it much more accurate. The list owner may want to receive unrecognized bounces so that they can manually disable or remove such members.

bounce_notify_owner_on_disable This option controls whether the list owner is notified when a member’s subscription is automatically disabled due to their bounce threshold being reached.

bounce_notify_owner_on_removal This option controls whether the list owner is notified when a member is removed from the list after their disabled notifications have been exhausted.

The Archiving Options Category

Mailman comes with a built-in Web-based archiver called Pipermail, although it can be con figured to use external, third party archivers.

archive This option tells Mailman whether or not to archive messages it receives. Turn this off if you don’t want to archive messages. Note that senders can control whether their own posts are archived on an individual, per-message basis. If the posted message has an X-No-Archive: header (regardless of value), or an X-Archive: header with a value of No (case insensitive), then the message will not be archived, although it will be treated as normal in all other ways.

archive_private Controls whether archives are private or public. Private archives require a valid member address and password, or a list administrator password in order to access them. This option has no effect when a third party archiver is used.

archive_volume_frequency Controls how messages are split in the archive. The most common option is Monthly, meaning a new archive volume is started every month. Very high volume lists may want a shorter frequency (e.g., Weekly or Daily) whereas lower volume lists may want a longer frequency (e.g., Yearly). This option has no effect when a third party archiver is used.