# href="?VARHELP=privacy/sender/generic_nonmember_action">general
# non-member rules.
#
# In the text boxes below, add one address per line; start the line
# with a ^ character to designate a # "https://docs.python.org/2/library/re.html" >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 = 1
# If a member posts this many times, within a period of time the member
# is automatically moderated. Use 0 to disable. See # href="?VARHELP=privacy/sender/member_verbosity_interval"
# >member_verbosity_interval for details on the time period.
#
# This is intended to stop people who join a list or lists and then use
# a bot to send many spam messages in a short interval.
#
# Be careful when using this setting. If it is set too low, this can be
# triggered by a single post cross-posted to multiple lists or by a
# single post to an umbrella list.
member_verbosity_threshold = 0
# If a member's total posts to all lists in this installation with
# member_verbosity_threshold enabled reaches this list's
# member_verbosity_threshold, the member is automatically moderated on
# this list.
#
# Posts which are counted towards this list's member_verbosity_threshold
# are all posts to any list with member_verbosity_threshold enabled that
# arrived within that list's member_verbosity_interval.
member_verbosity_interval = 300
# 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 # href="?VARHELP=privacy/sender/member_moderation_notice" >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
# Text to include in any # href="?VARHELP/privacy/sender/member_moderation_action" >rejection
# notice to be sent to moderated members who post to this list.
# Munge From -- applies the # href="?VARHELP=general/from_is_list">from_is_list Munge From
# transformation to these messages.
#
# Wrap Message -- applies the # href="?VARHELP=general/from_is_list">from_is_list Wrap Message
# transformation to these messages.
#
# Reject -- this automatically rejects the message by sending a bounce
# notice to the post's author. The text of the bounce notice can be # href="?VARHELP=privacy/sender/dmarc_moderation_notice" >configured by
# you.
#
# Discard -- this simply discards the message, with no notice sent to
# the post's author.
#
#
# This setting takes precedence over the # href="?VARHELP=general/from_is_list"> from_is_list setting if the
# message is From: an affected domain and the setting is other than
# Accept.
#
# legal values are:
# 0 = "Accept"
# 1 = "Munge From"
# 2 = "Wrap Message"
# 3 = "Reject"
# 4 = "Discard"
dmarc_moderation_action = 1
# No -- this applies dmarc_moderation_action to only those posts From: a
# domain with DMARC p=reject. This is appropriate if you are concerned
# about bounced messages, but want to apply dmarc_moderation_action to
# as few messages as possible. Yes -- this applies
# dmarc_moderation_action to posts From: a domain with DMARC p=reject or
# p=quarantine. If a message is From: a domain with DMARC p=quarantine
# and dmarc_moderation_action is not applied (this set to No) the
# message will likely not bounce, but will be delivered to recipients'
# spam folders or other hard to find places.
#
# legal values are:
# 0 = "No"
# 1 = "Yes"
dmarc_quarantine_moderation_action = False
# No -- this applies dmarc_moderation_action to only those posts From: a
# domain with DMARC p=reject and possibly p=quarantine depending on the
# setting of dmarc_quarantine_moderation_action. Yes -- this applies
# dmarc_moderation_action to posts From: a domain with DMARC p=none if
# dmarc_moderation_action is Munge From or Wrap Message and
# dmarc_quarantine_moderation_action is Yes. The intent of this setting
# is to eliminate failure reports to the owner of a domain that
# publishes DMARC p=none by applying the message transformations that
# would be applied if the domain's DMARC policy were stronger.
#
# legal values are:
# 0 = "No"
# 1 = "Yes"
dmarc_none_moderation_action = False
# Text to include in any # href="?VARHELP=privacy/sender/dmarc_moderation_action" >rejection
# notice to be sent to anyone who posts to this list from a domain with
# a DMARC Reject Policy.
dmarc_moderation_notice = ''
# Postings from any of these addresses will automatically apply any
# DMARC action mitigation. This can be utilized to automatically wrap
# or munge postings from known addresses or domains that might have
# policies rejecting external mail From: themselves.
#
# Add member addresses one per line; start the line with a ^ character
# to designate a regular expression match.
dmarc_moderation_addresses = []
# A wrapped message will either be a multipart/mixed message with up to
# four sub-parts; a text/plain part containing msg_header, a text/plain
# part containing dmarc_wrapped_message_text, a message/rfc822 part
# containing the original message and a text/plain part containing
# msg_footer, or a message/rfc822 message containing only the original
# message if none of the other parts are applicable.
dmarc_wrapped_message_text = ''
# If two poster addresses with the same local part but different domains
# are to be considered equivalents for list membership tests, the
# domains are put here. The format is one or more groups of equivalent
# domains. Within a group, the domains are separated by commas and
# multiple groups are separated by semicolons. White space is ignored.
# For example: example.com,mail.example.com;mac.com,me.com,icloud.com
#
# In this example, if user@example.com is a list member, a post from
# user@mail.example.com will be treated as if it is from
# user@example.com for list membership/moderation purposes, and
# likewise, if user@me.com is a list member, posts from user@mac.com or
# user@icloud.com will be treated as if from user@me.com. Note that the
# poster's address is first tested for list membership, and the
# equivalent domain addresses are only tested if the poster's address is
# not that of a member. Also note that moderation of the equivalent
# domain address will apply to the post, but other options such as 'ack'
# or 'not metoo' will not.
equivalent_domains = ''
# Postings from any of these non-members will be automatically accepted
# with no further moderation applied. Add member addresses one per
# line; start the line with a ^ character to designate a regular
# expression match. A line consisting of the @ character followed by a
# list name specifies another Mailman list in this installation, all of
# whose member addresses will be accepted for this list.
accept_these_nonmembers = ['mona@encs.concordia.ca', 'iliada@encs.concordia.ca']
# Postings from any of these non-members will be immediately and
# automatically held for moderation by the list moderators. The sender
# will receive a notification message which will allow them to cancel
# their held message. Add member addresses one per line; start the line
# with a ^ character to designate a regular expression match.
hold_these_nonmembers = []
# Postings from any of these non-members will be automatically rejected.
# In other words, their messages will be bounced back to the sender with
# a notification of automatic rejection. This option is not appropriate
# for known spam senders; their messages should be # href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
# discarded.
#
# Add member addresses one per line; start the line with a ^ character
# to designate a regular expression match.
reject_these_nonmembers = []
# Postings from any of these non-members will be automatically
# discarded. That is, the message will be thrown away with no further
# processing or notification. The sender will not receive a
# notification or a bounce, however the list moderators can optionally
# receive
# copies of auto-discarded messages..
#
# Add member addresses one per line; start the line with a ^ character
# to designate a regular expression match.
discard_these_nonmembers = []
# When a post from a non-member is received, the message's sender is
# matched against the list of explicitly # href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
# held, # >rejected (bounced), and # href="?VARHELP=privacy/sender/discard_these_nonmembers" >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
# Text to include in any rejection notice to be sent to non-members who
# post to this list. This notice can include the list's owner address by
# %(listowner)s and replaces the internally crafted default message.
## Privacy options
#
# This section allows you to configure various filters based on the
# recipient of the message.
# 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
#
#
# The relaying address has the same name, or
#
# The relaying address name is included on the options that specifies
# acceptable aliases for the list.
#
#
#
# legal values are:
# 0 = "No"
# 1 = "Yes"
require_explicit_destination = True
# 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.
acceptable_aliases = ''
# If a posting has this number, or more, of recipients, it is held for
# admin approval. Use 0 for no ceiling.
max_num_recipients = 10
## Privacy options
#
# 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.
#
# 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.
header_filter_rules = []
# 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 '@public.com' 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.
bounce_matching_headers =
To see the collection of prior postings to the list,
visit the Student-services-communications_ug_orient-eca
Archives.
(The current archive is only available to the list
members.)
