-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.
+This section contains some miscellaneous settings for your mailing
+list.
-
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 configure their subscription options.
+
emergency
+
When this option is enabled, all list traffic is emergency
+ moderated, i.e. held for moderation. Turn this option on when
+ your list is experiencing a flamewar and you want a cooling off
+ period.
-Some people get annoyed with 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.
+
+
new_member_options
+
Each member has 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. You can do that with
+ this variable, but see also the other categories for other member
+ defaults you can set.
-
-
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.
+This variable presents a set of checkboxes which control the
+ defaults for some of the member options. Conceal the
+ member's address specifies whether or not the address is
+ displayed in the list roster. Acknowledge the member's
+ posting controls whether or not 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.
-
-
send_welcome_msg
-
This flag controls whether or not the welcome message is sent to
- new subscribers.
+Of course, members can always override these defaults by making
+ changes on their membership options page.
-
goodbye_msg
-
Like the welcome_msg, a ``goodbye'' message can be sent to
- members when they unsubscribe from the list. Unlike the welcome
- message, there's no boilerplate for the goodbye message. Enter
- the entire goodbye message you'd like unsubscribing members to
- receive into the goodbye_msg text box.
+
administrivia
+
This option specifies whether Mailman will search posted messages
+ for admimistrivia, in other words, email commands which
+ usually should be posted to the -request address for the
+ list. Setting this to Yes helps prevent such things as
+ unsubscribe messages getting erroneously posted to the list.
-
-
send_goodbye_msg
-
This flag controls whether or not the goodbye message is sent to
- unsubscribing members.
+If a message seems to contain administrivia, it is held for
+ moderator approval.
-
admin_immed_notify
-
List moderators get 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's generally a good
- idea to leave this set to Yes.
+
max_message_size
+
This option specifies a maximum message size, in kilobytes, over
+ which the message will be held for moderator approval.
-
admin_notify_mchanges
-
This variable controls whether the list administrators should get
- notifications when members join or leave the list.
+
host_name
+
This option specifies the host name part of email addresses used
+ by this list. For example, 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 not that the url used to visit
+ the list's pages is not configurable through the web interface.
+ This is because if you messed it up, you'd have to have the site
+ administrator fix it.
-
respond_to_post_requests
-
This variable controls whether the original sender of a posting
- gets a notice when their message is held for moderator approval.
+
include_rfc2369_headers
+
RFC 2369 is an internet standard that describes a bunch of
+ headers that mailing list managers should add to messages to make
+ it easier for people to interact with the list. Mail reading
+ programs which 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.)
+
