updating the content for this guide

author: bwarsaw <> 2004-12-14 14:14:32 +0000
committer: bwarsaw <> 2004-12-14 14:14:32 +0000
commit: a3a7b94b04974c40bca54caece474e8506d53822 (patch)
tree: bb447beeccdfa07a18082a99929ea7eb9f85cf9e /admin/www/mailman-admin/node26.html
parent: d497f1c251bff2eae3bce19d183a4bd988fe37e4 (diff)
download: mailman2-a3a7b94b04974c40bca54caece474e8506d53822.tar.gz
mailman2-a3a7b94b04974c40bca54caece474e8506d53822.tar.xz
mailman2-a3a7b94b04974c40bca54caece474e8506d53822.zip
1 files changed, 94 insertions, 147 deletions
diff --git a/admin/www/mailman-admin/node26.html b/admin/www/mailman-admin/node26.html
index 318f2fef..11e30d15 100644
--- a/admin/www/mailman-admin/node26.html
+++ b/admin/www/mailman-admin/node26.html
@@ -1,187 +1,134 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html>
 <head>
-<title>3.8 The Bounce Processing Category</title>
-<META NAME="description" CONTENT="3.8 The Bounce Processing Category">
-<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="node27.html">
-<LINK REL="previous" HREF="node21.html">
-<LINK REL="up" HREF="node9.html">
-<LINK REL="next" HREF="node27.html">
+<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="node27.html" />
+<link rel="prev" href="node25.html" />
+<link rel="parent" href="node8.html" />
+<link rel="next" href="node27.html" />
+<meta name='aesop' content='information' />
+<title>2.9 The Archiving Options Category</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><A HREF="node25.html"><img src="../icons/previous.gif"
-  border="0" height="32"
-  alt="Previous Page" width="32"></A></td>
-<td><A HREF="node9.html"><img src="../icons/up.gif"
-  border="0" height="32"
-  alt="Up One Level" width="32"></A></td>
-<td><A HREF="node27.html"><img src="../icons/next.gif"
-  border="0" height="32"
-  alt="Next Page" width="32"></A></td>
+<td class='online-navigation'><a rel="prev" title="2.8 The Bounce Processing"
+  href="node25.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 The List Configuration"
+  href="node8.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.10 The Mail/News Gateway"
+  href="node27.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><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>
+<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>
-<b class="navlabel">Previous:</b> <a class="sectref" HREF="node25.html">3.7.4 Spam Filters</A>
-<b class="navlabel">Up:</b> <a class="sectref" HREF="node9.html">3 The List Configuration</A>
-<b class="navlabel">Next:</b> <a class="sectref" HREF="node27.html">3.9 The Archiving Options</A>
-<br><hr>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node25.html">2.8 The Bounce Processing</A>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</A>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node27.html">2.10 The Mail/News Gateway</A>
+</div>
+<hr /></div>
 </DIV>
 <!--End of Navigation Panel-->
 
-<H2><A NAME="SECTION002380000000000000000">
-3.8 The Bounce Processing Category</A>
+<H2><A NAME="SECTION002290000000000000000">
+2.9 The Archiving Options Category</A>
 </H2>
 
 <P>
-These policies control the automatic bounce processing system in
-Mailman.  Here's an overview of how it works:
-
-<P>
-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 <i>hard</i> for fatal errors, or
-<i>soft</i> for transient errors.  When in doubt, a hard severity is
-used.
-
-<P>
-If no member address can be extracted from the bounce, then the bounce
-message is usually discarded.  Every member has a <i>bounce score</i>,
-initialized at zero, and every time we encounter a bounce from a
-member we increment that member's 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.
-
-<P>
-When a member's bounce score is greater than the <i>bounce score
-threshold</i> (see below), the member's 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.
-
-<P>
-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.
+Mailman comes with a built-in web-based archiver called
+<em>Pipermail</em>, although it can be configured to use external,
+third party archivers.
 
 <P>
 <DL>
-<DT><STRONG>bounce_processing</STRONG></DT>
-<DD>Specifies whether or not this list should do automatic bounce
-    processing.
-
-<P>
-</DD>
-<DT><STRONG>bounce_score_threshold</STRONG></DT>
-<DD>This is the bounce score above which a member's subscription will
-    be automatically disabled.  When the subscription is re-enabled,
-    their bounce score will be reset to zero.  This value can be a
-    floating point number.
-
-<P>
-</DD>
-<DT><STRONG>bounce_info_stale_after</STRONG></DT>
-<DD>Thenumber of days after which a member's bounce information is
-    considered stale.  If no new bounces have been received in the
-    interrim, the bounce score is reset to zero.  This value must be
-    an integer.
+<DT><STRONG>archive</STRONG></DT>
+<DD>This option tells Mailman whether to archive messages it receives
+    or not, regardless of whether Pipermail or a third party archiver
+    is used.  Turn this off if you don't want to archive messages.
 
 <P>
-</DD>
-<DT><STRONG>bounce_you_are_disabled_warnings</STRONG></DT>
-<DD>The number of notices a disabled member will receive before their
-    address is removed from the mailing list's roster.  Set this to 0
-    to immediately remove an address from the list once their bounce
-    score exceeds the threshold.  This value must be an integer.
-
-<P>
-</DD>
-<DT><STRONG>bounce_you_are_disabled_warnings_interval</STRONG></DT>
-<DD>The number of days between each disabled notification.
-
-<P>
-</DD>
-<DT><STRONG>bounce_unrecognized_goes_to_list_owner</STRONG></DT>
-<DD>This variable controls whether unrecognized bounces are discarded,
-    or forwarded on the list administrator.  The bounce detector isn't
-    perfect, although personalization can make it much more accurate.
-    The list owner may want to receive unrecognized bounces so that
-    they can manually disable or remove such members.
+Note that senders can control whether their own posts are
+    archived, on an individual per-message basis.  If the posted
+    message has a <span class="mailheader">X-No-Archive:</span> header (regardless of
+    value), or a <span class="mailheader">X-Archive:</span> header with a value of
+    <code>No</code> (case insensitive), then the message will not be
+    archived, although it will be treated as normal in all other
+    ways.
 
 <P>
 </DD>
-<DT><STRONG>bounce_notify_owner_on_disable</STRONG></DT>
-<DD>This option controls whether or not the list owner is notified
-    when a member's subscription is automatically disabled due to
-    their bounce threshold being reached.
+<DT><STRONG>archive_private</STRONG></DT>
+<DD>Controls whether Pipermail archives are private or public.
+    Private archives require a valid member address and password, or a
+    list administrator password in order to access them.  This
+    option has no effect when a third party archiver is used.
 
 <P>
 </DD>
-<DT><STRONG>bounce_notify_owner_on_removal</STRONG></DT>
-<DD>This option controls whether or not the list owner is notified
-    when a member is removed from the list after their disabled
-    notifications have been exhausted.
+<DT><STRONG>archive_volume_frequency</STRONG></DT>
+<DD>Controls how Pipermail splits messages in the archive.  The most
+    common option is <em>Monthly</em> meaning a new archive volume is
+    started every month.  Very high volume lists may want a shorter
+    frequency (e.g. <em>Weekly</em> or <em>Daily</em>) where as lower
+    volume lists may want a longer frequency (e.g. <em>Yearly</em>).
+    This option has no effect when a third party archiver is used.
 </DD>
 </DL>
 
 <P>
 
 <DIV CLASS="navigation">
-<p><hr>
+<div class='online-navigation'>
+<p></p><hr />
 <table align="center" width="100%" cellpadding="0" cellspacing="2">
 <tr>
-<td><A HREF="node25.html"><img src="../icons/previous.gif"
-  border="0" height="32"
-  alt="Previous Page" width="32"></A></td>
-<td><A HREF="node9.html"><img src="../icons/up.gif"
-  border="0" height="32"
-  alt="Up One Level" width="32"></A></td>
-<td><A HREF="node27.html"><img src="../icons/next.gif"
-  border="0" height="32"
-  alt="Next Page" width="32"></A></td>
+<td class='online-navigation'><a rel="prev" title="2.8 The Bounce Processing"
+  href="node25.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 The List Configuration"
+  href="node8.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.10 The Mail/News Gateway"
+  href="node27.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><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>
+<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>
-<b class="navlabel">Previous:</b> <a class="sectref" HREF="node25.html">3.7.4 Spam Filters</A>
-<b class="navlabel">Up:</b> <a class="sectref" HREF="node9.html">3 The List Configuration</A>
-<b class="navlabel">Next:</b> <a class="sectref" HREF="node27.html">3.9 The Archiving Options</A>
-<hr>
-<span class="release-info">Release 2.1, documentation updated on October 2, 2004.</span>
+<div class='online-navigation'>
+<b class="navlabel">Previous:</b>
+<a class="sectref" rel="prev" href="node25.html">2.8 The Bounce Processing</A>
+<b class="navlabel">Up:</b>
+<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</A>
+<b class="navlabel">Next:</b>
+<a class="sectref" rel="next" href="node27.html">2.10 The Mail/News Gateway</A>
+</div>
+</div>
+<hr />
+<span class="release-info">Release 2.1, documentation updated on December 13, 2004.</span>
 </DIV>
 <!--End of Navigation Panel-->
author	bwarsaw <>	2004-12-14 14:14:32 +0000
committer	bwarsaw <>	2004-12-14 14:14:32 +0000
commit	a3a7b94b04974c40bca54caece474e8506d53822 (patch)
tree	bb447beeccdfa07a18082a99929ea7eb9f85cf9e /admin/www/mailman-admin/node26.html
parent	d497f1c251bff2eae3bce19d183a4bd988fe37e4 (diff)
download	mailman2-a3a7b94b04974c40bca54caece474e8506d53822.tar.gz mailman2-a3a7b94b04974c40bca54caece474e8506d53822.tar.xz mailman2-a3a7b94b04974c40bca54caece474e8506d53822.zip