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.
+
+# Each list member has a moderation flag which says whether messages
+# from the list member can be posted directly to the list, or must first
+# be approved by the list moderator. When the moderation flag is turned
+# on, list member postings must be approved first. You, the list
+# administrator can decide whether a specific individual's postings will
+# be moderated or not.
+#
+# When a new member is subscribed, their initial moderation flag takes
+# its value from this option. Turn this option off to accept member
+# postings by default. Turn this option on to, by default, moderate
+# member postings first. You can always manually set an individual
+# member's moderation bit by using the membership management screens.
+#
+# legal values are:
+# 0 = "No"
+# 1 = "Yes"
+default_member_moderation = 0
+
+# Hold -- this holds the message for approval by the list moderators.
+#
+# Reject -- this automatically rejects the message by sending a bounce
+# notice to the post's author. The text of the bounce notice can be configured by
+# you.
+#
+# Discard -- this simply discards the message, with no notice sent to
+# the post's author.
+#
+#
+# legal values are:
+# 0 = "Hold"
+# 1 = "Reject"
+# 2 = "Discard"
+member_moderation_action = 1
+
+# When a post from a non-member is received, the message's sender is
+# matched against the list of explicitly accepted,
+# held, rejected (bounced), and discarded
+# addresses. If no match is found, then this action is taken.
+#
+# legal values are:
+# 0 = "Accept"
+# 1 = "Hold"
+# 2 = "Reject"
+# 3 = "Discard"
+generic_nonmember_action = 2
+
+# Should messages from non-members, which are automatically discarded,
+# be forwarded to the list moderator?
+#
+# legal values are:
+# 0 = "No"
+# 1 = "Yes"
+forward_auto_discards = 1
+
+## Bounce options
+#
+# 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 the message
+# was intended for, and the severity of the problem causing the bounce.
+# The severity can be either hard or soft meaning
+# either a fatal error occurred, or a transient error occurred. When in
+# doubt, a hard severity is used.
+#
+# If no member address can be extracted from the bounce, then the
+# bounce is usually discarded. Otherwise, each member is assigned a
+# bounce score and every time we encounter a bounce from this
+# member we increment the 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, the 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 traffic volume of your list.
+
+# By setting this value to No, you disable all automatic bounce
+# processing for this list, however bounce messages will still be
+# discarded so that the list administrator isn't inundated with them.
+#
+# legal values are:
+# 0 = "No"
+# 1 = "Yes"
+bounce_processing = 1
+
+## Archive options
+#
+# List traffic archival policies.
+
+# Is archive file source for public or private archival?
+#
+# legal values are:
+# 0 = "public"
+# 1 = "private"
+archive_private = 1
--
cgit v1.2.3