[prev in list] [next in list] [prev in thread] [next in thread]
List: mailman-cvs
Subject: [Mailman-checkins] [Branch ~mailman-coders/mailman/2.1] Rev 1538: Added two previously renamed mailm
From: noreply () launchpad ! net
Date: 2015-02-10 23:36:19
Message-ID: 20150210233619.3574.55709.launchpad () ackee ! canonical ! com
[Download RAW message or body]
------------------------------------------------------------
revno: 1538
committer: Mark Sapiro <mark@msapiro.net>
branch nick: 2.1
timestamp: Tue 2015-02-10 15:18:45 -0800
message:
Added two previously renamed mailman-admin/*html files.
added:
doc/mailman-admin/general-personality.html
doc/mailman-admin/sender-filters.html
--
lp:mailman/2.1
https://code.launchpad.net/~mailman-coders/mailman/2.1
Your team Mailman Checkins is subscribed to branch lp:mailman/2.1.
To unsubscribe from this branch go to https://code.launchpad.net/~mailman-c=
oders/mailman/2.1/+edit-subscription
["revision-diff.txt" (revision-diff.txt)]
=== added file 'doc/mailman-admin/general-personality.html'
--- doc/mailman-admin/general-personality.html 1970-01-01 00:00:00 +0000
+++ doc/mailman-admin/general-personality.html 2015-02-10 23:18:45 +0000
@@ -0,0 +1,221 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' />
+<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration \
Manual' /> +<link rel='contents' href='contents.html' title="Contents" />
+<link rel='last' href='about.html' title='About this document...' />
+<link rel='help' href='about.html' title='About this document...' />
+<link rel="next" href="node11.html" />
+<link rel="prev" href="node9.html" />
+<link rel="parent" href="node9.html" />
+<link rel="next" href="node11.html" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name='aesop' content='information' />
+<title>2.1.1 General list personality</title>
+</head>
+<body>
+<div class="navigation">
+<div id='top-navigation-panel' xml:id='top-navigation-panel'>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td class='online-navigation'><a rel="prev" title="2.1 the General Options"
+ href="node9.html"><img src='previous.png'
+ border='0' height='32' alt='Previous Page' width='32' /></a></td>
+<td class='online-navigation'><a rel="parent" title="2.1 the General Options"
+ href="node9.html"><img src='up.png'
+ border='0' height='32' alt='Up one Level' width='32' /></a></td>
+<td class='online-navigation'><a rel="next" title="2.1.2 reply-to header munging"
+ href="node11.html"><img src='next.png'
+ border='0' height='32' alt='Next Page' width='32' /></a></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td class='online-navigation'><a rel="contents" title="Table of Contents"
+ href="contents.html"><img src='contents.png'
+ border='0' height='32' alt='Contents' width='32' /></a></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+</tr></table>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node9.html">2.1 The General Options</a>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node11.html">2.1.2 Reply-To header munging</a>
+</div>
+<hr /></div>
+</div>
+<!--End of Navigation Panel-->
+
+<h3><a name="SECTION002211000000000000000"></a><a name="general-personality"></a>
+<br>
+2.1.1 General list personality
+</h3>
+
+<p>
+These variables, grouped under the general list personality section,
+control some public information about the mailing list.
+
+<p>
+<dl>
+<dt><strong>real_name</strong></dt>
+<dd>Every mailing list has both a <em>posting name</em> and a <em>real
+ name</em>. The posting name shows up in urls and in email addresses,
+ e.g. the <code>mylist</code> in <code>mylist@example.com</code>. 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 <code>mylist</code>, the
+ real name can be <code>MyList</code>.
+
+<p>
+</dd>
+<dt><strong>owner</strong></dt>
+<dd>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
+ <code>moderator</code> addresses (see below).
+
+<p>
+</dd>
+<dt><strong>moderator</strong></dt>
+<dd>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 <code>owner</code> addresses. For example, when
+ you email <code>mylist-owner@example.com</code>, both the owner and
+ moderator addresses will receive a copy of the message.
+
+<p>
+</dd>
+<dt><strong>description</strong></dt>
+<dd>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 <span class="mailheader">To:</span> address. This text \
should + be relatively short and no longer than one line.
+
+<p>
+</dd>
+<dt><strong>info</strong></dt>
+<dd>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.
+
+<p>
+</dd>
+<dt><strong>subject_prefix</strong></dt>
+<dd>This is a string that will be prepended to the
+ <span class="mailheader">Subject:</span> header of any message posted to the \
list. + For example, if a message is posted to the list with a
+ <span class="mailheader">Subject:</span> like:
+
+<p>
+<div class="verbatim"><pre>
+ Subject: This is a message
+</pre></div>
+
+<p>
+and the <code>subject_prefix</code> is <code>[My List] </code> (note the
+ trailing space!), then the message will be received like so:
+
+<p>
+<div class="verbatim"><pre>
+ Subject: [My List] This is a message
+</pre></div>
+
+<p>
+If you leave <code>subject_prefix</code> empty, no prefix will be added
+ to the <span class="mailheader">Subject:</span>. 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.
+
+<p>
+</dd>
+<dt><strong>from_is_list</strong></dt>
+<dd>This applies to all non-digest messages sent by the list. For settings
+ that apply only to messages whose <span class="mailheader">From:</span> domain \
publishes a + DMARC <code>p=reject</code> or <code>p=quarantine</code> policy, see \
the + <code>dmarc_moderaction_action</code> description in section
+ <a href="sender-filters.html#sender-filters">2.7</a>.
+
+<p>
+If set to <em>Munge From</em>, it replaces the <span class="mailheader">From:</span> \
header + address with the list's posting address to mitigate issues stemming
+ from the original <span class="mailheader">From:</span> domain's DMARC or \
similar policies + and puts the original <span class="mailheader">From:</span> \
address in a + <span class="mailheader">Reply-To:</span> header.
+
+<p>
+If set to <em>Wrap Message</em> it wraps the original message as a MIME
+ subpart of an outer message with <span class="mailheader">From:</span> and
+ <span class="mailheader">Reply-To:</span> headers as above.
+
+<p>
+</dd>
+<dt><strong>anonymous_list</strong></dt>
+<dd>This variable allows you to turn on some simple anonymizing
+ features of Mailman. When you set this option to <em>Yes</em>,
+ Mailman will remove or replace the <span class="mailheader">From:</span>,
+ <span class="mailheader">Sender:</span>, and <span \
class="mailheader">Reply-To:</span> fields of any + message posted to the list.
+
+<p>
+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.
+</dd>
+</dl>
+
+<p>
+
+<div class="navigation">
+<div class='online-navigation'>
+<p></p><hr />
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td class='online-navigation'><a rel="prev" title="2.1 the General Options"
+ href="node9.html"><img src='previous.png'
+ border='0' height='32' alt='Previous Page' width='32' /></a></td>
+<td class='online-navigation'><a rel="parent" title="2.1 the General Options"
+ href="node9.html"><img src='up.png'
+ border='0' height='32' alt='Up one Level' width='32' /></a></td>
+<td class='online-navigation'><a rel="next" title="2.1.2 reply-to header munging"
+ href="node11.html"><img src='next.png'
+ border='0' height='32' alt='Next Page' width='32' /></a></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td class='online-navigation'><a rel="contents" title="Table of Contents"
+ href="contents.html"><img src='contents.png'
+ border='0' height='32' alt='Contents' width='32' /></a></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+</tr></table>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node9.html">2.1 The General Options</a>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node11.html">2.1.2 Reply-To header munging</a>
+</div>
+</div>
+<hr />
+<span class="release-info">Release 2.1, documentation updated on January 29, \
2015.</span> +</div>
+<!--End of Navigation Panel-->
+
+</body>
+</html>
=== added file 'doc/mailman-admin/sender-filters.html'
--- doc/mailman-admin/sender-filters.html 1970-01-01 00:00:00 +0000
+++ doc/mailman-admin/sender-filters.html 2015-02-10 23:18:45 +0000
@@ -0,0 +1,246 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' />
+<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration \
Manual' /> +<link rel='contents' href='contents.html' title="Contents" />
+<link rel='last' href='about.html' title='About this document...' />
+<link rel='help' href='about.html' title='About this document...' />
+<link rel="next" href="node23.html" />
+<link rel="prev" href="node21.html" />
+<link rel="parent" href="node20.html" />
+<link rel="next" href="node23.html" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name='aesop' content='information' />
+<title>2.7.2 Sender filters</title>
+</head>
+<body>
+<div class="navigation">
+<div id='top-navigation-panel' xml:id='top-navigation-panel'>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules"
+ href="node21.html"><img src='previous.png'
+ border='0' height='32' alt='Previous Page' width='32' /></a></td>
+<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options"
+ href="node20.html"><img src='up.png'
+ border='0' height='32' alt='Up one Level' width='32' /></a></td>
+<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters"
+ href="node23.html"><img src='next.png'
+ border='0' height='32' alt='Next Page' width='32' /></a></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td class='online-navigation'><a rel="contents" title="Table of Contents"
+ href="contents.html"><img src='contents.png'
+ border='0' height='32' alt='Contents' width='32' /></a></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+</tr></table>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a>
+</div>
+<hr /></div>
+</div>
+<!--End of Navigation Panel-->
+
+<h3><a name="SECTION002272000000000000000"></a><a name="sender-filters"></a>
+<br>
+2.7.2 Sender filters
+</h3>
+
+<p>
+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.
+
+<p>
+<dl>
+<dt><strong>default_member_moderation</strong></dt>
+<dd>Member postings are held for moderation if their <em>moderation
+ flag</em> is turned on. Note that only the list administrators can
+ change the value of a member's moderation flag.
+
+<p>
+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.
+
+<p>
+E-newsletter style lists can also be set up by using the
+ moderation flag. By setting the <code>member_moderation_action</code>
+ to <em>Reject</em>, 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.
+
+<p>
+</dd>
+<dt><strong>member_moderation_action</strong></dt>
+<dd>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 <em>Hold</em> 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
+ <em>Reject</em> or <em>Discard</em>.
+
+<p>
+Note that when a moderated member posts to your list, and the
+ <code>member_moderation_action</code> is set to <em>Hold</em>, 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.
+
+<p>
+</dd>
+<dt><strong>member_moderation_notice</strong></dt>
+<dd>When a member's moderation flag is turned on and
+ <code>member_moderation_action</code> is <em>Reject</em>, this variable
+ contains the text sent in the rejection notice.
+</dd>
+</dl>
+
+<p>
+The next group of settings control messages whose <span \
class="mailheader">From:</span> +domain publishes a DMARC <code>p=reject</code> or \
<code>p=quarantine</code> policy. +
+<p>
+<dl>
+<dt><strong>dmarc_moderation_action</strong></dt>
+<dd>These actions, <em>Accept</em>, <em>Munge From</em>, <em>Wrap Message</em>,
+ <em>Reject</em> and <em>Discard</em> apply only to messages whose
+ <span class="mailheader">From:</span> domain publishes a DMARC \
<code>p=reject</code> or optionally + (see the next setting) \
<code>p=quarantine</code> policy. If the message is + <span \
class="mailheader">From:</span> such a domain and this action is other than + \
<em>Accept</em>, this action applies to the message. Otherwise the + \
<code>from_is_list</code> setting in section <a \
href="general-personality.html#general-personality">2.1</a> + applies. See the \
<code>from_is_list</code> setting in section + <a \
href="general-personality.html#general-personality">2.1</a> for a description of the \
<em>Munge From</em> + and <em>Wrap Message</em> actions.
+</dd>
+<dt><strong>dmarc_quarantine_moderation_action</strong></dt>
+<dd>If this is set to <em>Yes</em>, the above <code>dmarc_moderation_action</code>
+ applies to messages with <span class="mailheader">From:</span> domain DMARC \
policy + <code>p=quarantine</code> as well as <code>p=reject</code>.
+</dd>
+<dt><strong>dmarc_moderation_notice</strong></dt>
+<dd>When <code>dmarc_moderation_action</code> applies and is <em>Reject</em>,
+ this variable contains the text sent in the rejection notice. If
+ empty, a generic notice mentioning DMARC is sent.
+</dd>
+</dl>
+
+<p>
+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).
+
+<p>
+<dl>
+<dt><strong>accept_these_nonmembers</strong></dt>
+<dd>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.
+
+<p>
+</dd>
+<dt><strong>hold_these_nonmembers</strong></dt>
+<dd>Postings from non-members whose addresses match this list are
+ held for moderator approval.
+
+<p>
+</dd>
+<dt><strong>reject_these_nonmembers</strong></dt>
+<dd>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.
+
+<p>
+</dd>
+<dt><strong>discard_these_nonmembers</strong></dt>
+<dd>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.
+
+<p>
+</dd>
+<dt><strong>generic_nonmember_action</strong></dt>
+<dd>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 <em>Hold</em>, 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.
+
+<p>
+</dd>
+<dt><strong>forward_auto_discards</strong></dt>
+<dd>When messages from non-members are discarded, either because the
+ sender address matched <code>discard_these_nonmembers</code>, or because
+ <code>generic_nonmember_action</code> is <em>Discard</em>, you can choose
+ whether such messages are forwarded to the lsit administrators or
+ not.
+</dd>
+</dl>
+
+<p>
+
+<div class="navigation">
+<div class='online-navigation'>
+<p></p><hr />
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules"
+ href="node21.html"><img src='previous.png'
+ border='0' height='32' alt='Previous Page' width='32' /></a></td>
+<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options"
+ href="node20.html"><img src='up.png'
+ border='0' height='32' alt='Up one Level' width='32' /></a></td>
+<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters"
+ href="node23.html"><img src='next.png'
+ border='0' height='32' alt='Next Page' width='32' /></a></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td class='online-navigation'><a rel="contents" title="Table of Contents"
+ href="contents.html"><img src='contents.png'
+ border='0' height='32' alt='Contents' width='32' /></a></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+<td class='online-navigation'><img src='blank.png'
+ border='0' height='32' alt='' width='32' /></td>
+</tr></table>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a>
+</div>
+</div>
+<hr />
+<span class="release-info">Release 2.1, documentation updated on January 29, \
2015.</span> +</div>
+<!--End of Navigation Panel-->
+
+</body>
+</html>
_______________________________________________
Mailman-checkins mailing list
Mailman-checkins@python.org
Unsubscribe: https://mail.python.org/mailman/options/mailman-checkins/mailman-cvs%40progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic