This section allows you to configure subscription and membership exposure policy. You can also control whether this list is public or not. See also the Archival Options section for separate archive-related privacy settings.

Subscription rules

Subscribing
Advertise this list when people ask what lists are on this machine? advertised (privacy): Advertise this list when people ask what lists are on this machine?
What steps are required for subscription? subscribe_policy (privacy): What steps are required for subscription?

Confirm (*) - email confirmation required
Require approval - require list administrator approval for subscriptions
Confirm and approve - both confirm and approve

(*) when someone requests a subscription, Mailman sends them a notice with a unique subscription request number that they must reply to in order to subscribe.
This prevents mischievous (or malicious) people from creating subscriptions for others without their consent.

Is the list moderator's approval required for unsubscription requests? (No is recommended) unsubscribe_policy (privacy): Is the list moderator's approval required for unsubscription requests? (Nois recommended)

When members want to leave a list, they will make an unsubscription request, either via the web or via email. Normally it is best for you to allow open unsubscriptions so that users can easily remove themselves from mailing lists (they get really upset if they can't get off lists!).

For some lists though, you may want to impose moderator approval before an unsubscription request is processed. Examples of such lists include a corporate mailing list that all employees are required to be members of.

Ban list
List of addresses which are banned from membership in this mailing list. ban_list (privacy): List of addresses which are banned from membership in this mailing list.

Addresses in this list are banned outright from subscribing to this mailing list, with no further moderation required. Add addresses one per line; start the line with a ^ character to designate a regular expression match.

Membership exposure
Who can view subscription list? private_roster (privacy): Who can view subscription list?

When set, the list of subscribers is protected by member or admin password authentication.

Show member addresses so they're not directly recognizable as email addresses? obscure_addresses (privacy): Show member addresses so they're not directly recognizable as email addresses?

Setting this option causes member email addresses to be transformed when they are presented on list web pages (both in text and as links), so they're not trivially recognizable as email addresses. The intention is to prevent the addresses from being snarfed up by automated web scanners for use by spammers.

Sender Filters

When a message is posted to the list, a series of moderation steps are take to decide whether the a moderator must first approve the message or not. This section contains the controls for moderation of both member and non-member postings.

Member postings are held for moderation if their moderation flag is turned on. You can control whether member postings are moderated by default or not.

Non-member postings can be automatically accepted, held for moderation, rejected (bounced), or discarded, either individually or as a group. Any posting from a non-member who is not explicitly accepted, rejected, or discarded, will have their posting filtered by the general non-member rules.

In the text boxes below, add one address per line; start the line with a ^ character to designate a Python regular expression. When entering backslashes, do so as if you were using Python raw strings (i.e. you generally just use a single backslash).

Note that non-regexp matches are always done first.

Recipient filters

This section allows you to configure various filters based on the recipient of the message.

Must posts have list named in destination (to, cc) field (or be among the acceptable alias names, specified below)? require_explicit_destination (privacy): Must posts have list named in destination (to, cc) field (or be among the acceptable alias names, specified below)?

Many (in fact, most) spams do not explicitly name their myriad destinations in the explicit destination addresses - in fact often the To: field has a totally bogus address for obfuscation. The constraint applies only to the stuff in the address before the '@' sign, but still catches all such spams.

The cost is that the list will not accept unhindered any postings relayed from other addresses, unless

  1. The relaying address has the same name, or
  2. The relaying address name is included on the options that specifies acceptable aliases for the list.
Alias names (regexps) which qualify as explicit to or cc destination names for this list. acceptable_aliases (privacy): Alias names (regexps) which qualify as explicit to or cc destination names for this list.

Alternate addresses that are acceptable when `require_explicit_destination' is enabled. This option takes a list of regular expressions, one per line, which is matched against every recipient address in the message. The matching is performed with Python's re.match() function, meaning they are anchored to the start of the string.

For backwards compatibility with Mailman 1.1, if the regexp does not contain an `@', then the pattern is matched against just the local part of the recipient address. If that match fails, or if the pattern does contain an `@', then the pattern is matched against the entire recipient address.

Matching against the local part is deprecated; in a future release, the pattern will always be matched against the entire recipient address.

Ceiling on acceptable number of recipients for a posting. max_num_recipients (privacy): Ceiling on acceptable number of recipients for a posting.

If a posting has this number, or more, of recipients, it is held for admin approval. Use 0 for no ceiling.

Spam filters

This section allows you to configure various anti-spam filters posting filters, which can help reduce the amount of spam your list members end up receiving.

Header filters
Filter rules to match against the headers of a message. header_filter_rules (privacy): Filter rules to match against the headers of a message.

Each header filter rule has two parts, a list of regular expressions, one per line, and an action to take. Mailman matches the message's headers against every regular expression in the rule and if any match, the message is rejected, held, or discarded based on the action you specify. Use Defer to temporarily disable a rule. You can have more than one filter rule for your list. In that case, each rule is matched in turn, with processing stopped after the first match. Note that headers are collected from all the attachments (except for the mailman administrivia message) and matched against the regular expressions. With this feature, you can effectively sort out messages with dangerous file types or file name extensions.

Legacy anti-spam filters
Hold posts with header value matching a specified regexp. bounce_matching_headers (privacy): Hold posts with header value matching a specified regexp.

Use this option to prohibit posts according to specific header values. The target value is a regular-expression for matching against the specified header. The match is done disregarding letter case. Lines beginning with '#' are ignored as comments.

For example:

to: .*@public.com 
says to hold all postings with a To:mail header containing This email address is being protected from spambots. You need JavaScript enabled to view it.' anywhere among the addresses.

Note that leading whitespace is trimmed from the regexp. This can be circumvented in a number of ways, e.g. by escaping or bracketing it.

Specials

Tired of Mailbox Size Issues?
Get Hosted Exchange
Now with 100GB Mailboxes
Ask about our Free Migration Offer


Need Email Archiving?
Get StarMaille
Email Archiving and Protection