2.1.1 General list personality

From feb0c79d073433101d19cab305d8427d855cd6b6 Mon Sep 17 00:00:00 2001 From: Mark Sapiro Date: Tue, 10 Feb 2015 15:18:45 -0800 Subject: Added two previously renamed mailman-admin/*html files. --- doc/mailman-admin/general-personality.html | 221 ++++++++++++++++++++++++++ doc/mailman-admin/sender-filters.html | 246 +++++++++++++++++++++++++++++ 2 files changed, 467 insertions(+) create mode 100644 doc/mailman-admin/general-personality.html create mode 100644 doc/mailman-admin/sender-filters.html (limited to 'doc') diff --git a/doc/mailman-admin/general-personality.html b/doc/mailman-admin/general-personality.html new file mode 100644 index 00000000..4e5a712c --- /dev/null +++ b/doc/mailman-admin/general-personality.html @@ -0,0 +1,221 @@ + + + + + + + + + + + + + + +2.1.1 General list personality + + + + + +

+
+2.1.1 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 posting name and a real + name. The posting name shows up in urls and in email addresses, + e.g. the mylist in mylist@example.com. 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. The real name can differ from the posting name by + case only. For example, if the posting name is mylist, the + real name can be MyList. + +

owner

This variable contains a list of email addresses, one address per + line, of the list owners. These addresses are used whenever the + list owners need to be contacted, either by the system or by end + users. Often, these addresses are used in combination with the + moderator addresses (see below). + +

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. For example, when + you email mylist-owner@example.com, 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 contents 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. + +

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. However, blank lines will be automatically + converted into paragraph breaks. Preview your HTML though, + because unclosed or invalid HTML 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. + 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 like so: + +

+    Subject: [My List] This is a message
+

+ +

+If you leave subject_prefix empty, no prefix 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 vagarities of the + email standards, you may or may not want to add a trailing space. + +

from_is_list

This applies to all non-digest messages sent by the list. For settings + that apply only to messages whose From: domain publishes a + DMARC p=reject or p=quarantine policy, see the + dmarc_moderaction_action description in section + 2.7. + +

+If set to Munge From, it replaces the From: header + address with the list's posting address to mitigate issues stemming + from the original From: domain's DMARC or similar policies + and puts the original From: address in a + Reply-To: header. + +

+If set to Wrap Message it wraps the original message as a MIME + subpart of an outer message with From: and + Reply-To: headers as above. + +

anonymous_list

This variable allows you to turn on some simple anonymizing + features of Mailman. 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 anonymization, 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's little Mailman + can do about this kind of identity leakage. +

+ +

+ + + + diff --git a/doc/mailman-admin/sender-filters.html b/doc/mailman-admin/sender-filters.html new file mode 100644 index 00000000..5280dda0 --- /dev/null +++ b/doc/mailman-admin/sender-filters.html @@ -0,0 +1,246 @@ + + + + + + + + + + + + + + +2.7.2 Sender filters + + + + + +

+
+2.7.2 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 modeation controls for postings from both members and +non-members. + +

default_member_moderation

Member postings are held for moderation if their moderation + flag is 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 who's + moderation flag is set. For typical discussion lists, you'll + likely set this to Hold so 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 + Reject or 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 group of settings control messages whose From: +domain publishes a DMARC p=reject or p=quarantine policy. + +

dmarc_moderation_action: These actions, Accept, Munge From, Wrap Message, + Reject and Discard apply only to messages whose + From: domain publishes a DMARC p=reject or optionally + (see the next setting) p=quarantine policy. If the message is + From: such a domain and this action is other than + Accept, this action applies to the message. Otherwise the + from_is_list setting in section 2.1 + applies. See the from_is_list setting in section + 2.1 for a description of the Munge From + and Wrap Message actions. +
dmarc_quarantine_moderation_action: If this is set to Yes, the above dmarc_moderation_action + applies to messages with From: domain DMARC policy + p=quarantine as well as p=reject. +
dmarc_moderation_notice: When dmarc_moderation_action applies and is Reject, + this variable contains the text sent in the rejection notice. If + empty, a generic notice mentioning DMARC is sent. +

+ +

+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 lsit administrators or + not. +

+ +

+ + + + -- cgit v1.2.3