/[gentoo]/xml/htdocs/doc/en/virt-mail-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/virt-mail-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.16 Revision 1.28
1<?xml version = '1.0' encoding = 'UTF-8'?> 1<?xml version = '1.0' encoding = 'UTF-8'?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/virt-mail-howto.xml,v 1.28 2004/03/04 18:24:44 swift Exp $ -->
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 4
4<guide link=" /doc/en/virt-mail-howto.xml" > 5<guide link=" /doc/en/virt-mail-howto.xml" >
5<title>Virtual Mailhosting System Guide</title> 6<title>Virtual Mailhosting System with Postfix Guide</title>
6<author title="Author" > 7<author title="Author" >
7<mail link="antifa@gentoo.org" >Ken Nowack</mail> 8<mail link="antifa@gentoo.org" >Ken Nowack</mail>
8</author> 9</author>
9<author title="Author" > 10<author title="Author" >
10<mail link="ezra@revoltltd.org" >Ezra Gorman</mail> 11<mail link="ezra@revoltltd.org" >Ezra Gorman</mail>
11</author> 12</author>
13<author title="Editor">
14<mail link="klasikahl@gentoo.org" >Zack Gilburd</mail>
15</author>
12<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract> 16<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract>
13<version>1.0.2</version> 17<version>1.0.10</version>
14<date>7 Aug 2003</date> 18<date>March 4, 2004</date>
15<!-- 19<!--
16 20
17Contents 21Contents
18 22
19I. Introduction 23I. Introduction
32XIV. Wrap Up 36XIV. Wrap Up
33XV. Troubleshooting 37XV. Troubleshooting
34 38
35--><chapter> 39--><chapter>
36<title>Introduction</title> 40<title>Introduction</title>
41<section>
37<body> 42<body>
38<p>For most gentoo users, a simple mail client and fetchmail will do. However, if you're hosting a domain with your system, you'll need a full blown MTA (Mail Transfer Agent). And if you're hosting multiple domains, then you'll definitely need something more robust to handle all of the email for your users. This system was designed to be an elegant solution to that problem.</p> 43<p>For most gentoo users, a simple mail client and fetchmail will do. However, if you're hosting a domain with your system, you'll need a full blown MTA (Mail Transfer Agent). And if you're hosting multiple domains, then you'll definitely need something more robust to handle all of the email for your users. This system was designed to be an elegant solution to that problem.</p>
39<p>A virtual mail system needs to be able to handle email for numerous domains with multiple users over a variety of interfaces. This presents some issues that must be dealt with. For instance, what if you have two users on different domains that want the same user name? If you are providing imap access and smtp-auth, how do combine the various authentication daemons into a single system? How do you provide security for the numerous components that comprise the system? How do you manage it all?</p> 44<p>A virtual mail system needs to be able to handle email for numerous domains with multiple users over a variety of interfaces. This presents some issues that must be dealt with. For instance, what if you have two users on different domains that want the same user name? If you are providing imap access and smtp-auth, how do combine the various authentication daemons into a single system? How do you provide security for the numerous components that comprise the system? How do you manage it all?</p>
40<p>This howto will show you how to set up with a mail system capable of handling mail for as many domains as your hardware can handle, supports virtual mail users that don't require shell accounts, has domain specific user names, can authenticate web, imap, smtp, and pop3 clients against a single database, utilizes ssl for transport layer security, has a web interface, can handle mailing lists for any domain on the machine, and is controlled by a nice, central and easy mysql database. </p> 45<p>This howto will show you how to set up with a mail system capable of handling mail for as many domains as your hardware can handle, supports virtual mail users that don't require shell accounts, has domain specific user names, can authenticate web, imap, smtp, and pop3 clients against a single database, utilizes ssl for transport layer security, has a web interface, can handle mailing lists for any domain on the machine, and is controlled by a nice, central and easy mysql database. </p>
41<p>There are quite a variety of ways to go about setting up a virtual mailhosting system. With so may options, another may be the best choice for your specific needs. Consider investigating <uri>http://www.qmail.org/</uri> and <uri>http://www.exim.org/</uri> to explore your options. </p> 46<p>There are quite a variety of ways to go about setting up a virtual mailhosting system. With so may options, another may be the best choice for your specific needs. Consider investigating <uri>http://www.qmail.org/</uri> and <uri>http://www.exim.org/</uri> to explore your options. </p>
42<p>The following packages are used in this setup: 47<p>The following packages are used in this setup:
43 48
44 apache, courier-imap, pam_mysql, postfix, mod_php, mod_ssl, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p> 49 apache, courier-imap, pam_mysql, postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p>
45<p>Make sure to turn on the following USE variables in <path>/etc/make.conf</path> before compiling the packages: <c>USE=&quot;mysql imap libwww maildir sasl ssl&quot;</c>. Otherwise you will most likely have to recompile things to get the support you need for all the protocols. Further, it's a good idea to turn off any other mail and network variables, like ipv6.</p> 50<p>Make sure to turn on the following USE variables in <path>/etc/make.conf</path> before compiling the packages: <c>USE=&quot;mysql imap libwww maildir sasl ssl&quot;</c>. Otherwise you will most likely have to recompile things to get the support you need for all the protocols. Further, it's a good idea to turn off any other mail and network variables, like ipv6.</p>
46<impo>This howto was written for postfix-2.0.x. If you are using postfix &lt; 2 some of the variables in this document will be different. It is recommended that you upgrade. Some other packages included in this howto are version sensitive as well. You are advised to read the documentation included with packages if you run into issues with this.</impo> 51<impo>This howto was written for postfix-2.0.x. If you are using postfix &lt; 2 some of the variables in this document will be different. It is recommended that you upgrade. Some other packages included in this howto are version sensitive as well. You are advised to read the documentation included with packages if you run into issues with this.</impo>
47<impo>This document uses apache-1.3.x. Apache-2 has been marked stable in portage. However there are still a number of issues with php integration. Until php support in apache-2.0.x is marked stable, this guide will continue to use the 1.3.x version.</impo> 52<impo>This document uses apache-1.3.x. Apache-2 has been marked stable in portage. However there are still a number of issues with php integration. Until php support in apache-2.0.x is marked stable, this guide will continue to use the 1.3.x version.</impo>
48<impo>You need a domain name to run a public mail server, or at least an MX record for a domain. Ideally you would have control of at least two domains to take advantage of your new virtual domain functionality.</impo> 53<impo>You need a domain name to run a public mail server, or at least an MX record for a domain. Ideally you would have control of at least two domains to take advantage of your new virtual domain functionality.</impo>
49<impo>Make sure <path>/etc/hostname</path> is set to the right hostname for your mail server. Verify your hostname is set correctly with <c>hostname</c>. Also verify that there are no conflicting entries in <path>/etc/hosts</path>.</impo> 54<impo>Make sure <path>/etc/hostname</path> is set to the right hostname for your mail server. Verify your hostname is set correctly with <c>hostname</c>. Also verify that there are no conflicting entries in <path>/etc/hosts</path>.</impo>
50<note>It is recommended that you read this entire document and familiarize yourself with all the steps before attempting the install. If you run into problems with any of the steps, check the troubleshooting guide at the end of this document. Also, not all the referenced packages are necessary, this set up is very flexible. For instance, if you do not desire a web interface, feel free to skip the squirrelmail section.</note> 55<note>It is recommended that you read this entire document and familiarize yourself with all the steps before attempting the install. If you run into problems with any of the steps, check the troubleshooting guide at the end of this document. Also, not all the referenced packages are necessary, this set up is very flexible. For instance, if you do not desire a web interface, feel free to skip the squirrelmail section.</note>
51</body> 56</body>
57</section>
52</chapter> 58</chapter>
59
53<chapter> 60<chapter>
54<title>Postfix Basics</title> 61<title>Postfix Basics</title>
62<section>
55<body> 63<body>
56<pre caption="Install postfix" ># <i>emerge postfix</i> 64<pre caption="Install postfix" ># <i>emerge postfix</i>
57</pre> 65</pre>
58<warn>Verify that you have not installed any other MTA, such as ssmtp, exim, or qmail, or you will surely have BIG problems.</warn> 66<warn>Verify that you have not installed any other MTA, such as ssmtp, exim, or qmail, or you will surely have BIG problems.</warn>
59<p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p> 67<p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p>
85# <i>/etc/init.d/postfix start</i> 93# <i>/etc/init.d/postfix start</i>
86</pre> 94</pre>
87<p>Now that postfix is running, fire up your favorite console mail client and send yourself an email. I use <c>mutt</c> for all my console mail. Verify that postfix is delivering mail to local users, once that's done, we're on to the next step.</p> 95<p>Now that postfix is running, fire up your favorite console mail client and send yourself an email. I use <c>mutt</c> for all my console mail. Verify that postfix is delivering mail to local users, once that's done, we're on to the next step.</p>
88<note>I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto. </note> 96<note>I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto. </note>
89</body> 97</body>
98</section>
90</chapter> 99</chapter>
91<chapter> 100<chapter>
92<title>Courier-imap</title> 101<title>Courier-imap</title>
102<section>
93<body> 103<body>
94<pre caption="Install courier-imap" ># <i>emerge courier-imap</i> 104<pre caption="Install courier-imap" ># <i>emerge courier-imap</i>
95</pre> 105</pre>
96<pre caption="Courier-imap configuration" > 106<pre caption="Courier-imap configuration" >
97# <i>cd /etc/courier-imap</i> 107# <i>cd /etc/courier-imap</i>
112# <i>/etc/init.d/courier-pop3d start</i> 122# <i>/etc/init.d/courier-pop3d start</i>
113# <i>/etc/init.d/courier-pop3d-ssl start</i> 123# <i>/etc/init.d/courier-pop3d-ssl start</i>
114</pre> 124</pre>
115<p>Start up your favorite mail client and verify that all connections you've started work for receiving and sending mail. Now that the basics work, we're going to do a whole bunch of stuff at once to get the rest of the system running. Again, please verify that what we've installed already works before progressing.</p> 125<p>Start up your favorite mail client and verify that all connections you've started work for receiving and sending mail. Now that the basics work, we're going to do a whole bunch of stuff at once to get the rest of the system running. Again, please verify that what we've installed already works before progressing.</p>
116</body> 126</body>
127</section>
117</chapter> 128</chapter>
118<chapter> 129<chapter>
119<title>Cyrus-sasl</title> 130<title>Cyrus-sasl</title>
131<section>
120<body> 132<body>
121<p>Next we're going to install cyrus-sasl. Sasl is going to play the role of actually passing your auth variables to pam, which will in turn pass that information to mysql for authentication of smtp users. For this howto, we'll not even try to verify that sasl is working until mysql is set up and contains a test user. Which is fine since we'll be authenticating against mysql in the end anyway.</p> 133<p>Next we're going to install cyrus-sasl. Sasl is going to play the role of actually passing your auth variables to pam, which will in turn pass that information to mysql for authentication of smtp users. For this howto, we'll not even try to verify that sasl is working until mysql is set up and contains a test user. Which is fine since we'll be authenticating against mysql in the end anyway.</p>
122<note>Now for some reason, sasl will not play nicely with pam against the shadow file. I banged my head against this problem for, well, a long time. If anyone knows why sasl will not auth against the shadow file in its current gentoo incarnation, please <mail link="ken@kickasskungfu.com" >email me</mail> as I'd love to hear a solution to this.</note> 134<note>Now for some reason, sasl will not play nicely with pam against the shadow file. I banged my head against this problem for, well, a long time. If anyone knows why sasl will not auth against the shadow file in its current gentoo incarnation, please <mail link="ken@kickasskungfu.com" >email me</mail> as I'd love to hear a solution to this.</note>
123<pre caption="Configuring and installing the cyrus-sasl ebuild" > 135<pre caption="Configuring and installing the cyrus-sasl ebuild" >
124# <i>USE='-ldap -mysql' emerge cyrus-sasl</i> 136# <i>USE='-ldap -mysql' emerge cyrus-sasl</i>
125<codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote> 137<codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote>
126<codenote>so we need to turn them off for this build.</codenote> 138<codenote>so we need to turn them off for this build.</codenote>
127</pre> 139</pre>
128<p>Next, edit <path>/usr/lib/sasl2/smtp.conf</path>.</p> 140<p>Next, edit <path>/etc/sasl2/smtpd.conf</path>.</p>
129<pre caption="Starting sasl" > 141<pre caption="Starting sasl" >
130# <i>nano -w /usr/lib/sasl2/smtp.conf</i> 142# <i>nano -w /etc/sasl2/smtpd.conf</i>
131pwcheck_method: saslauthd 143pwcheck_method: saslauthd
132mech_list: LOGIN PLAIN 144mech_list: LOGIN PLAIN
133<codenote>It's important to turn off auth mehtods we are not using.</codenote> 145<codenote>It's important to turn off auth methods we are not using.</codenote>
134<codenote>They cause problems for some mail clients.</codenote> 146<codenote>They cause problems for some mail clients.</codenote>
135# <i>/etc/init.d/saslauthd start</i> 147# <i>/etc/init.d/saslauthd start</i>
136</pre> 148</pre>
137</body> 149</body>
150</section>
138</chapter> 151</chapter>
139<chapter> 152<chapter>
140<title>SSL Certs for Postfix and Apache</title> 153<title>SSL Certs for Postfix and Apache</title>
154<section>
141<body> 155<body>
142<p>Next we're going to make a set of ssl certificates for postfix and apache.</p> 156<p>Next we're going to make a set of ssl certificates for postfix and apache.</p>
143<pre> 157<pre>
144# <i>cd /etc/ssl/</i> 158# <i>cd /etc/ssl/</i>
145# <i>nano -w openssl.cnf</i> 159# <i>nano -w openssl.cnf</i>
181# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i> 195# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>
182<codenote>Just leave the resulting certificates here for now.</codenote> 196<codenote>Just leave the resulting certificates here for now.</codenote>
183<codenote>We'll install them after Apache is installed.</codenote> 197<codenote>We'll install them after Apache is installed.</codenote>
184</pre> 198</pre>
185</body> 199</body>
200</section>
186</chapter> 201</chapter>
187<chapter> 202<chapter>
188<title>Adding SSL and SASL support to Postfix</title> 203<title>Adding SSL and SASL support to Postfix</title>
204<section>
189<body> 205<body>
190<p>Now edit the postfix config's to make it aware of your new sasl and ssl capabilities. Add the following parameters to the end of the file where they will be easy to find.</p> 206<p>Now edit the postfix config's to make it aware of your new sasl and ssl capabilities. Add the following parameters to the end of the file where they will be easy to find.</p>
191<pre caption="/etc/postfix/main.cf" > 207<pre caption="/etc/postfix/main.cf" >
192# <i>nano -w /etc/postfix/main.cf</i> 208# <i>nano -w /etc/postfix/main.cf</i>
193 209
248telnet> <i>quit</i> 264telnet> <i>quit</i>
249</pre> 265</pre>
250<p>Verify that the above AUTH and STARTTLS lines now appear in your postfix install. As I said before, as it stands now AUTH will not work. that's because sasl will try to auth against it's sasldb, instead of the shadow file for some unknown reason, which we have not set up. So we're going to just plow through and set up mysql to hold all of our auth and virtual domain information. 266<p>Verify that the above AUTH and STARTTLS lines now appear in your postfix install. As I said before, as it stands now AUTH will not work. that's because sasl will try to auth against it's sasldb, instead of the shadow file for some unknown reason, which we have not set up. So we're going to just plow through and set up mysql to hold all of our auth and virtual domain information.
251 </p> 267 </p>
252</body> 268</body>
269</section>
253</chapter> 270</chapter>
254<chapter> 271<chapter>
255<title>MySQL</title> 272<title>MySQL</title>
273<section>
256<body> 274<body>
257<p>Next we're going to install and configure MySQL. You'll need the <uri link="http://kickasskungfu.com/~ken/genericmailsql.sql" >genericmailsql.sql</uri> dumpfile for this step.</p> 275<p>Next we're going to install and configure MySQL. You'll need the <uri link="http://kickasskungfu.com/~ken/genericmailsql.sql" >genericmailsql.sql</uri> dumpfile for this step.</p>
258<pre caption="Installing and configuring MySQL" > 276<pre caption="Installing and configuring MySQL" >
259# <i>emerge mysql</i> 277# <i>emerge mysql</i>
260 278
309<pre caption="virtual table sample" > 327<pre caption="virtual table sample" >
310id email destination 328id email destination
3113 root@virt-bar.org other@email.address 3293 root@virt-bar.org other@email.address
312</pre> 330</pre>
313</body> 331</body>
332</section>
314</chapter> 333</chapter>
315<chapter> 334<chapter>
316<title>Apache and phpMyAdmin</title> 335<title>Apache and phpMyAdmin</title>
336<section>
317<body> 337<body>
318<p>Next we'll set up apache and add an interface to interact with the database more easily. </p> 338<p>Next we'll set up apache and add an interface to interact with the database more easily. </p>
319<pre caption="Setting up apache and phpmyadmin" > 339<pre caption="Setting up apache and phpmyadmin" >
320# <i>emerge apache mod_php mod_ssl phpmyadmin</i> 340# <i>emerge apache mod_php phpmyadmin</i>
321</pre> 341</pre>
322<p>There are plenty of guides out there about how to set up apache with php. Like this one: <uri>http://www.linuxguruz.org/z.php?id=31</uri>. There are also numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve problems with the installation (search for 'apache php'). So, that said, I'm not going to cover it here. Set up the apache and php installs, then continue with this howto. Now, a word for the wise: .htaccess the directory that you put phpmyadmin in. If you do not do this, search engine spiders will come along and index the page which in turn will mean that anyone will be able to find your phpmyadmin page via google and in turn be able to come change your database however they want which is <e>BAD!</e> There are many howtos on this including: <uri>http://docs.csoft.net/micro/black-htaccess.html</uri>.</p> 342<p>There are plenty of guides out there about how to set up apache with php. Like this one: <uri>http://www.linuxguruz.org/z.php?id=31</uri>. There are also numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve problems with the installation (search for 'apache php'). So, that said, I'm not going to cover it here. Set up the apache and php installs, then continue with this howto. Now, a word for the wise: .htaccess the directory that you put phpmyadmin in. If you do not do this, search engine spiders will come along and index the page which in turn will mean that anyone will be able to find your phpmyadmin page via google and in turn be able to come change your database however they want which is <e>BAD!</e> There are many howtos on this including: <uri>http://www.csoft.net/docs/micro/htaccess.html.en</uri>.</p>
323<p>Now we're going to install the Apache certificates we made previously. The Apache-SSL directives that you need to use the resulting cert are: 343<p>Now we're going to install the Apache certificates we made previously. The Apache-SSL directives that you need to use the resulting cert are:
324 <ul> 344 <ul>
325<li>SSLCertificateFile /path/to/certs/new.cert.cert</li> 345<li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
326<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li> 346<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
327</ul> 347</ul>
340# <i>/etc/init.d/apache restart</i> 360# <i>/etc/init.d/apache restart</i>
341</pre> 361</pre>
342<note>If you have an existing apache install, you'll likely have to perform a full server reboot to install your new certificates. Check your logs to verify apache restarted successfully.</note> 362<note>If you have an existing apache install, you'll likely have to perform a full server reboot to install your new certificates. Check your logs to verify apache restarted successfully.</note>
343<p>Next, configure phpMyAdmin.</p> 363<p>Next, configure phpMyAdmin.</p>
344<pre caption="Configuring phpMyAdmin" > 364<pre caption="Configuring phpMyAdmin" >
345# <i>nano -w /home/httpd/htdocs/phpmyadmin/config.inc.php</i> 365# <i>nano -w /var/www/localhost/htdocs/phpmyadmin/config.inc.php</i>
346<codenote>Change the following parameters</codenote> 366<codenote>Change the following parameters</codenote>
347 367
348$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname 368$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
349$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings 369$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
350 // (this user must have read-only 370 // (this user must have read-only
353$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user 373$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
354$cfg['Servers'][$i]['password'] = '$password'; // MySQL password 374$cfg['Servers'][$i]['password'] = '$password'; // MySQL password
355</pre> 375</pre>
356<p>Now enter the phpmyadmin page and browse the tables. You'll want to add in your local aliases, edit your user table to add a test user, and change your transport table to add information about your domains. The default values supplied with the dumpfile should be a sufficient guide to what values need to go where. Make sure that if you put information in the database that it is accurate. For instance, make sure the local users home dir exists and that the correct uid/gid values are in place. The maildirs should be created automatically by postfix when the user receives their first email. So, in general, it's a good idea to send a &quot;Welcome&quot; mail to a new user after you setup their account to make sure the .maildir gets created. </p> 376<p>Now enter the phpmyadmin page and browse the tables. You'll want to add in your local aliases, edit your user table to add a test user, and change your transport table to add information about your domains. The default values supplied with the dumpfile should be a sufficient guide to what values need to go where. Make sure that if you put information in the database that it is accurate. For instance, make sure the local users home dir exists and that the correct uid/gid values are in place. The maildirs should be created automatically by postfix when the user receives their first email. So, in general, it's a good idea to send a &quot;Welcome&quot; mail to a new user after you setup their account to make sure the .maildir gets created. </p>
357</body> 377</body>
378</section>
358</chapter> 379</chapter>
359<chapter> 380<chapter>
360<title>The vmail user</title> 381<title>The vmail user</title>
382<section>
361<body> 383<body>
362<p>At this point you may be wondering what user and directory to use for virtual mail users, and rightly so. Let's set that up.</p> 384<p>At this point you may be wondering what user and directory to use for virtual mail users, and rightly so. Let's set that up.</p>
363<pre caption="Adding the vmail user" > 385<pre caption="Adding the vmail user" >
364# <i>adduser -d /home/vmail -s /bin/false vmail</i> 386# <i>adduser -d /home/vmail -s /bin/false vmail</i>
365# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i> 387# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i>
367# <i>mkdir /home/vmail</i> 389# <i>mkdir /home/vmail</i>
368# <i>chown vmail. /home/vmail</i> 390# <i>chown vmail. /home/vmail</i>
369</pre> 391</pre>
370<p>So now when you're setting up vmail accounts, use the vmail uid, gid, and homedir. When you're setting up local accounts, use that users uid, gid, and homedir. We've been meaning to create a php admin page for this setup but haven't gotten around to it yet, as phpmyadmin generally works fine for us.</p> 392<p>So now when you're setting up vmail accounts, use the vmail uid, gid, and homedir. When you're setting up local accounts, use that users uid, gid, and homedir. We've been meaning to create a php admin page for this setup but haven't gotten around to it yet, as phpmyadmin generally works fine for us.</p>
371</body> 393</body>
394</section>
372</chapter> 395</chapter>
373<chapter> 396<chapter>
374<title>Configuring MySQL Authentication and vhosts</title> 397<title>Configuring MySQL Authentication and vhosts</title>
398<section>
375<body> 399<body>
376<p>Next we'll reconfigure our authentication to use the mailsql database in courier-imap and postfix. In all of the following examples, replace $password with the password you set for the mailsql mysql user.</p> 400<p>Next we'll reconfigure our authentication to use the mailsql database in courier-imap and postfix. In all of the following examples, replace $password with the password you set for the mailsql mysql user.</p>
377<pre> 401<pre>
378# <i>emerge /usr/portage/sys-libs/pam_mysql/pam_mysql-$currentversion.ebuild</i> 402# <i>emerge pam_mysql</i>
379<codenote>This package is currently masked so you'll have to give it an explicit path </codenote>
380<codenote>or unmask the package. This is subject to change when the package is unmasked</codenote>
381<codenote>in the portage tree.</codenote>
382
383# <i>nano -w /etc/pam.d/imap</i> 403# <i>nano -w /etc/pam.d/imap</i>
384<codenote>Comment out the existing auth lines and add the following as shown.</codenote> 404<codenote>Comment out the existing auth lines and add the following as shown.</codenote>
385 405
386#auth required pam_nologin.so 406#auth required pam_nologin.so
387#auth required pam_stack.so service=system-auth 407#auth required pam_stack.so service=system-auth
388#account required pam_stack.so service=system-auth 408#account required pam_stack.so service=system-auth
389#session required pam_stack.so service=system-auth 409#session required pam_stack.so service=system-auth
390 410
391auth optional pam_mysql.so server=localhost db=mailsql user=mailsql \ 411auth optional pam_mysql.so host=localhost db=mailsql user=mailsql \
392 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 412 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
393account required pam_mysql.so server=localhost db=mailsql user=mailsql \ 413account required pam_mysql.so host=localhost db=mailsql user=mailsql \
394 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 414 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
395 415
396# <i>nano -w /etc/pam.d/pop3</i> 416# <i>nano -w /etc/pam.d/pop3</i>
397# <i>nano -w /etc/pam.d/smtp</i> 417# <i>nano -w /etc/pam.d/smtp</i>
398<codenote>Make the same changes to the pop3 and smtp files</codenote> 418<codenote>Make the same changes to the pop3 and smtp files</codenote>
531virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf 551virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
532virtual_uid_maps = static:$vmail-uid 552virtual_uid_maps = static:$vmail-uid
533virtual_mailbox_base = / 553virtual_mailbox_base = /
534#virtual_mailbox_limit = 554#virtual_mailbox_limit =
535</pre> 555</pre>
556
557<p>
558For security reasons you should change the permissions of the various
559<path>/etc/mail/mysql-*.cf</path>:
560</p>
561
562<pre caption="Changing file permission">
563# <i>chmod 640 /etc/postfix/mysql-*.cf</i>
564# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>
565</pre>
566
536<p>As of Postfix 2.0.x, there were a number of significant changes over the 1.1.x release. Notably the transport, virtual-gid, and virtual-uid tables are no longer necessary. The tables are still included if you wish to use them.</p> 567<p>As of Postfix 2.0.x, there were a number of significant changes over the 1.1.x release. Notably the transport, virtual-gid, and virtual-uid tables are no longer necessary. The tables are still included if you wish to use them.</p>
537<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note> 568<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note>
538<pre># <i>postfix reload</i> 569<pre># <i>postfix reload</i>
539</pre> 570</pre>
540<p>Now, if all went well, you should have a functioning mailhost. Users should be able to authenticate against the sql database, using their full email address, for pop3, imap, and smtp. I would highly suggest that you verify that everything is working at this point. If you run into problems (with as many things as this setup has going on, it's likely that you will) check the troubleshooting section of this howto.</p> 571<p>Now, if all went well, you should have a functioning mailhost. Users should be able to authenticate against the sql database, using their full email address, for pop3, imap, and smtp. I would highly suggest that you verify that everything is working at this point. If you run into problems (with as many things as this setup has going on, it's likely that you will) check the troubleshooting section of this howto.</p>
541</body> 572</body>
573</section>
542</chapter> 574</chapter>
543<chapter> 575<chapter>
544<title>Squirrelmail</title> 576<title>Squirrelmail</title>
577<section>
545<body> 578<body>
546<pre> 579<pre>
547# <i>emerge squirrelmail</i> 580# <i>emerge squirrelmail</i>
548<codenote>I like to add a link to the htdocs space for a shorter url.</codenote> 581<codenote>I like to add a link to the htdocs space for a shorter url.</codenote>
549 582
550# <i>ln -s /home/httpd/htdocs/squirrelmail/ /home/httpd/htdocs/mail</i> 583# <i>ln -s /var/www/localhost/htdocs/squirrelmail/ /var/www/localhost/htdocs/mail</i>
551# <i>cd /home/httpd/htdocs/mail/conf</i> 584# <i>cd /var/www/localhost/htdocs/mail/conf</i>
552# <i>./conf.pl</i> 585# <i>./conf.pl</i>
553<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote> 586<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote>
554<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote> 587<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote>
555<codenote>and use your new webmail setup.</codenote> 588<codenote>and use your new webmail setup.</codenote>
556</pre> 589</pre>
557</body> 590</body>
591</section>
558</chapter> 592</chapter>
559<chapter> 593<chapter>
560<title>Mailman</title> 594<title>Mailman</title>
595<section>
561<body> 596<body>
562<p>Last step: mailman. The new version of mailman has very nice virtual domain support, which is why I use it, not to mention it's really a great package. To get this package installed and working correctly for virtual domains is going to require a bit of hacking. I really recommend reading all of the mailman documentation, including README.POSTFIX.gz, to understand what's being done here.</p> 597<p>Last step: mailman. The new version of mailman has very nice virtual domain support, which is why I use it, not to mention it's really a great package. To get this package installed and working correctly for virtual domains is going to require a bit of hacking. I really recommend reading all of the mailman documentation, including README.POSTFIX.gz, to understand what's being done here.</p>
563<p>One further note, current versions of mailman install to /usr/local/mailman. If you're like me and wish to change the default install location, it can be overridden in the ebuild filoe by changing the INSTALLDIR variable.</p> 598<p>One further note, current versions of mailman install to /usr/local/mailman. If you're like me and wish to change the default install location, it can be overridden in the ebuild filoe by changing the INSTALLDIR variable.</p>
564<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild"> 599<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
565# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i> 600# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i>
644<codenote>using virtual domains, adding the virtual alias maps</codenote> 679<codenote>using virtual domains, adding the virtual alias maps</codenote>
645<codenote>to postfix may cause problems, be warned.</codenote> 680<codenote>to postfix may cause problems, be warned.</codenote>
646</pre> 681</pre>
647<p> You should now be able to setup mailing lists for any domain on your box. Last note on this, make sure you run all mailman commands as the user mailman (<c>su mailman</c>) or else the permissions will be wrong and you'll have to fix them. Read the mailman doc's for more information on setting up and managing mailman lists.</p> 682<p> You should now be able to setup mailing lists for any domain on your box. Last note on this, make sure you run all mailman commands as the user mailman (<c>su mailman</c>) or else the permissions will be wrong and you'll have to fix them. Read the mailman doc's for more information on setting up and managing mailman lists.</p>
648</body> 683</body>
684</section>
649</chapter> 685</chapter>
650<chapter> 686<chapter>
651<title>Content Filtering and Anti-Virus</title> 687<title>Content Filtering and Anti-Virus</title>
688<section>
652<body><p>Coming soon...it would be done already but I need some perl help and testing to make it so. If you'd like to volunteer for that, please email me.</p></body> 689<body><p>Coming soon...it would be done already but I need some perl help and testing to make it so. If you'd like to volunteer for that, please email me.</p></body>
690</section>
653</chapter> 691</chapter>
654<chapter> 692<chapter>
655<title>Wrap Up</title> 693<title>Wrap Up</title>
694<section>
656<body> 695<body>
657<p>Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off verbose mode for production use. You'll probably also want to add the services to your startup routine to make sure everything comes back up on a reboot. Make sure to add all the services you're using - apache, mysql, saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all up to your decision on what access you want to provide. I generally have all the services enabled.</p> 696<p>Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off verbose mode for production use. You'll probably also want to add the services to your startup routine to make sure everything comes back up on a reboot. Make sure to add all the services you're using - apache, mysql, saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all up to your decision on what access you want to provide. I generally have all the services enabled.</p>
658<pre caption="Wrap up" > 697<pre caption="Wrap up" >
659# <i>postfix reload</i> 698# <i>postfix reload</i>
660# <i>rc-update add $service default</i> 699# <i>rc-update add $service default</i>
661</pre> 700</pre>
662<p> 701<p>
663<e>Have fun!</e> 702<e>Have fun!</e>
664</p> 703</p>
665</body> 704</body>
705</section>
666</chapter> 706</chapter>
667<chapter> 707<chapter>
668<title>Troubleshooting</title> 708<title>Troubleshooting</title>
669<section> 709<section>
670<title>Introduction</title> 710<title>Introduction</title>

Legend:
Removed from v.1.16  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20