<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gaia Environmental Sciences &#187; Uncategorized</title>
	<atom:link href="http://gaiaes.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://gaiaes.com</link>
	<description>Energy and Computer Consulting</description>
	<lastBuildDate>Sat, 30 Jan 2010 02:31:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Configuring Mailman on Ubuntu with Postfix</title>
		<link>http://gaiaes.com/2009/03/configuring-mailman-on-ubuntu-with-postfix/</link>
		<comments>http://gaiaes.com/2009/03/configuring-mailman-on-ubuntu-with-postfix/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 05:09:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Server Administration]]></category>

		<guid isPermaLink="false">http://gaiaes.com/?p=25</guid>
		<description><![CDATA[Mailman is one of the most flexible mail list software packages but can be difficult to set up. This article looks at one of the simpler configurations on Ubuntu 8.10 using Postfix and the Apache web server. It assumes that there are two domains, default.web and virtual.web (to be replaced throughout with the actual domain [...]]]></description>
			<content:encoded><![CDATA[<p>Mailman is one of the most flexible mail list software packages but can be difficult to set up.  This article looks at one of the simpler configurations on Ubuntu 8.10 using Postfix and the Apache web server.  It assumes that there are two domains, default.web and virtual.web (to be replaced throughout with the actual domain names).  Furthermore, these domains have the subdomains www, mail and lists where the last subdomain is used to separate mail for the mailing lists from other mail processed by the server.  It is also assumed that Postfix and Apache are already installed on the server and are working correctly.</p>
<p><strong>Mailman</strong></p>
<p>Start by installing Mailman.</p>
<blockquote><p>apt-get install mailman</p></blockquote>
<p>Running the script to check the permissions.</p>
<blockquote><p>check_perms</p></blockquote>
<p>This seems to indicate that some of the files have the wrong permissions.  To fix them run the script with the -f flag.</p>
<blockquote><p>check_perms -f</p></blockquote>
<p>This should be run twice.  There may still be some errors reported.  This is because there are some symbolic links and the script checks the permissions for the link instead of the permissions of the target.</p>
<p>Change to the /etc/mailman directory.  Here there is a script postfix-to-mailman.py<br />
which we will use to make the configuration simpler and avoid the need to create aliases.  Inside the script are instructions upon which these instructions are based.</p>
<p>Check to make sure there is a link from /var/lib/mailman/bin/postfix-to-mailman.py to /etc/mailman/postfix-to-mailman.py.</p>
<p>Edit the following parameters in /etc/mailman/mm_cfg.py and if they do not already exist, add them to the file.</p>
<blockquote><p>MTA=None # No MTA processing req&#8217;d for Ubuntu/virtual/postfix-to-mailman.py<br />
DEFAULT_URL_PATTERN = &#8216;http://%s/mailman/&#8217;<br />
PRIVATE_ARCHIVE_URL = &#8216;/cgi-bin/mailman/private&#8217;<br />
IMAGE_LOGOS         = &#8216;/images/mailman/&#8217;<br />
DEFAULT_EMAIL_HOST = &#8216;lists.default.web&#8217;<br />
DEFAULT_URL_HOST = &#8216;lists.default.web&#8217;<br />
DEB_LISTMASTER = &#8216;listmaster@default.web&#8217;<br />
add_virtualhost(&#8216;lists.virtual.web&#8217;, &#8216;lists.virtual.web&#8217;)<br />
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)</p></blockquote>
<p>listmaster@default.web should be replaced with an actual email address.  If there<br />
are additional virtual domains they can be similarly listed.</p>
<p><strong>Apache</strong></p>
<p>The URL pattern used above requires editing the file /etc/mailman/apache.conf and uncommenting the following line.</p>
<blockquote><p>ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/</p></blockquote>
<p>Create a link to point to the file we just edited.</p>
<blockquote><p>ln -s ../../mailman/apache.conf /etc/apache2/sites-available/mailman</p></blockquote>
<p>That is all that is required.  Now enable the site.</p>
<blockquote><p>a2ensite mailman</p></blockquote>
<p>The reload the Apache server so it picks up the new site.</p>
<blockquote><p>/etc/init.d/apache2 reload</p></blockquote>
<p><strong>Postfix</strong></p>
<p>Now it is time to configure Postfix for Mailman.  Create the file /etc/postfix/transport.</p>
<blockquote><p>lists.default.web   mailman:<br />
lists.virtual.web    mailman:</p></blockquote>
<p>Note that this is telling Postfix to send any mail to the lists subdomains to Mailman to be processed.</p>
<p>The postmap command is used to generate transport.db</p>
<blockquote><p>postmap transport</p></blockquote>
<p>Now edit the /etc/postfix/master.cf file.  The following line should appear but may need to be edited.</p>
<blockquote><p>mailman   unix  &#8211;       n       n       &#8211;       &#8211;       pipe<br />
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py<br />
${nexthop} ${mailbox}</p></blockquote>
<p>Make sure there are two &#8220;n&#8221;s as older versions only have one.  Edit /etc/postfix/main.cf.</p>
<blockquote><p>relay_domains = lists.default.web, lists.virtual.web<br />
transport_maps = hash:/etc/postfix/transport<br />
mailman_destination_recipient_limit = 1</p></blockquote>
<p>Reload Postfix to pick up the changes.</p>
<blockquote><p>/etc/init.d/postfix reload</p></blockquote>
<p><strong>Mailing lists</strong></p>
<p>Before we can start Mailman we need to set up the mailman list which is used for sending out administrative mail for Mailman.  Mailman will refuse to start until this step is completed.</p>
<blockquote><p>newlist mailman</p></blockquote>
<p>Enter an email address and password for the administrator of this administrative mailing list.  To configure this list run the script</p>
<blockquote><p>config_list -i /var/lib/mailman/data/sitelist.cfg mailman</p></blockquote>
<p>This should not be used for other mailing lists as it may not have appropriate settings for them.</p>
<p>In addition to a site-wide mailing list there is a site password which should be set.</p>
<blockquote><p>mmsitepass</p></blockquote>
<p>While a site password can be used to create mailing lists you may also want to create an optional list creator password to give to people instead of the site password.</p>
<blockquote><p>mmsitepassword -c</p></blockquote>
<p>Now we are ready to start Mailman.</p>
<blockquote><p>/etc/init.d/mailman start</p></blockquote>
<p>Mailman, Apache and Postfix should now all be working.</p>
<p><strong>Additional matters</strong></p>
<p>Before ending these instructions some additional information.  There are Mailman scripts used for administrative purposes which are covered at http://www.gnu.org/software/mailman/site.html.</p>
<p>To create a new mailing list, go to http://lists.default.web/mailman/create or http://lists.virtual.web/mailman/create depending on which domain you wish the list to use.</p>
]]></content:encoded>
			<wfw:commentRss>http://gaiaes.com/2009/03/configuring-mailman-on-ubuntu-with-postfix/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
