Lars Sommer, [email protected], 2009-03-17
DISCLAIMER: This is a personal note made for personal usage. It might not be easy usable nor explaining.
This setup is installing Mailman on a working mailserver running Postfix, with virtual domains in MySQL,
and with a working webserver running Apache 2.
Install the port
Enable the option POSTFIX
Add the the bottom of /usr/local/mailman/Mailman/mm_cfg.py:
SMTPHOST = ‘lasg.dk’
MTA = ‘Postfix’
POSTFIX_STYLE_VIRTUAL_DOMAINS = [‘lasg.dk’,’hosting.lasg.dk’]
Add to postfix/main.cf:
alias_maps = hash:/usr/local/mailman/data/aliases
Edit in postfix/main.cf, the virtual_alias_maps line:
virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf,
Add to /etc/rc.conf:
Check permissions on /usr/local/mailman/data/
aliases, aliases.db, virtual-mailman, virtual-mailman.db
to be in group “mailman” and with permissions rw-rw—-
This is a very simple config for Apache.
This can be inserted within a virtual host configuration scope.
This will allow everyone to access archives through /pipermail, and see all lists.
Perhaps a more secure approach would be to put ssl, htaccess and htpasswd on.
ScriptAlias /mailman “/usr/local/mailman/cgi-bin”
Alias /pipermail “/usr/local/mailman/archives/public”
Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all
Configure and starting up:
to set the master admin password for Mailman.
Create an initial required maillist, called mailman:
You will be asked for email address and a password
Reload postfix and start mailman:
It should work.
All administrative scripts are located in