Copy the mm21 admin directory out of the mm21 branch. We'll svn

external the latter to get that back into the release, but I really don't want to maintain multiple copies of the web pages.
author: bwarsaw <> 2006-09-17 18:16:07 +0000
committer: bwarsaw <> 2006-09-17 18:16:07 +0000
commit: 34d6ece8a454e5d1d027ed106ba039a0a88db36d (patch)
tree: 6dc6f8711b20124ce38491300d5fb95e1c022206 /admin/www/mailman-admin/node25.html
parent: b7f0fb3c888c1d331c2239fba0b8332a3bf240f2 (diff)
download: mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.gz
mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.xz
mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.zip
1 files changed, 0 insertions, 195 deletions
diff --git a/admin/www/mailman-admin/node25.html b/admin/www/mailman-admin/node25.html
deleted file mode 100644
index e13821ae..00000000
--- a/admin/www/mailman-admin/node25.html
+++ /dev/null
@@ -1,195 +0,0 @@
-<!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="node26.html" />
-<link rel="prev" href="node20.html" />
-<link rel="parent" href="node8.html" />
-<link rel="next" href="node26.html" />
-<meta name='aesop' content='information' />
-<title>2.8 The Bounce Processing 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 class='online-navigation'><a rel="prev" title="2.7.4 Spam Filters"
-  href="node24.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.9 The Archiving Options"
-  href="node26.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="node24.html">2.7.4 Spam Filters</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="node26.html">2.9 The Archiving Options</A>
-</div>
-<hr /></div>
-</DIV>
-<!--End of Navigation Panel-->
-
-<H2><A NAME="SECTION002280000000000000000">
-2.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 <em>hard</em> for fatal errors, or
-<em>soft</em> 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 <em>bounce score</em>,
-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 <em>bounce score
-threshold</em> (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">
-<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.4 Spam Filters"
-  href="node24.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.9 The Archiving Options"
-  href="node26.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="node24.html">2.7.4 Spam Filters</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="node26.html">2.9 The Archiving Options</A>
-</div>
-</div>
-<hr />
-<span class="release-info">Release 2.1, documentation updated on December 13, 2004.</span>
-</DIV>
-<!--End of Navigation Panel-->
-
-</BODY>
-</HTML>
author	bwarsaw <>	2006-09-17 18:16:07 +0000
committer	bwarsaw <>	2006-09-17 18:16:07 +0000
commit	34d6ece8a454e5d1d027ed106ba039a0a88db36d (patch)
tree	6dc6f8711b20124ce38491300d5fb95e1c022206 /admin/www/mailman-admin/node25.html
parent	b7f0fb3c888c1d331c2239fba0b8332a3bf240f2 (diff)
download	mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.gz mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.xz mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.zip