This commit was manufactured by cvs2svn to create branch

'Release_2_1-maint'.
author: <> 2004-11-03 18:29:30 +0000
committer: <> 2004-11-03 18:29:30 +0000
commit: 96f5db3dfd2e394698e5f9743318585782e3bca6 (patch)
tree: 6a354464a1a4e53ef2b7bf5eab93f83dea604a01 /admin/www/mailman-admin/node23.html
parent: 25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download: mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip
1 files changed, 208 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node23.html b/admin/www/mailman-admin/node23.html
new file mode 100644
index 00000000..ef2f32c3
--- /dev/null
+++ b/admin/www/mailman-admin/node23.html
@@ -0,0 +1,208 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<title>3.7.2 Sender filters</title>
+<META NAME="description" CONTENT="3.7.2 Sender filters">
+<META NAME="keywords" CONTENT="mailman-admin">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="STYLESHEET" href="mailman-admin.css">
+<link rel="first" href="mailman-admin.html">
+<link rel="contents" href="contents.html" title="Contents">
+
+<LINK REL="next" HREF="node24.html">
+<LINK REL="previous" HREF="node22.html">
+<LINK REL="up" HREF="node21.html">
+<LINK REL="next" HREF="node24.html">
+</head>
+<body>
+<DIV CLASS="navigation">
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node22.html"><img src="../icons/previous.gif"
+  border="0" height="32"
+  alt="Previous Page" width="32"></A></td>
+<td><A HREF="node21.html"><img src="../icons/up.gif"
+  border="0" height="32"
+  alt="Up One Level" width="32"></A></td>
+<td><A HREF="node24.html"><img src="../icons/next.gif"
+  border="0" height="32"
+  alt="Next Page" width="32"></A></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td><A href="contents.html"><img src="../icons/contents.gif"
+  border="0" height="32"
+  alt="Contents" width="32"></A></td>
+<td><img src="../icons/blank.gif"
+  border="0" height="32"
+  alt="" width="32"></td>
+<td><img src="../icons/blank.gif"
+  border="0" height="32"
+  alt="" width="32"></td>
+</tr></table>
+<b class="navlabel">Previous:</b> <a class="sectref" HREF="node22.html">3.7.1 Subscription rules</A>
+<b class="navlabel">Up:</b> <a class="sectref" HREF="node21.html">3.7 The Privacy Options</A>
+<b class="navlabel">Next:</b> <a class="sectref" HREF="node24.html">3.7.3 Recipient Filters</A>
+<br><hr>
+</DIV>
+<!--End of Navigation Panel-->
+
+<H3><A NAME="SECTION002372000000000000000">
+3.7.2 Sender filters</A>
+</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 <i>moderation
+    flag</i> 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 <i>Reject</i>, 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 <i>Hold</i> 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
+    <i>Reject</i> or <i>Discard</i>.
+
+<P>
+Note that when a moderated member posts to your list, and the
+    <code>member_moderation_action</code> is set to <i>Hold</i>, 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 <i>Reject</i>, this variable
+    contains the text sent in the rejection notice.
+</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 <i>Hold</i>, 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 <i>Discard</i>, you can choose
+    whether such messages are forwarded to the lsit administrators or
+    not.
+</DD>
+</DL>
+
+<P>
+
+<DIV CLASS="navigation">
+<p><hr>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node22.html"><img src="../icons/previous.gif"
+  border="0" height="32"
+  alt="Previous Page" width="32"></A></td>
+<td><A HREF="node21.html"><img src="../icons/up.gif"
+  border="0" height="32"
+  alt="Up One Level" width="32"></A></td>
+<td><A HREF="node24.html"><img src="../icons/next.gif"
+  border="0" height="32"
+  alt="Next Page" width="32"></A></td>
+<td align="center" width="100%">GNU Mailman - List Administration Manual</td>
+<td><A href="contents.html"><img src="../icons/contents.gif"
+  border="0" height="32"
+  alt="Contents" width="32"></A></td>
+<td><img src="../icons/blank.gif"
+  border="0" height="32"
+  alt="" width="32"></td>
+<td><img src="../icons/blank.gif"
+  border="0" height="32"
+  alt="" width="32"></td>
+</tr></table>
+<b class="navlabel">Previous:</b> <a class="sectref" HREF="node22.html">3.7.1 Subscription rules</A>
+<b class="navlabel">Up:</b> <a class="sectref" HREF="node21.html">3.7 The Privacy Options</A>
+<b class="navlabel">Next:</b> <a class="sectref" HREF="node24.html">3.7.3 Recipient Filters</A>
+<hr>
+<span class="release-info">Release 2.1, documentation updated on October 2, 2004.</span>
+</DIV>
+<!--End of Navigation Panel-->
+
+</BODY>
+</HTML>
author	<>	2004-11-03 18:29:30 +0000
committer	<>	2004-11-03 18:29:30 +0000
commit	96f5db3dfd2e394698e5f9743318585782e3bca6 (patch)
tree	6a354464a1a4e53ef2b7bf5eab93f83dea604a01 /admin/www/mailman-admin/node23.html
parent	25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download	mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip