特殊:Badtitle/NS100:Mailman

来自Ubuntu中文
Wikibot留言 | 贡献2008年10月19日 (日) 23:47的版本
跳到导航跳到搜索
可打印版本不再受到支持且可能有渲染错误。请更新您的浏览器书签并改用浏览器默认打印功能。

{{#ifexist: :Mailman/zh | | {{#ifexist: Mailman/zh | | {{#ifeq: {{#titleparts:Mailman|1|-1|}} | zh | | }} }} }} {{#ifeq: {{#titleparts:Mailman|1|-1|}} | zh | | }}

This guide explains how to setup Mailman mailing list software with the Apache web server and either the Exim4 or Postfix mail servers on Ubuntu. The intended audience is experienced linux users and system administrators.

Introduction

If you are new to Mailman, this section provides a quick introduction to Mailman. Mailman is an open source program for managing electronic mail discussions and e-newsletter lists. Many open source mailing lists (including all the Ubuntu mailing lists) use Mailman as their mailing list software. It is powerful, easy to install and easy to maintain.

Assumptions

It is assumed that you know how to run linux commands, edit files, and start and stop services in the linux system. It is also assumed that you have administrative access to an Ubuntu system, that you have internet connection and that you have configured /etc/apt/sources.list.

Installation

Mailman provides the web interface for the administrators and users. Mailman uses an external mailserver to send/receive emails. It works perfectly with the following mailservers:

In this section, we will see howto install Mailman, Apache web server and Exim or Postfix mail server. If you wish to install Mailman with another mail server, please refer the reference pages given at the end of the guide.

Apache2

Apache2 is already in the repository. Install the following packages: apache2 (see InstallingSoftware).

Mailman

Mailman is Main in the repository. Install the following packages: mailman (see InstallingSoftware). It copies the installation files in /var/lib/mailman. It installs the cgi scripts in /usr/lib/cgi-bin/mailman directory. The package creates a 'list' user and a 'list' group. The mailman process is be owned by this user.

Mail server installation

You only need one Mail Transport Agent (MTA) installed and configured in order to use Mailman. Here are instructions and for installing Exim4 and Postfix.

Exim4

Exim4 is already in the repository. Install the following packages: exim4 (see InstallingSoftware). See the Exim4 page for more details on installing and configuring Exim4. This example uses split configuration (Exim4 default, multiple configuration files), not monolithic/unsplit configuration (a single file).

Postfix

Install the following packages: postfix (see InstallingSoftware). Just choose Internet Site and default options. For further details on Postfix installation, visit the Postfix page.

Configuration

This section assumes you have successfully completed the installation of Mailman, Apache and a Mail server. Now you just need to configure them. At the end of this section, your Mailman will be ready to rock!

Apache Configuration

An example Apache configuration file comes with Mailman and is placed in /etc/mailman/apache.conf. In order for Apache to use the config file it needs to be copied to /etc/apache2/sites-enabled:

sudo ln -s ../../mailman/apache.conf /etc/apache2/sites-enabled/mailman

This will setup a new Apache VirtualHost for the Mailman administration site. Once you have created the symbolic link, you'll need to enable it and restart Apache:

sudo /etc/init.d/apache2 restart

Postfix Configuration

For this integration, we will associates the domain lists.example.com with the mailing lists. As a consequence, the domain will be reserved for the mailing-list traffic. You can nevertheless have a website to this domain (usually, the domain lists.example.com is used by the mailing list system and for the mailman web interface). You can use the postconf command to add the necessary configuration to /etc/postfix/main.cf:

sudo postconf -e 'relay_domains = lists.example.com'
sudo postconf -e 'transport_maps = hash:/etc/postfix/transport'
sudo postconf -e 'mailman_destination_recipient_limit = 1'

In /etc/postfix/master.cf double check that you have the following transport:

mailman   unix  -       n       n       -       -       pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

It calls the postfix-to-mailman.py script when a mail is delivered to a list. Associate the domain lists.example.com to the mailman transport with the transport map. Edit the file /etc/postfix/transport:

lists.example.com      mailman:

Now have Postfix build the transport map by entering the following from a terminal prompt:

sudo postmap -v /etc/postfix/transport

Then restart Postfix to enable the new configurations:

sudo /etc/init.d/postfix restart

That's all ! It is very easy and very efficient.

Exim4 Configuration

Once exim4 is installed, you can run it using the following command:

# /etc/init.d/exim4 start

In order to make mailman work with exim4, you need to configure exim4. As mentioned earlier, by default, exim4 uses multiple configuration files of different types. For details, please refer Exim website. To run mailman, we should make add new configuration file to each of the following configuration types:

  • Main
  • Transport
  • Router

Exim creates a master configuration file, by sorting all these mini configuration files. So, the order of these configuration files is important. This is accomplished using certain file names prefixed by a number. See below.

Main

All the configuration files belonging to main type are stored in /etc/exim4/conf.d/main/ directory. You can add the following content in a new file. You may name it as 04_exim4-config_mailman::

# start
# Home dir for your Mailman installation -- aka Mailman's prefix
# directory.
# By default this is set to "/usr/local/mailman"
# On a Red Hat/Fedora system using the RPM use "/var/mailman"
# On Debian using the deb package use "/var/lib/mailman"
# This is normally the same as ~mailman
MM_HOME=/var/lib/mailman
#
# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.  Value is normally "mailman"
MM_UID=list
MM_GID=list
#
# Domains that your lists are in - colon separated list
# you may wish to add these into local_domains as well
domainlist mm_domains=lists.example.com
#
# -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
#
# These values are derived from the ones above and should not need
# editing unless you have munged your mailman installation
#
# The path of the Mailman mail wrapper script
MM_WRAP=MM_HOME/mail/mailman
#
# The path of the list config file (used as a required file when
# verifying list addresses)
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
# end

IMPORTANT: Please replace lists.example.com with your own domain

Transport

All the configuration files belonging to transport type are stored in /etc/exim4/conf.d/transport/ directory. You can add the following content in a new file. You may name it as 40_exim4-config_mailman::

mailman_transport:
   driver = pipe
   command = MM_WRAP \
               '${if def:local_part_suffix \
                     {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1\}\}\} \
                     {post}}' \
               $local_part
   current_directory = MM_HOME
   home_directory = MM_HOME
   user = MM_UID
   group = MM_GID

IMPORTANT: In the above configuration, in line no 5, I've escaped three braces (\}\}\}) to make it compatible with this document. Please unescape it (by deleting the backslashes before each brace) when you save this file.

Router

All the configuration files belonging to router type are stored in /etc/exim4/conf.d/router/ directory. You can add the following content in a new file. You may name it as 101_exim4-config_mailman::

mailman_router:
   driver = accept
   require_files = MM_HOME/lists/$local_part/config.pck
   local_part_suffix_optional
   local_part_suffix = -bounces : -bounces+* : \
                       -confirm+* : -join : -leave : \
                       -owner : -request : -admin
   transport = mailman_transport

IMPORTANT: The order of main and transport configuration files can be in any order. But, the order of router configuration files must be in the same order. This particular file, must appear before 200_exim4-config_primary file. These two configuration files contain same type of information. The first file takes the precedence. For more details, please refer to the exim website or the references section in this page.

Mailman Configuration

Once mailman is installed, you should create the default mailing list. Run the following command:

  # sudo newlist mailman
  Enter the email of the person running the list: bhuvaneswaran at NOSPAM gmail.com
  Initial mailman password:
  To finish creating your mailing list, you must edit your /etc/aliases (or
  equivalent) file by adding the following lines, and possibly running the
  `newaliases' program:

  ## mailman mailing list
  mailman:              "|/var/lib/mailman/mail/mailman post mailman"
  mailman-admin:        "|/var/lib/mailman/mail/mailman admin mailman"
  mailman-bounces:      "|/var/lib/mailman/mail/mailman bounces mailman"
  mailman-confirm:      "|/var/lib/mailman/mail/mailman confirm mailman"
  mailman-join:         "|/var/lib/mailman/mail/mailman join mailman"
  mailman-leave:        "|/var/lib/mailman/mail/mailman leave mailman"
  mailman-owner:        "|/var/lib/mailman/mail/mailman owner mailman"
  mailman-request:      "|/var/lib/mailman/mail/mailman request mailman"
  mailman-subscribe:    "|/var/lib/mailman/mail/mailman subscribe mailman"
  mailman-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe mailman"

  Hit enter to notify mailman owner...

  # 

Once mailman is installed and the default mailing list created, you can run it using the following command:

sudo /etc/init.d/mailman start

We have configured Exim4 or Postfix to recognize all emails from Mailman. So, it's not mandatory to make any new entries in /etc/aliases. If you have made any changes to the configuration files, please ensure that you restart those services, before continuing to next section.

Administration

Web administration

In this section, we assume you have done the default installation. The Mailman CGI scripts are still in /usr/lib/cgi-bin/mailman directory. Mailman provides web based administration facility. To access this page, point your browser to the following url: http://hostname/cgi-bin/mailman/admin The default mailing list, 'mailman' would appear in this screen. If you click the mailing list name, it would ask for authentication password. If you enter the correct password, you would be able to change administrative settings of this mailing list. You can create new mailing list using command line utilility (newlist). Alternatively, you can create new mailing list using web interface. For each list, you have three web sections:

  • http://hostname/cgi-bin/mailman/admin/list: admin interface for the list list.
  • http://hostname/cgi-bin/mailman/listinfo/list: user interface for the list list.
  • http://hostname/cgi-bin/mailman/admindb/list: pending messages waiting for approval.

Command line interface

Mailman also have a set of command line tools. Here are the most important:

  • newlist: add a new list
  • rmlist ''list'': delete a list
  • list_lists: list all the lists
  • list_members ''list'': list all the members of the list
  • add_members ''[email protected]'' ''list'': add e-mail [email protected] to the list list.
  • remove_members ''[email protected]'' ''list'': remove e-mail [email protected] to the list list
  • mmsitepass: define a site password to access administration web interfaces

Users

Mailman provides web based interfaces for users. To access this page, point your browser to the following url: http://hostname/cgi-bin/mailman/listinfo The default mailing list, 'mailman' would appear in this screen. If you click the mailing list name, it would display the subscription form. You can enter your email address, name (optional) and password to subscribe. An email intimation would be sent to you. You can follow the instructions in the email to subscribe.

References

Hope this document is useful. Feedbacks are welcome to bhuvaneswaran at NOSPAM gmail.com.