1 files changed, 189 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node26.html b/admin/www/mailman-admin/node26.html
new file mode 100644
index 00000000..318f2fef
--- /dev/null
+++ b/admin/www/mailman-admin/node26.html
@@ -0,0 +1,189 @@
+<!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">
+</head>
+<body>
+<DIV CLASS="navigation">
+<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 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="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>
+<!--End of Navigation Panel-->
+
+<H2><A NAME="SECTION002380000000000000000">
+3.8 The Bounce Processing 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.
+
+<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.
+
+<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.
+
+<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.
+
+<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.
+</DD>
+</DL>
+
+<P>
+
+<DIV CLASS="navigation">
+<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 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="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>
+<!--End of Navigation Panel-->
+
+</BODY>
+</HTML>