This shows you the differences between two versions of the page.
configuring_mailman_for_ubuntu [2007/01/24 16:43] adam |
configuring_mailman_for_ubuntu [2016/11/25 22:38] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Configuring [[http:// | ||
- | |||
- | Taken from [[http:// | ||
- | |||
- | Draft - Started 17 December 2005 | ||
- | Released to the unsuspecting world - 21 December 2005 | ||
- | Latest minor revision - 24 August 2006 at 01:30 PM | ||
- | |||
- | Creative Commons License | ||
- | This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License. | ||
- | Software selected | ||
- | |||
- | Install | ||
- | |||
- | There is only one package you'll need to add - mailman. Use Synaptic Package Manager or apt-get to add it to your machine. | ||
- | |||
- | It's my belief the Ubuntu install files leave you with the wrong file ownerships, so if you haven' | ||
- | $ sudo -s (and enter your password) | ||
- | Mailman includes a handy script to make check your permissions. It's in /usr/sbin/ so it should be on root's path. | ||
- | # check-perms | ||
- | - and note the massive problems. To fix permissions, | ||
- | # check-perms -f | ||
- | A bunch of changes scroll by, but did it get them all? | ||
- | # check-perms -f | ||
- | Nope; still errors. In fact, you need to | ||
- | # cd / | ||
- | # chown -R list:list * | ||
- | |||
- | Of course I'm using example.com for this HOWTO. Substitute your own domain name. | ||
- | Mailman configuration files | ||
- | |||
- | The Mailman configuration files are in / | ||
- | |||
- | |||
- | | ||
- | |||
- | | ||
- | |||
- | | ||
- | | ||
- | |||
- | I'm not sure if you need this line - can someone tell me? | ||
- | |||
- | | ||
- | |||
- | Apache 2 config files are in / | ||
- | |||
- | | ||
- | | ||
- | |||
- | < | ||
- | AllowOverride None | ||
- | Options ExecCGI | ||
- | Order allow,deny | ||
- | Allow from all | ||
- | </ | ||
- | Alias /pipermail/ / | ||
- | < | ||
- | Options Indexes MultiViews FollowSymLinks | ||
- | AllowOverride None | ||
- | Order allow,deny | ||
- | Allow from all | ||
- | </ | ||
- | |||
- | Optional - pipermail is one of those directory names which hangs around for historical reasons but makes little sense to users. You might want to add a more sensible-sounding alias for the mailing list archives. | ||
- | |||
- | Alias /archives/ / | ||
- | < | ||
- | Options Indexes MultiViews FollowSymLinks | ||
- | AllowOverride None | ||
- | Order allow,deny | ||
- | Allow from all | ||
- | </ | ||
- | |||
- | Now add a symlink to this file so Apache will use your new Mailman aliases the next time it starts: | ||
- | |||
- | # cd / | ||
- | # ln -s / | ||
- | |||
- | All your configuration files are now set. Activate everything by restarting your services: | ||
- | |||
- | # / | ||
- | # / | ||
- | # / | ||
- | |||
- | Create your first list | ||
- | |||
- | Mailman doesn' | ||
- | |||
- | # newlist mailman | ||
- | |||
- | You'll be asked for an administrator email address - give it yours - and a password. If all goes well you should immediately get an email welcoming you to your new list. The email will have a URL where you can go and experiment with the web-based mailman configuration. There' | ||
- | Adding MySQL aliases | ||
- | |||
- | If you've installed phpmyadmin as Ivar suggests you can use a GUI interface, otherwise you'll edit your MySQL database through the command line. Insert the following entries into the aliases table of the maildb database: | ||
- | |||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | |||
- | Your ' | ||