diff options
author | bwarsaw <> | 2003-02-08 07:14:13 +0000 |
---|---|---|
committer | bwarsaw <> | 2003-02-08 07:14:13 +0000 |
commit | 925200da11d52ae4d7fc664bff898f8050bef687 (patch) | |
tree | 389bbd6c076718221b427d6d6e4fa199a1729ec0 /doc | |
parent | dea51d7d5a5c5d8ea6900a838a12e230b7a000b6 (diff) | |
download | mailman2-925200da11d52ae4d7fc664bff898f8050bef687.tar.gz mailman2-925200da11d52ae4d7fc664bff898f8050bef687.tar.xz mailman2-925200da11d52ae4d7fc664bff898f8050bef687.zip |
Backporting from the trunk.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/mailman-admin.tex | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/doc/mailman-admin.tex b/doc/mailman-admin.tex index 8cdc7a61..197a18f1 100644 --- a/doc/mailman-admin.tex +++ b/doc/mailman-admin.tex @@ -1315,10 +1315,60 @@ to the frequency and traffic volume of your list. perfect, although personalization can make it much more accurate. The list owner may want to receive unrecognized bounces so that they can manually disable or remove such members. + +\item[bounce_notify_owner_on_disable] + This option controls whether or not the list owner is notified + when a member's subscription is automatically disabled due to + their bounce threshold being reached. + +\item[bounce_notify_owner_on_removal] + This option controls whether or not the list owner is notified + when a member is removed from the list after their disabled + notifications have been exhausted. \end{description} \subsection{The Archiving Options Category} + +Mailman comes with a built-in web-based archiver called +\emph{Pipermail}, although it can be configured to use external, +third party archivers. + +\begin{description} + +\item[archive] + This option tells Mailman whether to archive messages it receives + or not, regardless of whether Pipermail or a third party archiver + is used. Turn this off if you don't want to archive messages. + + Note that senders can control whether their own posts are + archived, on an individual per-message basis. If the posted + message has a \mailheader{X-No-Archive} header (regardless of + value), or a \mailheader{X-Archive} header with a value of + \code{No} (case insensitive), then the message will not be + archived, although it will be treated as normal in all other + ways. + +\item[archive_private] + Controls whether Pipermail archives are private or public. + Private archives require a valid member address and password, or a + list administrator password in order to access them. This + option has no effect when a third party archiver is used. + +\item[archive_volume_frequency] + Controls how Pipermail splits messages in the archive. The most + common option is \emph{Monthly} meaning a new archive volume is + started every month. Very high volume lists may want a shorter + frequency (e.g. \emph{Weekly} or \emph{Daily}) where as lower + volume lists may want a longer frequency (e.g. \emph{Yearly}). + This option has no effect when a third party archiver is used. +\end{description} + \subsection{The Mail/News Gateway Category} + +Mailman has a sophisticated mail-to-news gateway feature. It can +independently gate messages from news to mail and vice versa, and can +even be used to manage moderated newsgroups. + \subsection{The Auto-responder Category} \subsection{The Content Filtering Category} \subsection{The Topics Category} |