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/node21.html
parent: b7f0fb3c888c1d331c2239fba0b8332a3bf240f2 (diff)
download: mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.gz
mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.xz
mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.zip
1 files changed, 0 insertions, 203 deletions
diff --git a/admin/www/mailman-admin/node21.html b/admin/www/mailman-admin/node21.html
deleted file mode 100644
index 03d23444..00000000
--- a/admin/www/mailman-admin/node21.html
+++ /dev/null
@@ -1,203 +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="node22.html" />
-<link rel="prev" href="node20.html" />
-<link rel="parent" href="node20.html" />
-<link rel="next" href="node22.html" />
-<meta name='aesop' content='information' />
-<title>2.7.1 Subscription rules</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 The Privacy Options"
-  href="node20.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.7 The Privacy Options"
-  href="node20.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.7.2 Sender filters"
-  href="node22.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="node20.html">2.7 The Privacy Options</A>
-<b class="navlabel">Up:</b>
-<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</A>
-<b class="navlabel">Next:</b>
-<a class="sectref" rel="next" href="node22.html">2.7.2 Sender filters</A>
-</div>
-<hr /></div>
-</DIV>
-<!--End of Navigation Panel-->
-
-<H3><A NAME="SECTION002271000000000000000">
-2.7.1 Subscription rules</A>
-</H3>
-
-<P>
-This subcategory controls the rules for exposing the existance of this
-list, and for what new members must do in order to subscribe to the
-list.
-
-<P>
-<DL>
-<DT><STRONG>advertised</STRONG></DT>
-<DD>This option controls whether this list will show up in the list
-    overview for the site.  Normally, an overview contains the name
-    and short description of every mailing list in the virtual
-    domain.  By setting this variable to <em>No</em>, it will not show
-    up in this overview, nor will it show up in the administrative
-    overview.  The only way then to find the list is to guess (or
-    know!) its name.
-
-<P>
-</DD>
-<DT><STRONG>subscribe_policy</STRONG></DT>
-<DD>This option controls the steps that a new member must take to join
-    the list.  The available options may differ based on some defaults
-    that the site administrator chooses.  They are:
-
-<P>
-
-<UL>
-<LI>None - No verification is done on the subscribing
-          member. This is also called <em>open subscriptions</em> and is
-          generally disabled by default.  The site administrator must
-          allow list admins to choose this option; if not, this option
-          will not be presented to you.
-
-<P>
-</LI>
-<LI>Confirm - An email confirmation step is required before the
-          address is added to the list.  When a member requests
-          subscription, either via the web page or by sending a
-          message to <var>yourlist</var><code>-join@example.com</code>, Mailman
-          will send a confirmation message to the requesting address.
-          This mail-back confirmation contains a unique identifier,
-          which the requester can present to Mailman in order to
-          confirm their subscription.  This can be done either by
-          replying to the mail-back, or by visiting the url in the
-          mail-back message.  The url points to a page that lets the
-          user either discard or confirm their request.
-
-<P>
-</LI>
-<LI>Require approval - All subscription requests are held for
-          approval of the list moderator.  No mail-back confirmation
-          is sent, but the list admins will recieve a message
-          indicating that approval is pending.
-
-<P>
-</LI>
-<LI>Confirm and approve - Here, a mail-back notice must first
-          be confirmed by the requester.  Once confirmed, the list
-          moderator must then approve the request.  This is the most
-          secure method for users to subscribe since it both verifies
-          the requesting address, and forces the list moderators to
-          approve the request.
-
-<P>
-</LI>
-</UL>
-
-<P>
-</DD>
-<DT><STRONG>unsubscribe_policy</STRONG></DT>
-<DD>Specifies whether the list moderator's approval is required for
-    unsubscription requests.  <em>No</em> is highly recommended, since
-    it is exceedingly impolite to not allow people to leave a mailing
-    list whenever they want (i.e. opt-out).  <em>Yes</em> is useful in
-    some specialized contexts; e.g. you may not want to allow
-    employees to unsubscribe from the company newsletter.
-
-<P>
-</DD>
-<DT><STRONG>ban_list</STRONG></DT>
-<DD>This contains a list of addresses (or regular expressiosn), one
-    per line, that are banned from ever subscribing to your mailing
-    list.  If a match occurs during the subscription process, the
-    request will be automatically rejected, and the requester will get
-    a rejection notice.  You can use this to permanently ban
-    troublesome posters to a members-only list.
-
-<P>
-</DD>
-<DT><STRONG>private_roster</STRONG></DT>
-<DD>This specifies who is allowed to view the roster of member
-    addresses.  If you choose <em>Anyone</em>, then the list membership
-    is completely public.  You can limit exposure of the roster to
-    just list members, or just to the list administrators.  In the
-    former case, a user must enter a valid member's address and
-    password before they can view the roster.  In the latter case, a
-    list administrator's password must be enter; if a matching admin
-    password is entered, address field is ignored.
-
-<P>
-</DD>
-<DT><STRONG>obscure_addresses</STRONG></DT>
-<DD>Controls whether some simple obfuscation of addresses is used when
-    member addresses are included on web pages.  This should reduce
-    the opportunity for email address harvesting by spammers, although
-    it probably doesn't eliminate it.
-</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 The Privacy Options"
-  href="node20.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.7 The Privacy Options"
-  href="node20.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.7.2 Sender filters"
-  href="node22.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="node20.html">2.7 The Privacy Options</A>
-<b class="navlabel">Up:</b>
-<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</A>
-<b class="navlabel">Next:</b>
-<a class="sectref" rel="next" href="node22.html">2.7.2 Sender filters</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/node21.html
parent	b7f0fb3c888c1d331c2239fba0b8332a3bf240f2 (diff)
download	mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.gz mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.tar.xz mailman2-34d6ece8a454e5d1d027ed106ba039a0a88db36d.zip