Message-ID: <280436183.16910.1368914565089.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16909_1807751477.1368914565089" ------=_Part_16909_1807751477.1368914565089 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document describes the list administrator's interface for G= NU Mailman 2.1. It contains information a list owner would need to configur= e their list, either through the web interface or through email. It also co= vers the moderator's interface for approving held messages and subscription= notices, and the web interface for creating new mailing lists. In general,= it does not cover the command line interface to Mailman, installing Mailma= n, or interacting with Mailman from the point of view of the user. That inf= ormation is covered in other manuals.
I (Terri) am currently in the process of importing the 2.1 documentation= from latex. It's fairly likely that there will be syntax issues and missi= ng pieces. Please bear with me, and feel free to fix markup if you see a f= law.
Older versions of this document can be found at the following locations:=
Or the information is also available on list.org:
|Table of Contents|
This is one of a set of three documents for the various people involved = in running and using a mailing list. For the members of mailing lists (the= subscribers), we have the Mailman 2.1 Members Manual which covers things like subscribing and= unsubscribing. For the people who install and set up Mailman, we will eve= ntually have the Mailman 2.1 Site Administration Manual, which has not yet been wr= itten.
This document covers the people who run mailing lists: the list administ= rators (who can change all the list options, as well as authorize postings = that have been held for moderation), and the list moderators (who cannot mo= dify list settings).
This document does not need to be read in order, so if you just want an = answer to a specific question, jump to the appropriate place and references= to other sections will be provided when necessary or potentially helpful.<= /p>
The bulk of this document has been written by Terri Oda. Terri used to = get a lot of spam, so she did research into neat evolutionary anti-spam sol= utions. And then she thought it would be nice if her grandfather could use= the web without worrying about bad stuff getting into his computer, so she= started doing web security. All of this is a roundabout way of saying tha= t her day job is as a security researcher, and she actually doesn't conside= r herself a document writer, but she was tired of Mailman not having docume= ntation so she figured it was time to do something about it.
The original site admin docs were written by Barry Warsaw. Thanks also = go to the rest of the Mailman team who provided the inline help upon which = much of this documentation is based.
This document is now stored in the Mailman wiki http://wiki.list.org, and may be edited and a= dded to by members of the Mailman community. Please see the wiki changelogs= for more information.
Mailman has 3 interfaces:
The most commonly used interface of Mailman is the web interface. Almos= t all the options can be set from this interface, and it also provides inli= ne help and descriptions of each option. More importantly, the day-to-day = tasks of running a mailing list are handed through this interface.
Assuming a fairly standard configuration, the configuration interface ha= s a URL like this:
And the moderation interface has a very similar URL as follows:
The web domain (WEBSERVER) can't be set from the web, since it's a bit t= oo easy to render your web interface unusable by making a typo. As such, t= his setting is usually changed from the command line. The fix_url<= /strong> script is provided for this purpose. It is used in conjuction wit= h withlist as follows:
bin/withlist -l -r fix_url listname [options]
In many cases, this is the only interface a list administrator will use,= and may be the only interface the list administrator has permissions to us= e.
There is also an email interface for Mailman, allowing list admins to ad= just settings or handle caught messages without requiring them to open up a= web browser.
Since this interface is not as commonly used as the web interface, it is= highly likely that this part of the documentation will be among the last p= ieces written. If you wish to speed this up, please feel free to help fill= it in!
The web interface for moderation can be found at a URL similar to the fo= llowing, depending on your mailman config:
From here, you will see a list of anything awaiting your decision. This= is largely messages that have been caught for some reason, but may also in= clude subscription/unsubscription requests if you require admin authorizati= on before someone can join or leave the list.
Messages are "caught" in the moderation queue depending upon y= our list settings. There are a number of rules that allow you to choose wh= ich messages require moderation, but basically you want things which might = be inappropriate to be caught by these filters so a human can choose whethe= r they get sent to all subscribers or not.
For example, as an anti-spam measure, many lists only accept messages fr= om their members. Any non-member who sends a message will have it caught i= n the moderation queue. If the message turns out to be spam, it can be dis= carded, but if it turns out to be from someone posting from their work addr= ess, you may wish to send it out anyhow.
Put a link to the relevant sec= tion here
For each message displayed in the queue, Mailman will give a summary of = the message. This includes the following:
A link is provided so you can read the entire message if you want to.
There are 4 choices when it comes to moderating a message:
In addition, there is a checkbox (near the submit button) which allows y= ou to "Discard all messages marked Defer" =E2=80=93 this allows y= ou to bulk-discard spam messages and can be a very handy option. It only a= pplies to the messages displayed in the queue page as you've loaded it.
This is a setting chosen when the list was set up. If you do not wish t= o moderate subscription/unsubscription requests, you can change your list c= onfig.
Put a link to the relevant sec= tion here
The interface for moderating members joining and leaving is similar to t= hat for messages, only instead of a message summary we have the email addre= ss and name of the person under consideration.
The options for subscriptions and unsubscriptions are the same as those = for messages:
Removing/deleting mailing lists is performed with the command line tool = rmlist. rmlist has 2 modes of operating:
If list archives are retained (default behavior), the archive files are = left on the file system. The Mailman administrator can still access the arc= hives through web interface (if the URL has been bookmarked) but list users= (and the list administrator) will not have access unless another web servi= ce is making the list archives accessible (for example through a search eng= ine).
NOTE removing the list completely requires manual editing of the mail al= iases file, that is, /etc/aliases
Once a list has been removed, it may be re-added with the newlis= t command line tool, however all information about the list (for e= xample, description and previous members) will be missing. However the arch= ives will then be available to all users via the web interface.
It is also possible to allow mailing list removal with the option/variab= le OWNERS_CAN_DELETE_THEIR_OWN_LISTS in mm_cfg.py, by defa= ult this option is disabled.