This commit was manufactured by cvs2svn to create branch

'Release_2_1-maint'.
author: <> 2004-11-03 18:29:30 +0000
committer: <> 2004-11-03 18:29:30 +0000
commit: 96f5db3dfd2e394698e5f9743318585782e3bca6 (patch)
tree: 6a354464a1a4e53ef2b7bf5eab93f83dea604a01 /admin/www/mailman-admin/node15.html
parent: 25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download: mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip
1 files changed, 200 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node15.html b/admin/www/mailman-admin/node15.html
new file mode 100644
index 00000000..88ab9964
--- /dev/null
+++ b/admin/www/mailman-admin/node15.html
@@ -0,0 +1,200 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<title>3.1.5 Additional settings</title>
+<META NAME="description" CONTENT="3.1.5 Additional settings">
+<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="previous" HREF="node14.html">
+<LINK REL="up" HREF="node10.html">
+<LINK REL="next" HREF="node16.html">
+</head>
+<body>
+<DIV CLASS="navigation">
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node14.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="node16.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="node14.html">3.1.4 Notifications</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="node16.html">3.2 The Passwords Category</A>
+<br><hr>
+</DIV>
+<!--End of Navigation Panel-->
+
+<H3><A NAME="SECTION002315000000000000000">
+3.1.5 Additional settings</A>
+</H3>
+
+<P>
+This section contains some miscellaneous settings for your mailing
+list.
+
+<P>
+<DL>
+<DT><STRONG>emergency</STRONG></DT>
+<DD>When this option is enabled, all list traffic is emergency
+    moderated, i.e. held for moderation.  Turn this option on when
+    your list is experiencing a flamewar and you want a cooling off
+    period.
+
+<P>
+</DD>
+<DT><STRONG>new_member_options</STRONG></DT>
+<DD>Each member has a set of subscription options which they can use
+    to control how they receive messages and otherwise interact with
+    the list.  While the members can change these settings by logging
+    into their personal options page, you might want to set the
+    default for a number of the member options.  You can do that with
+    this variable, but see also the other categories for other member
+    defaults you can set.
+
+<P>
+This variable presents a set of checkboxes which control the
+    defaults for some of the member options.  <i>Conceal the
+    member's address</i> specifies whether or not the address is
+    displayed in the list roster.  <i>Acknowledge the member's
+    posting</i> controls whether or not Mailman sends an acknowledgement
+    to a member when they post a message to the list.  <i>Do not
+    send a copy of a member's own post</i> specifies whether a member
+    posting to the list will get a copy of their own posting.
+    <i>Filter out duplicate messages to list members (if possible)</i>
+    specifies whether members who are explicitly listed as a recipient
+    of a message (e.g. via the <span class="mailheader">Cc:</span> header) will also get a
+    copy from Mailman.
+
+<P>
+Of course, members can always override these defaults by making
+    changes on their membership options page.
+
+<P>
+</DD>
+<DT><STRONG>administrivia</STRONG></DT>
+<DD>This option specifies whether Mailman will search posted messages
+    for <i>admimistrivia</i>, in other words, email commands which
+    usually should be posted to the <code>-request</code> address for the
+    list.  Setting this to <i>Yes</i> helps prevent such things as
+    unsubscribe messages getting erroneously posted to the list.
+
+<P>
+If a message seems to contain administrivia, it is held for
+    moderator approval.
+
+<P>
+</DD>
+<DT><STRONG>max_message_size</STRONG></DT>
+<DD>This option specifies a maximum message size, in kilobytes, over
+    which the message will be held for moderator approval.
+
+<P>
+</DD>
+<DT><STRONG>host_name</STRONG></DT>
+<DD>This option specifies the host name part of email addresses used
+    by this list.  For example, this is the <code>example.com</code> part of
+    the posting address <code>mylist@example.com</code>.
+
+<P>
+It's generally not a good idea to change this value, since its
+    default value is specified when the mailing list is created.
+    Changing this to an incorrect value could make it difficult to
+    contact your mailing list.  Also not that the url used to visit
+    the list's pages is not configurable through the web interface.
+    This is because if you messed it up, you'd have to have the site
+    administrator fix it.
+
+<P>
+</DD>
+<DT><STRONG>include_rfc2369_headers</STRONG></DT>
+<DD><a class="rfc" name="rfcref-1046"
+href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a> is an internet standard that describes a bunch of
+    headers that mailing list managers should add to messages to make
+    it easier for people to interact with the list.  Mail reading
+    programs which support this standard may provide buttons for easy
+    access to the list's archives, or for subscribing and
+    unsubscribing to the list.  It's generally a good idea to enable
+    these headers as it provides for an improved user experience.
+    These headers are often called the <code>List-*</code> headers.
+
+<P>
+However, not all mail readers are standards compliant yet, and if
+    you have a large number of members who are using non-compliant
+    mail readers, they may be annoyed at these headers.  You should
+    first try to educate your members as to why these headers exist,
+    and how to hide them in their mail clients.  As a last resort you
+    can disable these headers, but this is not recommended.
+
+<P>
+</DD>
+<DT><STRONG>include_list_post_header</STRONG></DT>
+<DD>The <span class="mailheader">List-Post:</span> header is one of the headers
+    recommended by <a class="rfc" name="rfcref-1048"
+href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>.  However for some announce-only mailing
+    lists, only a very select group of people are allowed to post to
+    the list; the general membership is usually not allowed to post to
+    such lists.  For lists of this nature, the <span class="mailheader">List-Post:</span>
+    header is misleading.  Select <i>No</i> to disable the inclusion
+    of this header. (This does not affect the inclusion of the other
+    <code>List-*</code> headers.)
+</DD>
+</DL>
+
+<P>
+
+<DIV CLASS="navigation">
+<p><hr>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node14.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="node16.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="node14.html">3.1.4 Notifications</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="node16.html">3.2 The Passwords Category</A>
+<hr>
+<span class="release-info">Release 2.1, documentation updated on October 2, 2004.</span>
+</DIV>
+<!--End of Navigation Panel-->
+
+</BODY>
+</HTML>
author	<>	2004-11-03 18:29:30 +0000
committer	<>	2004-11-03 18:29:30 +0000
commit	96f5db3dfd2e394698e5f9743318585782e3bca6 (patch)
tree	6a354464a1a4e53ef2b7bf5eab93f83dea604a01 /admin/www/mailman-admin/node15.html
parent	25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download	mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip