Differences

This shows you the differences between two versions of the page.

--- build:lists [2008/03/05 19:29]
4.245.78.137
+++ build:lists [2018/05/28 02:25]
SLUUG Administration [cron]
@@ Line 55: / Line 55: @@
-NOTE: MailMan requires at least Python 2.4. Debian 4.0 meets this requirement. Debian 3.1 did not, so we had to install Pyton 2.4 and use update-alternatives to make it the default version. Debian 3.1 also required installing libdb2.
+NOTE: MailMan requires at least Python 2.4. Debian 4.0 meets this requirement. Debian 3.1 did not, so we had to install Python 2.4 and use update-alternatives to make it the default version. Debian 3.1 also required installing libdb2.
 =====Pre-installation Steps=====
-As root, create /usr/local/mailman-2.1.9, make it owned by group mailman, and chgrp 2775 /usr/local/mailman.
+As root, create the Mailman directory, set its ownership and permissions:
+<code rootshell>
+mkdir /usr/local/mailman-2.1.9
+chown mailman /usr/local/mailman-2.1.9
+chmod 2775 /usr/local/mailman-2.1.9
+ln -s mailman-2.1.9 /usr/local/mailman
+</code>
 =====Extract and Prepare Source=====
-The Debian Mailman package did not include search capibility. To enable search Mailman has to be compiled with htdig.  Extract the source file into /usr/local/src/mailman-2.1.9 and move the patch into that directory. gunzip the patch.
+The Debian Mailman package did not include search capability. To enable search Mailman has to be compiled with htdig.  Extract the source file into /usr/local/src/mailman-2.1.9 and move the patch into that directory. gunzip the patch.
 Disable most language support. This is an ugly hack to get around a problem with Japanese-language support in python on Debian Etch. Comment out the following line in messages/Makefile.in:
@@ Line 223: / Line 230: @@
 </code>
+Edit ''crontab'' before or after installation to:
+  * Comment the ''gate_news'' entry.  We are not using any usenet gateway.
 =====Copy Apache Images to Mailman=====
 <code root>
@@ Line 405: / Line 414: @@
 Configure the bud_test list at [[http://bud.sluug.org/mailman/admin/bud_test/]]
+=====Creating lists for virtual domains=====
+* Make sure your domain's MX records point to bud.sluug.org
+* Make sure your domain is included in virtual_alias_maps in /etc/postfix/main.cf
+* In /etc/postfix/virtual, add a new entry for your list. The LHS should be the address to which users send their posts, and the RHS should be the name of the list you are creating (no domain part, just the list name).
+* Run
+<code root>
+# postmap /etc/postfix/virtual
+</code>
+* In /usr/local/mailman/Mailman/mm_cfg.py, add your domain to POSTFIX_STYLE_VIRTUAL_DOMAINS. If there needs to be more than one domain set in POSTFIX_STYLE_VIRTUAL_DOMAINS, this variable probably needs to be set in python list syntax.
+* Restart mailman
+<code root>
+# /etc/init.d/mailman restart
+</code>
+* Create a new vhost in /etc/apache2/sites-available for your virtual domain if it doesn't already exist. Using /etc/apache2/sites-available/www.sluug.org as an example, copy the mailman <directory> containers into your vhost, making sure to update passwords, descriptions, and archive paths as necessary.
+* Restart apache
+<code root>
+# apache2ctl graceful
+</code>
+* Create your list
+<code root>
+#/usr/local/mailman/bin/newlist list@domain
+</code>
+You will be prompted for the email address of a list admin and for an administrative password for the list. Check that email account for a welcome mail. Go to the admin URL in that mail and select "Privacy Options"->"Recipient Filters". Add your list's email address to the box labeled "Alias names (regexps) which qualify as explicit to or cc destination names for this list." If you don't, all posts to your new list will be held for admin approval with a message about implicit destinations.
+* Send some test mails to verify that the list is working as expected.
+Currently we are hosting announce@stlwebdev.org and discuss@stlwebdev.org.
 =====Mailman TODO:=====

SLUUG Wiki

User Tools

Site Tools

Differences

Page Tools