diff options
Diffstat (limited to 'admin/www/mailman-admin/node22.html')
-rw-r--r-- | admin/www/mailman-admin/node22.html | 197 |
1 files changed, 197 insertions, 0 deletions
diff --git a/admin/www/mailman-admin/node22.html b/admin/www/mailman-admin/node22.html new file mode 100644 index 00000000..00f14733 --- /dev/null +++ b/admin/www/mailman-admin/node22.html @@ -0,0 +1,197 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<title>3.7.1 Subscription rules</title> +<META NAME="description" CONTENT="3.7.1 Subscription rules"> +<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="node23.html"> +<LINK REL="previous" HREF="node21.html"> +<LINK REL="up" HREF="node21.html"> +<LINK REL="next" HREF="node23.html"> +</head> +<body> +<DIV CLASS="navigation"> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td><A HREF="node21.html"><img src="../icons/previous.gif" + border="0" height="32" + alt="Previous Page" width="32"></A></td> +<td><A HREF="node21.html"><img src="../icons/up.gif" + border="0" height="32" + alt="Up One Level" width="32"></A></td> +<td><A HREF="node23.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="node21.html">3.7 The Privacy Options</A> +<b class="navlabel">Up:</b> <a class="sectref" HREF="node21.html">3.7 The Privacy Options</A> +<b class="navlabel">Next:</b> <a class="sectref" HREF="node23.html">3.7.2 Sender filters</A> +<br><hr> +</DIV> +<!--End of Navigation Panel--> + +<H3><A NAME="SECTION002371000000000000000"> +3.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 <i>No</i>, 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 <i>open subscriptions</i> 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. <i>No</i> is highly recommended, since + it is exceedingly impolite to not allow people to leave a mailing + list whenever they want (i.e. opt-out). <i>Yes</i> 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 <i>Anyone</i>, 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"> +<p><hr> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td><A HREF="node21.html"><img src="../icons/previous.gif" + border="0" height="32" + alt="Previous Page" width="32"></A></td> +<td><A HREF="node21.html"><img src="../icons/up.gif" + border="0" height="32" + alt="Up One Level" width="32"></A></td> +<td><A HREF="node23.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="node21.html">3.7 The Privacy Options</A> +<b class="navlabel">Up:</b> <a class="sectref" HREF="node21.html">3.7 The Privacy Options</A> +<b class="navlabel">Next:</b> <a class="sectref" HREF="node23.html">3.7.2 Sender filters</A> +<hr> +<span class="release-info">Release 2.1, documentation updated on October 2, 2004.</span> +</DIV> +<!--End of Navigation Panel--> + +</BODY> +</HTML> |