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/node11.html
parent: 25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download: mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz
mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip
1 files changed, 192 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node11.html b/admin/www/mailman-admin/node11.html
new file mode 100644
index 00000000..3ab9bf19
--- /dev/null
+++ b/admin/www/mailman-admin/node11.html
@@ -0,0 +1,192 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<title>3.1.1 General list personality</title>
+<META NAME="description" CONTENT="3.1.1 General list personality">
+<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="node12.html">
+<LINK REL="previous" HREF="node10.html">
+<LINK REL="up" HREF="node10.html">
+<LINK REL="next" HREF="node12.html">
+</head>
+<body>
+<DIV CLASS="navigation">
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node10.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="node12.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="node10.html">3.1 The General Options</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="node12.html">3.1.2 Reply-To header munging</A>
+<br><hr>
+</DIV>
+<!--End of Navigation Panel-->
+
+<H3><A NAME="SECTION002311000000000000000">
+3.1.1 General list personality</A>
+</H3>
+
+<P>
+These variables, grouped under the general list personality section,
+control some public information about the mailing list.
+
+<P>
+<DL>
+<DT><STRONG>real_name</STRONG></DT>
+<DD>Every mailing list has both a <i>posting name</i> and a <i>real
+    name</i>.  The posting name shows up in urls and in email addresses,
+    e.g. the <code>mylist</code> in <code>mylist@example.com</code>.  The posting
+    name is always presented in lower case, with alphanumeric
+    characters and no spaces.  The list's real name is used in some
+    public information and email responses, such as in the general
+    list overview.  The real name can differ from the posting name by
+    case only.  For example, if the posting name is <code>mylist</code>, the
+    real name can be <code>Posting</code>.
+
+<P>
+</DD>
+<DT><STRONG>owner</STRONG></DT>
+<DD>This variable contains a list of email addresses, one address per
+    line, of the list owners.  These addresses are used whenever the
+    list owners need to be contacted, either by the system or by end
+    users.  Often, these addresses are used in combination with the
+    <code>moderator</code> addresses (see below).
+
+<P>
+</DD>
+<DT><STRONG>moderator</STRONG></DT>
+<DD>This variable contains a list of email addresses, one address per
+    line, of the list moderators.  These addresses are often used in
+    combination with the <code>owner</code> addresses.  For example, when
+    you email <code>mylist-owner@example.com</code>, both the owner and
+    moderator addresses will receive a copy of the message.
+
+<P>
+</DD>
+<DT><STRONG>description</STRONG></DT>
+<DD>In the general list overview page, which shows you every available
+    mailing list, each list is displayed with a short description.
+    The contents of this variable is that description.  Note that in
+    emails from the mailing list, this description is also used in the
+    comment section of the <span class="mailheader">To:</span> address.  This text should
+    be relatively short and no longer than one line.
+
+<P>
+</DD>
+<DT><STRONG>info</STRONG></DT>
+<DD>This variable contains a longer description of the mailing list.
+    It is included at the top of the list's information page, and it
+    can contain HTML.  However, blank lines will be automatically
+    converted into paragraph breaks.  Preview your HTML though,
+    because unclosed or invalid HTML can prevent display of parts of
+    the list information page.
+
+<P>
+</DD>
+<DT><STRONG>subject_prefix</STRONG></DT>
+<DD>This is a string that will be prepended to the
+    <span class="mailheader">Subject:</span> header of any message posted to the list.
+    For example, if a message is posted to the list with a
+    <span class="mailheader">Subject:</span> like:
+
+<P>
+<dl><dd><pre class="verbatim">
+    Subject: This is a message
+</pre></dl>
+
+<P>
+and the <code>subject_prefix</code> is <code>[My List] </code> (note the
+    trailing space!), then the message will be received like so:
+
+<P>
+<dl><dd><pre class="verbatim">
+    Subject: [My List] This is a message
+</pre></dl>
+
+<P>
+If you leave <code>subject_prefix</code> empty, no prefix will be added
+    to the <span class="mailheader">Subject:</span>.  Mailman is careful not to add a
+    prefix when the header already has one, as is the case in replies
+    for example.  The prefix can also contain characters in the list's
+    preferred language.  In this case, because of vagarities of the
+    email standards, you may or may not want to add a trailing space.
+
+<P>
+</DD>
+<DT><STRONG>anonymous_list</STRONG></DT>
+<DD>This variable allows you to turn on some simple anonymizing
+    features of Mailman.  When you set this option to <i>Yes</i>,
+    Mailman will remove or replace the <span class="mailheader">From:</span>,
+    <span class="mailheader">Sender:</span>, and <span class="mailheader">Reply-To:</span> fields of any
+    message posted to the list.
+
+<P>
+Note that this option is simply an aid for anonymization, it
+    doesn't guarantee it.  For example, a poster's identity could be
+    evident in their signature, or in other mail headers, or even in
+    the style of the content of the message.  There's little Mailman
+    can do about this kind of identity leakage.
+</DD>
+</DL>
+
+<P>
+
+<DIV CLASS="navigation">
+<p><hr>
+<table align="center" width="100%" cellpadding="0" cellspacing="2">
+<tr>
+<td><A HREF="node10.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="node12.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="node10.html">3.1 The General Options</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="node12.html">3.1.2 Reply-To header munging</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/node11.html
parent	25b16e646ed8ac48fa99584e631bd2a69ce02b2b (diff)
download	mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.gz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.tar.xz mailman2-96f5db3dfd2e394698e5f9743318585782e3bca6.zip