Because the admin directory is no longer included, the www directory isn't

either, and that's where the generated docs used to live. So now, make this directory include the generated docs, removing the old IPC7 and LISA-98 directories, and the .tex source files. These latter are moved to the admin repository.
author: Barry Warsaw <barry@python.org> 2007-12-05 17:23:41 -0500
committer: Barry Warsaw <barry@python.org> 2007-12-05 17:23:41 -0500
commit: 3a258ad5cdd98c5705af6c02ba91993b3d382adc (patch)
tree: 85c90c037ee5b5f992c3b291e66c60cab46d9e73 /doc/mailman-admin/node11.html
parent: 18f080804e368c63de499b32717d57701aaf8880 (diff)
download: mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.tar.gz
mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.tar.xz
mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.zip
1 files changed, 200 insertions, 0 deletions
diff --git a/doc/mailman-admin/node11.html b/doc/mailman-admin/node11.html
new file mode 100644
index 00000000..665d5bfd
--- /dev/null
+++ b/doc/mailman-admin/node11.html
@@ -0,0 +1,200 @@
+<!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="node12.html" />
+<link rel="prev" href="node10.html" />
+<link rel="parent" href="node9.html" />
+<link rel="next" href="node12.html" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name='aesop' content='information' />
+<title>2.1.2 Reply-To header munging</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.1 general list personality"
+  href="node10.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.3 umbrella list settings"
+  href="node12.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="node10.html">2.1.1 General list personality</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="node12.html">2.1.3 Umbrella list settings</a>
+</div>
+<hr /></div>
+</div>
+<!--End of Navigation Panel-->
+
+<h3><a name="SECTION002212000000000000000">
+2.1.2 Reply-To header munging</a>
+</h3>
+
+<p>
+This section controls what happens to the <span class="mailheader">Reply-To:</span>
+headers of messages posted through your list.
+
+<p>
+Beware!  <span class="mailheader">Reply-To:</span> munging is considered a religious issue
+and the policies you set here can ignite some of the most heated
+off-topic flame wars on your mailing lists.  We'll try to stay as
+agnostic as possible, but our biases may still peak through.
+
+<p>
+<span class="mailheader">Reply-To:</span> is a header that is commonly used to redirect
+replies to messages.  Exactly what happens when your uses reply to
+such a message depends on the mail readers your users use, and what
+functions they provide.  Usually, there is both a ``reply to sender''
+button and a ``reply to all'' button.  If people use these buttons
+correctly, you will probably never need to munge
+<span class="mailheader">Reply-To:</span>, so the default values should be fine.
+
+<p>
+Since an informed decision is always best, here are links to two
+articles that discuss the opposing viewpoints in great detail:
+
+<p>
+
+<ul>
+<li><a class="ulink" href="http://www.unicom.com/pw/reply-to-harmful.html"
+  >Reply-To Munging Considered
+      Harmful</a>
+</li>
+<li><a class="ulink" href="http://www.metasystema.org/essays/reply-to-useful.mhtml"
+  >Reply-To Munging Considered
+      Useful</a>
+
+<p>
+</li>
+</ul>
+
+<p>
+The three options in this section work together to provide enough
+flexibility to do whatever <span class="mailheader">Reply-To:</span> munging you might
+(misguidingly :) feel you need to do.
+
+<p>
+<dl>
+<dt><strong>first_strip_reply_to</strong></dt>
+<dd>This variable controls whether any <span class="mailheader">Reply-To:</span> header
+    already present in the posted message should get removed before
+    any other munging occurs.  Stripping this header will be done
+    regardless of whether or not Mailman will add its own
+    <span class="mailheader">Reply-To:</span> header to the message.
+
+<p>
+If this option is set to <em>No</em>, then any existing
+    <span class="mailheader">Reply-To:</span> header will be retained in the posted
+    message.  If Mailman adds its own header, it will contain
+    addresses which are the union of the original header and the
+    Mailman added addresses.  The mail standards specify that a
+    message may only have one <span class="mailheader">Reply-To:</span> header, but that
+    that header may contain multiple addresses.
+
+<p>
+</dd>
+<dt><strong>reply_goes_to_list</strong></dt>
+<dd>This variable controls whether Mailman will add its own
+    <span class="mailheader">Reply-To:</span> header, and if so, what the value of that
+    header will be (not counting original header stripping - see
+    above).
+
+<p>
+When you set this variable to <em>Poster</em>, no additional
+    <span class="mailheader">Reply-To:</span> header will be added by Mailman.  This
+    setting is strongly recommended.
+
+<p>
+When you set this variable to <em>This list</em>, a
+    <span class="mailheader">Reply-To:</span> header pointing back to your list's posting
+    address will be added.
+
+<p>
+When you set this variable to <em>Explicit address</em>, the value
+    of the variable <code>reply_to_address</code> (see below) will be
+    added.  Note that this is one situation where
+    <span class="mailheader">Reply-To:</span> munging may have a legitimate purpose.  Say
+    you have two lists at your site, an announce list and a discussion
+    list.  The announce list might allow postings only from a small
+    number of approved users; the general list membership probably
+    can't post to this list.  But you want to allow comments on
+    announcements to be posted to the general discussion list by any
+    list member.  In this case, you can set the <span class="mailheader">Reply-To:</span>
+    header for the announce list to point to the discussion list's
+    posting address.
+
+<p>
+</dd>
+<dt><strong>reply_to_address</strong></dt>
+<dd>This is the address that will be added in the
+    <span class="mailheader">Reply-To:</span> header if <code>reply_goes_to_list</code> is set
+    to <em>Explicit address</em>.
+
+<p>
+</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.1 general list personality"
+  href="node10.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.3 umbrella list settings"
+  href="node12.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="node10.html">2.1.1 General list personality</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="node12.html">2.1.3 Umbrella list settings</a>
+</div>
+</div>
+<hr />
+<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span>
+</div>
+<!--End of Navigation Panel-->
+
+</body>
+</html>
author	Barry Warsaw <barry@python.org>	2007-12-05 17:23:41 -0500
committer	Barry Warsaw <barry@python.org>	2007-12-05 17:23:41 -0500
commit	3a258ad5cdd98c5705af6c02ba91993b3d382adc (patch)
tree	85c90c037ee5b5f992c3b291e66c60cab46d9e73 /doc/mailman-admin/node11.html
parent	18f080804e368c63de499b32717d57701aaf8880 (diff)
download	mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.tar.gz mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.tar.xz mailman2-3a258ad5cdd98c5705af6c02ba91993b3d382adc.zip