aboutsummaryrefslogtreecommitdiffstats
path: root/admin/www/mailman-admin/node12.html
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--admin/www/mailman-admin/node12.html193
1 files changed, 193 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node12.html b/admin/www/mailman-admin/node12.html
new file mode 100644
index 00000000..9a908dfc
--- /dev/null
+++ b/admin/www/mailman-admin/node12.html
@@ -0,0 +1,193 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<title>3.1.2 Reply-To header munging</title>
+<META NAME="description" CONTENT="3.1.2 Reply-To header munging">
+<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="node13.html">
+<LINK REL="previous" HREF="node11.html">
+<LINK REL="up" HREF="node10.html">
+<LINK REL="next" HREF="node13.html">
+</head>
+<body>
+<DIV CLASS="navigation">
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node11.html"><img src="../icons/previous.gif"
+ border="0" height="32"
+ alt="Previous Page" width="32"></A></td>
+<td><A HREF="node10.html"><img src="../icons/up.gif"
+ border="0" height="32"
+ alt="Up One Level" width="32"></A></td>
+<td><A HREF="node13.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="node11.html">3.1.1 General list personality</A>
+<b class="navlabel">Up:</b> <a class="sectref" HREF="node10.html">3.1 The General Options</A>
+<b class="navlabel">Next:</b> <a class="sectref" HREF="node13.html">3.1.3 Umbrella list settings</A>
+<br><hr>
+</DIV>
+<!--End of Navigation Panel-->
+
+<H3><A NAME="SECTION002312000000000000000">
+3.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 <i>No</i>, 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 <i>Poster</i>, 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 <i>This list</i>, 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 <i>Explicit address</i>, 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 <i>Explicit address</i>.
+
+<P>
+</DD>
+</DL>
+
+<P>
+
+<DIV CLASS="navigation">
+<p><hr>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node11.html"><img src="../icons/previous.gif"
+ border="0" height="32"
+ alt="Previous Page" width="32"></A></td>
+<td><A HREF="node10.html"><img src="../icons/up.gif"
+ border="0" height="32"
+ alt="Up One Level" width="32"></A></td>
+<td><A HREF="node13.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="node11.html">3.1.1 General list personality</A>
+<b class="navlabel">Up:</b> <a class="sectref" HREF="node10.html">3.1 The General Options</A>
+<b class="navlabel">Next:</b> <a class="sectref" HREF="node13.html">3.1.3 Umbrella list settings</A>
+<hr>
+<span class="release-info">Release 2.1, documentation updated on October 2, 2004.</span>
+</DIV>
+<!--End of Navigation Panel-->
+
+</BODY>
+</HTML>