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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.19 - (show annotations) (download) (as text)
Sat Nov 15 00:35:19 2003 UTC (14 years, 7 months ago) by neysx
Branch: MAIN
Changes since 1.18: +1 -0 lines
File MIME type: application/xml
Added $Header$ cvs tag -- NO CONTENT CHANGE

1 <?xml version = '1.0' encoding = 'UTF-8'?>
2 <!-- $Header$ -->
3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 <guide link=" /doc/en/virt-mail-howto.xml" >
6 <title>Virtual Mailhosting System Guide</title>
7 <author title="Author" >
8 <mail link="antifa@gentoo.org" >Ken Nowack</mail>
9 </author>
10 <author title="Author" >
11 <mail link="ezra@revoltltd.org" >Ezra Gorman</mail>
12 </author>
13 <abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract>
14 <version>1.0.4</version>
15 <date>November 13, 2003</date>
16 <!--
18 Contents
20 I. Introduction
21 II. Postfix Basics
22 III. Courier-imap
23 IV. Cyrus-sasl
24 V. SSL Certificates for Postfix and Apache
25 VI. Adding SSL and SASL support to Postfix
27 VIII. Apache and phpMyAdmin
28 IX. The vmail user
29 X. Configuring MySQL Authentication and vhosts
30 XI. Squirrelmail
31 XII. Mailman
32 XIII. Content Filtering and Anti-Virus
33 XIV. Wrap Up
34 XV. Troubleshooting
36 --><chapter>
37 <title>Introduction</title>
38 <body>
39 <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>
40 <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>
41 <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>
42 <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>
43 <p>The following packages are used in this setup:
45 apache, courier-imap, pam_mysql, postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p>
46 <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>
47 <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>
48 <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>
49 <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>
50 <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>
51 <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>
52 </body>
53 </chapter>
54 <chapter>
55 <title>Postfix Basics</title>
56 <body>
57 <pre caption="Install postfix" ># <i>emerge postfix</i>
58 </pre>
59 <warn>Verify that you have not installed any other MTA, such as ssmtp, exim, or qmail, or you will surely have BIG problems.</warn>
60 <p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p>
61 <pre caption="/etc/postfix/main.cf" >
62 myhostname = $host.domain.name
63 mydomain = $domain.name
64 inet_interfaces = all
65 mydestination = $myhostname, localhost.$mydomain $mydomain
66 mynetworks = my.ip.net.work/24,
67 home_mailbox = .maildir/
68 local_destination_concurrency_limit = 2
69 default_destination_concurrency_limit = 10 </pre>
70 <p>Next change the following in <path>/etc/postfix/master.cf</path>. This will turn on verbose output for debugging:</p>
71 <pre caption="/etc/postfix/master.cf" >
72 # service type private unpriv chroot wakeup maxproc command + args
73 # (yes) (yes) (yes) (never) (50)
74 #
75 ==========================================================================
76 smtp inet n - n - - smtpd -v
78 <codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote>
79 </pre>
80 <p>Next, edit <path>/etc/mail/aliases</path> to add your local aliases. There should at least be an alias for root like: <c>root: your@email.address</c>.</p>
81 <pre caption="Starting postfix for the first time" >
82 # <i>/usr/bin/newaliases</i>
83 <codenote>This will install the new aliases. You only need to do this </codenote>
84 <codenote>when you update or install aliases.</codenote>
86 # <i>/etc/init.d/postfix start</i>
87 </pre>
88 <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>
89 <note>I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto. </note>
90 </body>
91 </chapter>
92 <chapter>
93 <title>Courier-imap</title>
94 <body>
95 <pre caption="Install courier-imap" ># <i>emerge courier-imap</i>
96 </pre>
97 <pre caption="Courier-imap configuration" >
98 # <i>cd /etc/courier-imap</i>
99 <codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote>
100 <codenote>you'll need to create certs for this purpose.</codenote>
101 <codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote>
103 # <i>nano -w pop3d.cnf</i>
104 # <i>nano -w imapd.cnf</i>
105 <codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote>
107 # <i>mkpop3dcert</i>
108 # <i>mkimapdcert</i>
109 </pre>
110 <pre caption="Start the courier services you need." >
111 # <i>/etc/init.d/courier-imapd start</i>
112 # <i>/etc/init.d/courier-imapd-ssl start</i>
113 # <i>/etc/init.d/courier-pop3d start</i>
114 # <i>/etc/init.d/courier-pop3d-ssl start</i>
115 </pre>
116 <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>
117 </body>
118 </chapter>
119 <chapter>
120 <title>Cyrus-sasl</title>
121 <body>
122 <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>
123 <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>
124 <pre caption="Configuring and installing the cyrus-sasl ebuild" >
125 # <i>USE='-ldap -mysql' emerge cyrus-sasl</i>
126 <codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote>
127 <codenote>so we need to turn them off for this build.</codenote>
128 </pre>
129 <p>Next, edit <path>/usr/lib/sasl2/smtp.conf</path>.</p>
130 <pre caption="Starting sasl" >
131 # <i>nano -w /usr/lib/sasl2/smtp.conf</i>
132 pwcheck_method: saslauthd
133 mech_list: LOGIN PLAIN
134 <codenote>It's important to turn off auth mehtods we are not using.</codenote>
135 <codenote>They cause problems for some mail clients.</codenote>
136 # <i>/etc/init.d/saslauthd start</i>
137 </pre>
138 </body>
139 </chapter>
140 <chapter>
141 <title>SSL Certs for Postfix and Apache</title>
142 <body>
143 <p>Next we're going to make a set of ssl certificates for postfix and apache.</p>
144 <pre>
145 # <i>cd /etc/ssl/</i>
146 # <i>nano -w openssl.cnf</i>
148 <codenote>Change the following default values for your domain:</codenote>
149 countryName_default
150 stateOrProvinceName_default
151 localityName_default
152 0.organizationName_default
153 commonName_default
154 emailAddress_default.
156 <codenote>If the variables are not already present, just add them in a sensible place.</codenote>
159 # <i>cd misc</i>
160 # <i>nano -w CA.pl</i>
161 <codenote>We need to add -nodes to the # create a certificate and</codenote>
162 <codenote>#create a certificate request code in order to let our new ssl</codenote>
163 <codenote>certs be loaded without a password. Otherwise when you</codenote>
164 <codenote>reboot your ssl certs will not be available.</codenote>
166 # create a certificate
167 system (&quot;$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS&quot;);
169 # create a certificate request
170 system (&quot;$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS&quot;);
172 # <i>./CA.pl -newca</i>
173 # <i>./CA.pl -newreq</i>
174 # <i>./CA.pl -sign</i>
175 # <i>cp newcert.pem /etc/postfix</i>
176 # <i>cp newreq.pem /etc/postfix</i>
177 # <i>cp demoCA/cacert.pem /etc/postfix</i>
178 <codenote>Now we do the same thing for apache</codenote>
180 # <i>openssl req -new > new.cert.csr</i>
181 # <i>openssl rsa -in privkey.pem -out new.cert.key</i>
182 # <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>
183 <codenote>Just leave the resulting certificates here for now.</codenote>
184 <codenote>We'll install them after Apache is installed.</codenote>
185 </pre>
186 </body>
187 </chapter>
188 <chapter>
189 <title>Adding SSL and SASL support to Postfix</title>
190 <body>
191 <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>
192 <pre caption="/etc/postfix/main.cf" >
193 # <i>nano -w /etc/postfix/main.cf</i>
195 smtpd_sasl_auth_enable = yes
196 smtpd_sasl2_auth_enable = yes
197 smtpd_sasl_security_options = noanonymous
198 broken_sasl_auth_clients = yes
199 smtpd_sasl_local_domain =
201 <codenote>The broken_sasl_auth_clients option and the login auth method </codenote>
202 <codenote>are for outlook and outlook express only and are undocumented.</codenote>
203 <codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote>
204 <codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote>
205 <codenote>smtp-auth. Make sure it's blank or your user names will get</codenote>
206 <codenote>mangled by postfix and be unable to auth.</codenote>
208 smtpd_recipient_restrictions =
209 permit_sasl_authenticated,
210 permit_mynetworks,
211 reject_unauth_destination
214 smtpd_use_tls = yes
215 #smtpd_tls_auth_only = yes
216 smtpd_tls_key_file = /etc/postfix/newreq.pem
217 smtpd_tls_cert_file = /etc/postfix/newcert.pem
218 smtpd_tls_CAfile = /etc/postfix/cacert.pem
219 smtpd_tls_loglevel = 3
220 smtpd_tls_received_header = yes
221 smtpd_tls_session_cache_timeout = 3600s
222 tls_random_source = dev:/dev/urandom
224 <codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote>
225 <codenote>You can turn this on later if you desire.</codenote>
227 # <i>postfix reload</i>
228 </pre>
229 <p>Now we're going to verify that the config's we added were picked up by postfix.</p>
230 <pre caption="Verifying sasl and tls support" >
231 # <i>telnet localhost 25</i>
233 Trying
234 Connected to localhost.
235 Escape character is '^]'.
236 220 mail.domain.com ESMTP Postfix
237 <i>EHLO domain.com</i>
238 250-mail.domain.com
240 250-SIZE 10240000
241 250-VRFY
242 250-ETRN
243 250-STARTTLS
246 250-XVERP
247 250 8BITMIME
248 <i>^]</i>
249 telnet> <i>quit</i>
250 </pre>
251 <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.
252 </p>
253 </body>
254 </chapter>
255 <chapter>
256 <title>MySQL</title>
257 <body>
258 <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>
259 <pre caption="Installing and configuring MySQL" >
260 # <i>emerge mysql</i>
262 # <i>/usr/bin/mysql_install_db</i>
263 <codenote>After this command runs follow the onscreen directions</codenote>
264 <codenote>for adding a root password with mysql,</codenote>
265 <codenote>not mysqladmin, otherwise your db will be wide open.</codenote>
267 # <i>/etc/init.d/mysql start</i>
268 # <i>mysqladmin -u root -p create mailsql</i>
269 # <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>
271 # <i>mysql -u root -p mysql</i>
273 -> <i>ON mailsql.*</i>
274 -> <i>TO mailsql@localhost</i>
275 -> <i>IDENTIFIED BY '$password';</i>
277 -> <i>quit</i>
278 <codenote>Verify that the new mailsql user can connect to the mysql server.</codenote>
280 # <i>mysql -u mailsql -p mailsql</i>
281 </pre>
282 <p>Your new database has default values and tables set up for two domains. The following tables are included:
283 <ul>
284 <li>alias - local email alias and mailman alias information.</li>
285 <li>relocated - relocated user email address maps</li>
286 <li>transport - default mail transport information for all domains you are hosting</li>
287 <li>users - all user account information</li>
288 <li>virtual - virtual domain email alias maps</li>
289 </ul>
290 </p>
291 <pre caption="alias table sample" >
292 id alias destination
293 1 root foo@bar.com
294 2 postmaster foo@bar.com
295 </pre>
296 <pre caption="user table sample" >
297 <codenote>Line wrapped for clarity</codenote>
298 id email clear name uid gid homedir \
299 maildir quota postfix
300 10 foo@virt-bar.org $password realname virtid virtid /home/vmail \
301 /home/vmail/virt-bar.org/foo/.maildir/ y
302 13 foo@bar.com $password realname localid localid /home/foo \
303 /home/foo/.maildir/ y
304 </pre>
305 <pre caption="transport table sample" >
306 id domain destination
307 1 bar.com local:
308 2 virt-bar.org virtual:
309 </pre>
310 <pre caption="virtual table sample" >
311 id email destination
312 3 root@virt-bar.org other@email.address
313 </pre>
314 </body>
315 </chapter>
316 <chapter>
317 <title>Apache and phpMyAdmin</title>
318 <body>
319 <p>Next we'll set up apache and add an interface to interact with the database more easily. </p>
320 <pre caption="Setting up apache and phpmyadmin" >
321 # <i>emerge apache mod_php phpmyadmin</i>
322 </pre>
323 <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>
324 <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:
325 <ul>
326 <li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
327 <li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
328 </ul>
329 </p>
330 <pre caption="Install Apache SSL certificates" >
331 # <i>cp /etc/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i>
332 # <i>cp /etc/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i>
333 # <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i>
334 <codenote>Change the following parameters</codenote>
336 ServerName host.domain.name
337 ServerAdmin your@email.address
338 SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert
339 SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key
341 # <i>/etc/init.d/apache restart</i>
342 </pre>
343 <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>
344 <p>Next, configure phpMyAdmin.</p>
345 <pre caption="Configuring phpMyAdmin" >
346 # <i>nano -w /home/httpd/htdocs/phpmyadmin/config.inc.php</i>
347 <codenote>Change the following parameters</codenote>
349 $cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
350 $cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
351 // (this user must have read-only
352 $cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot;
353 // and &quot;mysql/db&quot; tables)
354 $cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
355 $cfg['Servers'][$i]['password'] = '$password'; // MySQL password
356 </pre>
357 <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>
358 </body>
359 </chapter>
360 <chapter>
361 <title>The vmail user</title>
362 <body>
363 <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>
364 <pre caption="Adding the vmail user" >
365 # <i>adduser -d /home/vmail -s /bin/false vmail</i>
366 # <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i>
367 # <i>groupadd -g $uid vmail</i>
368 # <i>mkdir /home/vmail</i>
369 # <i>chown vmail. /home/vmail</i>
370 </pre>
371 <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>
372 </body>
373 </chapter>
374 <chapter>
375 <title>Configuring MySQL Authentication and vhosts</title>
376 <body>
377 <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>
378 <pre>
379 # <i>emerge /usr/portage/sys-libs/pam_mysql/pam_mysql-$currentversion.ebuild</i>
380 <codenote>This package is currently masked so you'll have to give it an explicit path </codenote>
381 <codenote>or unmask the package. This is subject to change when the package is unmasked</codenote>
382 <codenote>in the portage tree.</codenote>
384 # <i>nano -w /etc/pam.d/imap</i>
385 <codenote>Comment out the existing auth lines and add the following as shown.</codenote>
387 #auth required pam_nologin.so
388 #auth required pam_stack.so service=system-auth
389 #account required pam_stack.so service=system-auth
390 #session required pam_stack.so service=system-auth
392 auth optional pam_mysql.so host=localhost db=mailsql user=mailsql \
393 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
394 account required pam_mysql.so host=localhost db=mailsql user=mailsql \
395 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
397 # <i>nano -w /etc/pam.d/pop3</i>
398 # <i>nano -w /etc/pam.d/smtp</i>
399 <codenote>Make the same changes to the pop3 and smtp files</codenote>
400 </pre>
401 <p>Next, we need to edit courier's authentication config's.</p>
402 <pre>
403 # <i>nano -w /etc/courier-imap/authdaemonrc</i>
404 authmodulelist=&quot;authmysql authpam&quot;
406 # <i>nano -w /etc/courier-imap/authdaemond.conf</i>
407 AUTHDAEMOND=&quot;authdaemond.mysql&quot;
409 # <i>nano -w /etc/courier-imap/authmysqlrc</i>
410 MYSQL_SERVER localhost
411 MYSQL_USERNAME mailsql
412 MYSQL_PASSWORD $password
413 MYSQL_DATABASE mailsql
415 #MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext)
420 MYSQL_HOME_FIELD homedir
424 # <i>/etc/init.d/authdaemond restart</i>
425 # <i>/etc/init.d/saslauthd restart</i>
426 </pre>
427 <p>We're almost there I promise! Next, set up the rest of the necessary config's for postfix to interract with the database for all it's other transport needs.</p>
428 <pre caption="/etc/postfix/mysql-aliases.cf" >
429 # <i>nano -w /etc/postfix/mysql-aliases.cf</i>
430 # mysql-aliases.cf
432 user = mailsql
433 password = $password
434 dbname = mailsql
435 table = alias
436 select_field = destination
437 where_field = alias
438 hosts = unix:/var/run/mysqld/mysqld.sock
439 </pre>
440 <pre caption="/etc/postfix/mysql-relocated.cf" >
441 # <i>nano -w /etc/postfix/mysql-relocated.cf</i>
442 # mysql-relocated.cf
444 user = mailsql
445 password = $password
446 dbname = mailsql
447 table = relocated
448 select_field = destination
449 where_field = email
450 hosts = unix:/var/run/mysqld/mysqld.sock
451 </pre>
452 <pre caption="/etc/postfix/mysql-transport.cf (optional)" >
453 # <i>nano -w /etc/postfix/mysql-transport.cf</i>
454 # mysql-transport.cf
456 user = mailsql
457 password = $password
458 dbname = mailsql
459 table = transport
460 select_field = destination
461 where_field = domain
462 hosts = unix:/var/run/mysqld/mysqld.sock
463 </pre>
464 <pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" >
465 # <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>
466 #myql-virtual-gid.cf
468 user = mailsql
469 password = $password
470 dbname = mailsql
471 table = users
472 select_field = gid
473 where_field = email
474 additional_conditions = and postfix = 'y'
475 hosts = unix:/var/run/mysqld/mysqld.sock
476 </pre>
477 <pre caption="/etc/postfix/mysql-virtual-maps.cf" >
478 # <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>
479 #myql-virtual-maps.cf
481 user = mailsql
482 password = $password
483 dbname = mailsql
484 table = users
485 select_field = maildir
486 where_field = email
487 additional_conditions = and postfix = 'y'
488 hosts = unix:/var/run/mysqld/mysqld.sock
489 </pre>
490 <pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" >
491 # <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>
492 # mysql-virtual-uid.cf
494 user = mailsql
495 password = $password
496 dbname = mailsql
497 table = users
498 select_field = uid
499 where_field = email
500 additional_conditions = and postfix = 'y'
501 hosts = unix:/var/run/mysqld/mysqld.sock
502 </pre>
503 <pre caption="/etc/postfix/mysql-virtual.cf" >
504 # <i>nano -w /etc/postfix/mysql-virtual.cf</i>
505 # mysql-virtual.cf
507 user = mailsql
508 password = $password
509 dbname = mailsql
510 table = virtual
511 select_field = destination
512 where_field = email
513 hosts = unix:/var/run/mysqld/mysqld.sock
514 </pre>
515 <p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p>
516 <pre caption="/etc/postfix/main.cf" >
517 # <i>nano -w /etc/postfix/main.cf</i>
518 alias_maps = mysql:/etc/postfix/mysql-aliases.cf
519 relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
521 local_transport = local
522 local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname
524 virtual_transport = virtual
525 virtual_mailbox_domains =
526 virt-bar.com,
527 $other-virtual-domain.com
529 virtual_minimum_uid = 1000
530 virtual_gid_maps = static:$vmail-gid
531 virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf
532 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
533 virtual_uid_maps = static:$vmail-uid
534 virtual_mailbox_base = /
535 #virtual_mailbox_limit =
536 </pre>
537 <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>
538 <note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note>
539 <pre># <i>postfix reload</i>
540 </pre>
541 <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>
542 </body>
543 </chapter>
544 <chapter>
545 <title>Squirrelmail</title>
546 <body>
547 <pre>
548 # <i>emerge squirrelmail</i>
549 <codenote>I like to add a link to the htdocs space for a shorter url.</codenote>
551 # <i>ln -s /home/httpd/htdocs/squirrelmail/ /home/httpd/htdocs/mail</i>
552 # <i>cd /home/httpd/htdocs/mail/conf</i>
553 # <i>./conf.pl</i>
554 <codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote>
555 <codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote>
556 <codenote>and use your new webmail setup.</codenote>
557 </pre>
558 </body>
559 </chapter>
560 <chapter>
561 <title>Mailman</title>
562 <body>
563 <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>
564 <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>
565 <pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
566 # <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i>
567 MAILGID="280"
568 <codenote>Set MAILGID to the mailman group instead of nobody</codenote>
569 <codenote>This is needed for postfix integration</codenote>
570 </pre>
571 <pre>
572 # <i>emerge mailman</i>
573 <codenote>This package is currently masked as well, so you'll need to unmask it or give </codenote>
574 <codenote>emerge an explicit path to the ebuild. Once it's installed, follow the directions</codenote>
575 <codenote>in the README.gentoo.gz *except* do not add your aliases to /etc/mail/aliases.</codenote>
576 <codenote>We will instead be linking the entire alias db into postfix.</codenote>
578 # <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i>
579 </pre>
580 <pre caption="Setting defaults: Mailman/Defaults.py">
581 # <i> nano -w /var/mailman/Mailman/Defaults.py</i>
582 <codenote>Change the values below to reflect your primary domain, virtuals will be set next.</codenote>
583 DEFAULT_EMAIL_HOST = 'domain.com'
584 DEFAULT_URL_HOST = 'www.domain.com'
585 </pre>
586 <pre caption="mailman config: mm_cfg.py">
587 # <i>nano -w /var/mailman/Mailman/mm_cfg.py</i>
588 MTA = "Postfix"
589 POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']
590 add_virtualhost('www.virt.domain.com', 'virt.domain.com')
591 add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')
592 <codenote>This is required for your virtual domains for mailman to function.</codenote>
593 </pre>
594 <pre>
595 <codenote>Once that's finished, add your first list.</codenote>
597 # <i>su mailman</i>
598 # <i>cd ~</i>
599 # <i>bin/newlist test</i>
600 Enter the email of the person running the list: your@email.address
601 Initial test password:
602 Hit enter to continue with test owner notification...
603 <codenote>Virtual domain lists may be specified with</codenote>
604 <codenote>list@domain.com style list names</codenote>
605 # <i>bin/genaliases</i>
606 <codenote>Now that your aliases have been generated,</codenote>
607 <codenote>verify that they were added successfully.</codenote>
609 # <i>nano -w data/aliases</i>
610 # STANZA START: test
611 # CREATED:
612 test: "|/var/mailman/mail/mailman post test"
613 test-admin: "|/var/mailman/mail/mailman admin test"
614 test-bounces: "|/var/mailman/mail/mailman bounces test"
615 test-confirm: "|/var/mailman/mail/mailman confirm test"
616 test-join: "|/var/mailman/mail/mailman join test"
617 test-leave: "|/var/mailman/mail/mailman leave test"
618 test-owner: "|/var/mailman/mail/mailman owner test"
619 test-request: "|/var/mailman/mail/mailman request test"
620 test-subscribe: "|/var/mailman/mail/mailman subscribe test"
621 test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test"
622 # STANZA END: test
624 # <i>/etc/init.d/mailman start</i>
625 # <i>rc-update add mailman default</i>
626 <codenote>To start mailman at once and on every reboot</codenote>
627 </pre>
629 <pre caption="Adding mailman alias support to postfix">
630 # <i>nano -w /etc/postfix/main.cf</i>
631 owner_request_special = no
632 recipient_delimiter = +
633 <codenote>Read README.POSTFIX.gz for details on this</codenote>
635 alias_maps =
636 hash:/var/mailman/data/aliases,
637 mysql:/etc/postfix/mysql-aliases.cf
639 virtual_alias_maps =
640 hash:/var/mailman/data/virtual-mailman,
641 mysql:/etc/postfix/mysql-virtual.cf
642 <codenote>This adds mailman alias file support to postfix</codenote>
643 <codenote>You may of course use the mysql tables for this,</codenote>
644 <codenote>but I hate doing that by hand. Also, if you are not</codenote>
645 <codenote>using virtual domains, adding the virtual alias maps</codenote>
646 <codenote>to postfix may cause problems, be warned.</codenote>
647 </pre>
648 <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>
649 </body>
650 </chapter>
651 <chapter>
652 <title>Content Filtering and Anti-Virus</title>
653 <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>
654 </chapter>
655 <chapter>
656 <title>Wrap Up</title>
657 <body>
658 <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>
659 <pre caption="Wrap up" >
660 # <i>postfix reload</i>
661 # <i>rc-update add $service default</i>
662 </pre>
663 <p>
664 <e>Have fun!</e>
665 </p>
666 </body>
667 </chapter>
668 <chapter>
669 <title>Troubleshooting</title>
670 <section>
671 <title>Introduction</title>
672 <body>
673 <p>Troubleshooting: This is a short troubleshooting guide for the set up we've detailed how to install here. It is not exhaustive, but meant as a place to get you started in figuring out problems. With a complicated setup such as this, it's imperative that you narrow down the problem to the particular component that is malfunctioning. In general I do that by following a few steps. Start from the base of the system and work your way up, ruling out components that work along the way until you discover which component is having the problem.</p>
674 </body>
675 </section>
676 <section>
677 <title>Step 1: Check your config files.</title>
678 <body>
679 <p>Typos are killers, especially when dealing with authentication systems. Scan your config's and mailsql database for typo's. You can debug all you want, but if you're not passing the right information back and forth to your mail system, it's not going to work. If you make a change to a config file for a service, make sure you restart that service so that the config change gets picked up.</p>
680 <pre>
681 # <i>/etc/init.d/service restart</i>
682 </pre>
683 </body>
684 </section>
685 <section>
686 <title>Step 2: Are all the necessary services actually running?</title>
687 <body>
688 <p>If it's not running, start it up. It's awful hard to debug a service that isn't running. Sometimes a service will act like it's started but still not function. Sometimes, when a bad config is used, or a bad transmission comes into a mail component, the service will hang and keep the port from being used by another process. Sometimes you can detect this with netstat. Or, if you've been at it awhile, just take a break and reboot your box in the meantime. That will clear out any hung services. Then you can come back fresh and try it again.</p>
689 <pre>
690 # <i>/etc/init.d/$service status</i>
691 # <i>netstat -a | grep $service (or $port)</i>
692 </pre>
693 </body>
694 </section>
695 <section>
696 <title>Step 3: Are all the service using the current config's?</title>
697 <body>
698 <p>If you've recently made a change to a config file, restart that service to make sure it's using the current version. Some of the components will dump their current config's to you, like postfix.</p>
699 <pre>
700 # <i>apachectl fullstatus</i> (needs lynx installed)
701 # <i>apachectl configtest</i> (checks config sanity)
702 # <i>postconf -n</i> (will tell you exactly what param's postfix is using)
703 # <i>/etc/init.d/$service restart</i>
704 </pre>
705 </body>
706 </section>
707 <section>
708 <title>Step 4: Check the logs.</title>
709 <body>
710 <p>Repeat after me, logs are my friend. My next troubleshooting stop is always the logs. Sometimes it's helpful to try a failed operation again then check the logs so that the error message is right at the bottom (or top depending on your logger) instead of buried in there somewhere. See if there is any information in your log that can help you diagnose the problem, or at the very least, figure out which component is having the problem.</p>
711 <pre>
712 # <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)
713 # <i>nano -w /var/log/mail/current</i>
714 # <i>cat /var/log/mysql/mysql.log</i>
715 # <i>tail /var/log/apache/error_log</i>
716 </pre>
717 <p>You may also find the debug_peer parameters in main.cf helpful. Setting these will increase log output over just verbose mode.</p>
718 <pre caption="adding debug_peer support">
719 # <i>nano -w /etc/postfix/main.cf</i>
720 debug_peer_level = 5
721 debug_peer_list = $host.domain.name
722 <codenote>Uncomment one of the suggested debugger</codenote>
723 <codenote>commands as well.</codenote>
724 </pre>
725 </body>
726 </section>
727 <section>
728 <title>Step 5: Talk to the service itself.</title>
729 <body>
730 <p>SMTP, IMAP, and POP3 all respond to telnet sessions. As we've seen earlier when we verified postfix's config. Sometimes it's helpful to open a telnet session to the service itself and see what's happening.</p>
731 <pre>
732 # <i>telnet localhost $port</i>
733 <codenote>SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,</codenote>
734 <codenote>letting you know that the service is running and ready to respond to requests.</codenote>
736 Trying
737 Connected to localhost.
738 Escape character is '^]'.
739 * OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.
740 </pre>
741 </body>
742 </section>
743 <section>
744 <title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title>
745 <body>
746 <p>You should have this installed anyway. This is an invaluable tool for debugging software. You can start commands from the command line with strace and watch all the system calls as they happen. It often dumps a huge amount of information, so you'll either need to watch it realtime as you retry a failed transaction with the mail system, or dump the output to a file for review.</p>
747 <pre>
748 # <i>emerge strace</i>
749 # <i>strace $command</i>
750 # <i>strace -p `ps -C $service -o pid=`</i>
751 </pre>
752 </body>
753 </section>
754 <section>
755 <title>Step 7: Research</title>
756 <body>
757 <p>Once you have the information, if you can diagnose and fix the problem, great! If not, you'll probably need to go digging on the net for information that will help you fix it. Here's a list of sites you can check to see if your error has already been resolved. There's also a really good howto on setting up smtp-auth which contains some great debugging ideas.</p>
758 <p>
759 <ul>
760 <li>
761 <uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users</li>
762 <li>
763 <uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place to look for specific errors</li>
764 <li>
765 <uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto</li>
766 <li>
767 <uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing lists - searchable</li>
768 <li>
769 <uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - Courier-imap mailing list archives - not searchable</li>
770 <li>
771 <uri>http://www.google.com/</uri> - If all else fails, there's always google, which has never failed me</li>
772 <li>I also spend a lot of time on irc.freenode.net #gentoo. Irc is a great place to go for help.</li>
773 </ul>
774 </p>
775 </body>
776 </section>
777 </chapter>
778 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20