/[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.28 Revision 1.42
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<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/virt-mail-howto.xml,v 1.42 2005/03/25 14:39:17 neysx Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link=" /doc/en/virt-mail-howto.xml" > 5<guide link="/doc/en/virt-mail-howto.xml">
6<title>Virtual Mailhosting System with Postfix Guide</title> 6<title>Virtual Mailhosting System with Postfix Guide</title>
7
7<author title="Author" > 8<author title="Author">
8<mail link="antifa@gentoo.org" >Ken Nowack</mail> 9 <mail link="antifa@gentoo.org">Ken Nowack</mail>
9</author> 10</author>
10<author title="Author" > 11<author title="Author">
11<mail link="ezra@revoltltd.org" >Ezra Gorman</mail> 12 <mail link="ezra@revoltltd.org">Ezra Gorman</mail>
12</author> 13</author>
13<author title="Editor"> 14<author title="Editor">
14<mail link="klasikahl@gentoo.org" >Zack Gilburd</mail> 15 <mail link="klasikahl@gentoo.org">Zack Gilburd</mail>
15</author> 16</author>
16<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract> 17
18<abstract>
19This document details how to create a virtual mailhosting system based upon
20postfix, mysql, courier-imap, and cyrus-sasl.
21</abstract>
22
17<version>1.0.10</version> 23<version>1.0.19</version>
18<date>March 4, 2004</date> 24<date>2005-03-25</date>
25
19<!-- 26<!--
20
21Contents 27Contents
22 28
23I. Introduction 29I. Introduction
24II. Postfix Basics 30II. Postfix Basics
25III. Courier-imap 31III. Courier-imap
33XI. Squirrelmail 39XI. Squirrelmail
34XII. Mailman 40XII. Mailman
35XIII. Content Filtering and Anti-Virus 41XIII. Content Filtering and Anti-Virus
36XIV. Wrap Up 42XIV. Wrap Up
37XV. Troubleshooting 43XV. Troubleshooting
44-->
38 45
39--><chapter> 46<chapter>
40<title>Introduction</title> 47<title>Introduction</title>
41<section> 48<section>
42<body> 49<body>
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> 50
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> 51<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> 52For most gentoo users, a simple mail client and fetchmail will do. However, if
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> 53you're hosting a domain with your system, you'll need a full blown MTA (Mail
47<p>The following packages are used in this setup: 54Transfer Agent). And if you're hosting multiple domains, then you'll definitely
48 55need something more robust to handle all of the email for your users. This
49 apache, courier-imap, pam_mysql, postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p> 56system was designed to be an elegant solution to that problem.
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> 57</p>
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> 58
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> 59<p>
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> 60A virtual mail system needs to be able to handle email for numerous domains
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> 61with multiple users over a variety of interfaces. This presents some issues
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> 62that must be dealt with. For instance, what if you have two users on different
63domains that want the same user name? If you are providing imap access and
64smtp-auth, how do combine the various authentication daemons into a single
65system? How do you provide security for the numerous components that comprise
66the system? How do you manage it all?
67</p>
68
69<p>
70This howto will show you how to set up with a mail system capable of handling
71mail for as many domains as your hardware can handle, supports virtual mail
72users that don't require shell accounts, has domain specific user names, can
73authenticate web, imap, smtp, and pop3 clients against a single database,
74utilizes ssl for transport layer security, has a web interface, can handle
75mailing lists for any domain on the machine, and is controlled by a nice,
76central and easy mysql database.
77</p>
78
79<p>
80There are quite a variety of ways to go about setting up a virtual mailhosting
81system. With so may options, another may be the best choice for your specific
82needs. Consider investigating <uri>http://www.qmail.org/</uri> and
83<uri>http://www.exim.org/</uri> to explore your options.
84</p>
85
86<p>
87The following packages are used in this setup: apache, courier-imap, pam_mysql,
88postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and
89mailman.
90</p>
91
92<p>
93Make sure to turn on the following USE variables in <path>/etc/make.conf</path>
94before compiling the packages: <c>USE="mysql pam-mysql imap libwww maildir
95sasl ssl"</c>. Otherwise you will most likely have to recompile things to
96get the support you need for all the protocols. Further, it's a good idea to
97turn off any other mail and network variables, like ipv6.
98</p>
99
100<impo>
101This howto was written for postfix-2.0.x. If you are using postfix &lt; 2 some
102of the variables in this document will be different. It is recommended that you
103upgrade. Some other packages included in this howto are version sensitive as
104well. You are advised to read the documentation included with packages if you
105run into issues with this.
106</impo>
107
108<impo>
109This document uses apache-1.3.x. Apache-2 has been marked stable in portage.
110However there are still a number of issues with php integration. Until php
111support in apache-2.0.x is marked stable, this guide will continue to use the
1121.3.x version.
113</impo>
114
115<impo>
116You need a domain name to run a public mail server, or at least an MX record
117for a domain. Ideally you would have control of at least two domains to take
118advantage of your new virtual domain functionality.
119</impo>
120
121<impo>
122Make sure <path>/etc/hostname</path> is set to the right hostname for your mail
123server. Verify your hostname is set correctly with <c>hostname</c>. Also
124verify that there are no conflicting entries in <path>/etc/hosts</path>.
125</impo>
126
127<note>
128It is recommended that you read this entire document and familiarize yourself
129with all the steps before attempting the install. If you run into problems with
130any of the steps, check the troubleshooting guide at the end of this document.
131Also, not all the referenced packages are necessary, this set up is very
132flexible. For instance, if you do not desire a web interface, feel free to skip
133the squirrelmail section.
134</note>
135
56</body> 136</body>
57</section> 137</section>
58</chapter> 138</chapter>
59 139
60<chapter> 140<chapter>
61<title>Postfix Basics</title> 141<title>Postfix Basics</title>
62<section> 142<section>
63<body> 143<body>
64<pre caption="Install postfix" ># <i>emerge postfix</i> 144
145<pre caption="Install postfix">
146# <i>emerge postfix</i>
147</pre>
148
149<warn>
150Verify that you have not installed any other MTA, such as ssmtp, exim, or
151qmail, or you will surely have BIG problems.
152</warn>
153
154<p>
155After postfix is installed, it's time to configure it. Change the following
156options in <path>/etc/postfix/main.cf</path>:
65</pre> 157</p>
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> 158
67<p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p>
68<pre caption="/etc/postfix/main.cf" > 159<pre caption="/etc/postfix/main.cf">
69myhostname = $host.domain.name 160myhostname = $host.domain.name
70mydomain = $domain.name 161mydomain = $domain.name
71inet_interfaces = all 162inet_interfaces = all
72mydestination = $myhostname, localhost.$mydomain $mydomain 163mydestination = $myhostname, localhost.$mydomain $mydomain
73mynetworks = my.ip.net.work/24, 127.0.0.0/8 164mynetworks = my.ip.net.work/24, 127.0.0.0/8
74home_mailbox = .maildir/ 165home_mailbox = .maildir/
75local_destination_concurrency_limit = 2 166local_destination_concurrency_limit = 2
76default_destination_concurrency_limit = 10 </pre> 167default_destination_concurrency_limit = 10
168</pre>
169
170<p>
77<p>Next change the following in <path>/etc/postfix/master.cf</path>. This will turn on verbose output for debugging:</p> 171Next change the following in <path>/etc/postfix/master.cf</path>. This will
172turn on verbose output for debugging:
173</p>
174
78<pre caption="/etc/postfix/master.cf" > 175<pre caption="/etc/postfix/master.cf">
79# service type private unpriv chroot wakeup maxproc command + args 176# service type private unpriv chroot wakeup maxproc command + args
80# (yes) (yes) (yes) (never) (50) 177# (yes) (yes) (yes) (never) (50)
81# 178#
82========================================================================== 179==========================================================================
180<comment>(Just add the "-v" after the smtpd in the following line)</comment>
83smtp inet n - n - - smtpd -v 181smtp inet n - n - - smtpd -v
182</pre>
84 183
85<codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote> 184<p>
185Next, edit <path>/etc/mail/aliases</path> to add your local aliases. There
186should at least be an alias for root like: <c>root: your@email.address</c>.
86</pre> 187</p>
87<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> 188
88<pre caption="Starting postfix for the first time" > 189<pre caption="Starting postfix for the first time">
89# <i>/usr/bin/newaliases</i> 190# <i>/usr/bin/newaliases</i>
90<codenote>This will install the new aliases. You only need to do this </codenote> 191<comment>(This will install the new aliases. You only need to do this
91<codenote>when you update or install aliases.</codenote> 192when you update or install aliases.)</comment>
92 193
93# <i>/etc/init.d/postfix start</i> 194# <i>/etc/init.d/postfix start</i>
94</pre> 195</pre>
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> 196
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> 197<p>
198Now that postfix is running, fire up your favorite console mail client and send
199yourself an email. I use <c>mutt</c> for all my console mail. Verify that
200postfix is delivering mail to local users, once that's done, we're on to the
201next step.
202</p>
203
204<note>
205I strongly recommend that you verify this basic postfix setup is functioning
206before you progress to the next step of the howto.
207</note>
208
97</body> 209</body>
98</section> 210</section>
99</chapter> 211</chapter>
212
100<chapter> 213<chapter>
101<title>Courier-imap</title> 214<title>Courier-imap</title>
102<section> 215<section>
103<body> 216<body>
104<pre caption="Install courier-imap" ># <i>emerge courier-imap</i> 217
218<pre caption="Install courier-imap">
219# <i>emerge courier-imap</i>
105</pre> 220</pre>
221
106<pre caption="Courier-imap configuration" > 222<pre caption="Courier-imap configuration">
107# <i>cd /etc/courier-imap</i> 223# <i>cd /etc/courier-imap</i>
108<codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote> 224<comment>(If you want to use the ssl capabilities of courier-imap or pop3,
109<codenote>you'll need to create certs for this purpose.</codenote> 225you'll need to create certs for this purpose.
110<codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote> 226This step is recommended. If you do not want to use ssl, skip this step.)</comment>
111 227
112# <i>nano -w pop3d.cnf</i> 228# <i>nano -w pop3d.cnf</i>
113# <i>nano -w imapd.cnf</i> 229# <i>nano -w imapd.cnf</i>
114<codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote> 230<comment>(Change the C, ST, L, CN, and email parameters to match your server.)</comment>
115 231
116# <i>mkpop3dcert</i> 232# <i>mkpop3dcert</i>
117# <i>mkimapdcert</i> 233# <i>mkimapdcert</i>
118</pre> 234</pre>
235
119<pre caption="Start the courier services you need." > 236<pre caption="Start the courier services you need.">
120# <i>/etc/init.d/courier-imapd start</i> 237# <i>/etc/init.d/courier-imapd start</i>
121# <i>/etc/init.d/courier-imapd-ssl start</i> 238# <i>/etc/init.d/courier-imapd-ssl start</i>
122# <i>/etc/init.d/courier-pop3d start</i> 239# <i>/etc/init.d/courier-pop3d start</i>
123# <i>/etc/init.d/courier-pop3d-ssl start</i> 240# <i>/etc/init.d/courier-pop3d-ssl start</i>
124</pre> 241</pre>
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> 242
243<p>
244Start up your favorite mail client and verify that all connections you've
245started work for receiving and sending mail. Now that the basics work, we're
246going to do a whole bunch of stuff at once to get the rest of the system
247running. Again, please verify that what we've installed already works before
248progressing.
249</p>
250
126</body> 251</body>
127</section> 252</section>
128</chapter> 253</chapter>
254
129<chapter> 255<chapter>
130<title>Cyrus-sasl</title> 256<title>Cyrus-sasl</title>
131<section> 257<section>
132<body> 258<body>
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> 259
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> 260<p>
261Next we're going to install cyrus-sasl. Sasl is going to play the role of
262actually passing your auth variables to pam, which will in turn pass that
263information to mysql for authentication of smtp users. For this howto, we'll
264not even try to verify that sasl is working until mysql is set up and contains
265a test user. Which is fine since we'll be authenticating against mysql in the
266end anyway.
267</p>
268
135<pre caption="Configuring and installing the cyrus-sasl ebuild" > 269<pre caption="Configuring and installing the cyrus-sasl ebuild">
136# <i>USE='-ldap -mysql' emerge cyrus-sasl</i> 270# <i>emerge cyrus-sasl</i>
137<codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote>
138<codenote>so we need to turn them off for this build.</codenote>
139</pre> 271</pre>
272
273<p>
140<p>Next, edit <path>/etc/sasl2/smtpd.conf</path>.</p> 274Next, edit <path>/etc/sasl2/smtpd.conf</path>.
275</p>
276
141<pre caption="Starting sasl" > 277<pre caption="Starting sasl">
142# <i>nano -w /etc/sasl2/smtpd.conf</i> 278# <i>nano -w /etc/sasl2/smtpd.conf</i>
279mech_list: PLAIN LOGIN
143pwcheck_method: saslauthd 280pwcheck_method: saslauthd
144mech_list: LOGIN PLAIN 281# <i>nano -w /etc/conf.d/saslauthd</i>
145<codenote>It's important to turn off auth methods we are not using.</codenote> 282SASLAUTHD_OPTS="${SASLAUTH_MECH} -a pam -r"
146<codenote>They cause problems for some mail clients.</codenote>
147# <i>/etc/init.d/saslauthd start</i> 283# <i>/etc/init.d/saslauthd start</i>
148</pre> 284</pre>
285
149</body> 286</body>
150</section> 287</section>
151</chapter> 288</chapter>
289
152<chapter> 290<chapter>
153<title>SSL Certs for Postfix and Apache</title> 291<title>SSL Certs for Postfix and Apache</title>
154<section> 292<section>
155<body> 293<body>
294
295<p>
156<p>Next we're going to make a set of ssl certificates for postfix and apache.</p> 296Next we're going to make a set of ssl certificates for postfix and apache.
157<pre> 297</p>
298
299<pre caption="Making ssl certicates">
158# <i>cd /etc/ssl/</i> 300# <i>cd /etc/ssl/</i>
159# <i>nano -w openssl.cnf</i> 301# <i>nano -w openssl.cnf</i>
160 302
161<codenote>Change the following default values for your domain:</codenote> 303<comment>Change the following default values for your domain:</comment>
162countryName_default 304countryName_default
163stateOrProvinceName_default 305stateOrProvinceName_default
164localityName_default 306localityName_default
1650.organizationName_default 3070.organizationName_default
166commonName_default 308commonName_default
167emailAddress_default. 309emailAddress_default.
168 310
169<codenote>If the variables are not already present, just add them in a sensible place.</codenote> 311<comment>(If the variables are not already present, just add them in a sensible place.)</comment>
170
171 312
172# <i>cd misc</i> 313# <i>cd misc</i>
173# <i>nano -w CA.pl</i> 314# <i>nano -w CA.pl</i>
174<codenote>We need to add -nodes to the # create a certificate and</codenote> 315<comment>(We need to add -nodes to the # create a certificate and
175<codenote>#create a certificate request code in order to let our new ssl</codenote> 316#create a certificate request code in order to let our new ssl
176<codenote>certs be loaded without a password. Otherwise when you</codenote> 317certs be loaded without a password. Otherwise when you
177<codenote>reboot your ssl certs will not be available.</codenote> 318reboot your ssl certs will not be available.)</comment>
178 319
179# create a certificate 320# create a certificate
180system (&quot;$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS&quot;); 321system ("$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS");
181 322
182# create a certificate request 323# create a certificate request
183system (&quot;$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS&quot;); 324system ("$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS");
184 325
185# <i>./CA.pl -newca</i> 326# <i>./CA.pl -newca</i>
186# <i>./CA.pl -newreq</i> 327# <i>./CA.pl -newreq</i>
187# <i>./CA.pl -sign</i> 328# <i>./CA.pl -sign</i>
188# <i>cp newcert.pem /etc/postfix</i> 329# <i>cp newcert.pem /etc/postfix</i>
189# <i>cp newreq.pem /etc/postfix</i> 330# <i>cp newreq.pem /etc/postfix</i>
190# <i>cp demoCA/cacert.pem /etc/postfix</i> 331# <i>cp demoCA/cacert.pem /etc/postfix</i>
191<codenote>Now we do the same thing for apache</codenote> 332<comment>(Now we do the same thing for apache.)</comment>
192 333
193# <i>openssl req -new > new.cert.csr</i> 334# <i>openssl req -new > new.cert.csr</i>
194# <i>openssl rsa -in privkey.pem -out new.cert.key</i> 335# <i>openssl rsa -in privkey.pem -out new.cert.key</i>
195# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i> 336# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>
196<codenote>Just leave the resulting certificates here for now.</codenote> 337<comment>(Just leave the resulting certificates here for now.
197<codenote>We'll install them after Apache is installed.</codenote> 338We'll install them after Apache is installed.)</comment>
198</pre> 339</pre>
340
199</body> 341</body>
200</section> 342</section>
343
201</chapter> 344</chapter>
202<chapter> 345<chapter>
203<title>Adding SSL and SASL support to Postfix</title> 346<title>Adding SSL and SASL support to Postfix</title>
204<section> 347<section>
205<body> 348<body>
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> 349
350<p>
351Now edit the postfix config's to make it aware of your new sasl and ssl
352capabilities. Add the following parameters to the end of the file where they
353will be easy to find.
354</p>
355
207<pre caption="/etc/postfix/main.cf" > 356<pre caption="/etc/postfix/main.cf">
208# <i>nano -w /etc/postfix/main.cf</i> 357# <i>nano -w /etc/postfix/main.cf</i>
209 358
210smtpd_sasl_auth_enable = yes 359smtpd_sasl_auth_enable = yes
211smtpd_sasl2_auth_enable = yes 360smtpd_sasl2_auth_enable = yes
212smtpd_sasl_security_options = noanonymous 361smtpd_sasl_security_options = noanonymous
213broken_sasl_auth_clients = yes 362broken_sasl_auth_clients = yes
214smtpd_sasl_local_domain = 363smtpd_sasl_local_domain =
215 364
216<codenote>The broken_sasl_auth_clients option and the login auth method </codenote> 365<comment>(The broken_sasl_auth_clients option and the login auth method
217<codenote>are for outlook and outlook express only and are undocumented.</codenote> 366are for outlook and outlook express only and are undocumented.
218<codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote> 367Isn't having to hack software for stupid, broken, M$ BS great?
219<codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote> 368smtpd_sasl_local_domain appends a domain name to clients using
220<codenote>smtp-auth. Make sure it's blank or your user names will get</codenote> 369smtp-auth. Make sure it's blank or your user names will get
221<codenote>mangled by postfix and be unable to auth.</codenote> 370mangled by postfix and be unable to auth.)</comment>
222 371
223smtpd_recipient_restrictions = 372smtpd_recipient_restrictions =
224 permit_sasl_authenticated, 373 permit_sasl_authenticated,
225 permit_mynetworks, 374 permit_mynetworks,
226 reject_unauth_destination 375 reject_unauth_destination
234smtpd_tls_loglevel = 3 383smtpd_tls_loglevel = 3
235smtpd_tls_received_header = yes 384smtpd_tls_received_header = yes
236smtpd_tls_session_cache_timeout = 3600s 385smtpd_tls_session_cache_timeout = 3600s
237tls_random_source = dev:/dev/urandom 386tls_random_source = dev:/dev/urandom
238 387
239<codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote> 388<comment>(smtpd_tls_auth_only is commented out to ease testing the system.
240<codenote>You can turn this on later if you desire.</codenote> 389You can turn this on later if you desire.)</comment>
241 390
242# <i>postfix reload</i> 391# <i>postfix reload</i>
243</pre> 392</pre>
393
394<p>
244<p>Now we're going to verify that the config's we added were picked up by postfix.</p> 395Now we're going to verify that the config's we added were picked up by postfix.
396</p>
397
245<pre caption="Verifying sasl and tls support" > 398<pre caption="Verifying sasl and tls support">
246# <i>telnet localhost 25</i> 399# <i>telnet localhost 25</i>
247 400
248Trying 127.0.0.1... 401Trying 127.0.0.1...
249Connected to localhost. 402Connected to localhost.
250Escape character is '^]'. 403Escape character is '^]'.
261250-XVERP 414250-XVERP
262250 8BITMIME 415250 8BITMIME
263<i>^]</i> 416<i>^]</i>
264telnet> <i>quit</i> 417telnet> <i>quit</i>
265</pre> 418</pre>
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. 419
420<p>
421Verify that the above AUTH and STARTTLS lines now appear in your postfix
422install. As I said before, as it stands now AUTH will not work. that's because
423sasl will try to auth against it's sasldb, instead of the shadow file for some
424unknown reason, which we have not set up. So we're going to just plow through
425and set up mysql to hold all of our auth and virtual domain information.
267 </p> 426</p>
427
268</body> 428</body>
269</section> 429</section>
270</chapter> 430</chapter>
431
271<chapter> 432<chapter>
272<title>MySQL</title> 433<title>MySQL</title>
273<section> 434<section>
274<body> 435<body>
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> 436
437<p>
438Next we're going to install and configure MySQL. You'll need the <uri
439link="http://www.gentoo.org/doc/en/files/genericmailsql.sql">genericmailsql.sql</uri>
440dumpfile for this step.
441</p>
442
276<pre caption="Installing and configuring MySQL" > 443<pre caption="Installing and configuring MySQL">
277# <i>emerge mysql</i> 444# <i>emerge mysql</i>
278 445
279# <i>/usr/bin/mysql_install_db</i> 446# <i>/usr/bin/mysql_install_db</i>
280<codenote>After this command runs follow the onscreen directions</codenote> 447<comment>(After this command runs follow the onscreen directions
281<codenote>for adding a root password with mysql,</codenote> 448for adding a root password with mysql,
282<codenote>not mysqladmin, otherwise your db will be wide open.</codenote> 449not mysqladmin, otherwise your db will be wide open.)</comment>
283 450
284# <i>/etc/init.d/mysql start</i> 451# <i>/etc/init.d/mysql start</i>
285# <i>mysqladmin -u root -p create mailsql</i> 452# <i>mysqladmin -u root -p create mailsql</i>
286# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i> 453# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>
287 454
290 -> <i>ON mailsql.*</i> 457 -> <i>ON mailsql.*</i>
291 -> <i>TO mailsql@localhost</i> 458 -> <i>TO mailsql@localhost</i>
292 -> <i>IDENTIFIED BY '$password';</i> 459 -> <i>IDENTIFIED BY '$password';</i>
293 460
294 -> <i>quit</i> 461 -> <i>quit</i>
295<codenote>Verify that the new mailsql user can connect to the mysql server.</codenote> 462<comment>(Verify that the new mailsql user can connect to the mysql server.)</comment>
296 463
297# <i>mysql -u mailsql -p mailsql</i> 464# <i>mysql -u mailsql -p mailsql</i>
298</pre> 465</pre>
466
467<p>
299<p>Your new database has default values and tables set up for two domains. The following tables are included: 468Your new database has default values and tables set up for two domains. The
469following tables are included:
470</p>
471
300 <ul> 472<ul>
301<li>alias - local email alias and mailman alias information.</li> 473 <li>alias - local email alias and mailman alias information.</li>
302<li>relocated - relocated user email address maps</li> 474 <li>relocated - relocated user email address maps</li>
475 <li>
303<li>transport - default mail transport information for all domains you are hosting</li> 476 transport - default mail transport information for all domains you are
477 hosting
478 </li>
304<li>users - all user account information</li> 479 <li>users - all user account information</li>
305<li>virtual - virtual domain email alias maps</li> 480 <li>virtual - virtual domain email alias maps</li>
306</ul> 481</ul>
307</p> 482
308<pre caption="alias table sample" > 483<pre caption="alias table sample">
309id alias destination 484id alias destination
3101 root foo@bar.com 4851 root foo@bar.com
3112 postmaster foo@bar.com 4862 postmaster foo@bar.com
312</pre> 487</pre>
488
313<pre caption="user table sample" > 489<pre caption="user table sample">
314<codenote>Line wrapped for clarity</codenote> 490<comment>(Line wrapped for clarity.)</comment>
315id email clear name uid gid homedir \ 491id email clear name uid gid homedir \
316 maildir quota postfix 492 maildir quota postfix
31710 foo@virt-bar.org $password realname virtid virtid /home/vmail \ 49310 foo@virt-bar.org $password realname virtid virtid /home/vmail \
318 /home/vmail/virt-bar.org/foo/.maildir/ y 494 /home/vmail/virt-bar.org/foo/.maildir/ y
31913 foo@bar.com $password realname localid localid /home/foo \ 49513 foo@bar.com $password realname localid localid /home/foo \
320 /home/foo/.maildir/ y 496 /home/foo/.maildir/ y
321</pre> 497</pre>
498
499<p>
500The values of the <c>virtid</c> uid and gid should be those of the <c>vmail</c>
501user and group.
502</p>
503
322<pre caption="transport table sample" > 504<pre caption="transport table sample">
323id domain destination 505id domain destination
3241 bar.com local: 5061 bar.com local:
3252 virt-bar.org virtual: 5072 virt-bar.org virtual:
326</pre> 508</pre>
509
327<pre caption="virtual table sample" > 510<pre caption="virtual table sample">
328id email destination 511id email destination
3293 root@virt-bar.org other@email.address 5123 root@virt-bar.org other@email.address
330</pre> 513</pre>
514
331</body> 515</body>
332</section> 516</section>
333</chapter> 517</chapter>
518
334<chapter> 519<chapter>
335<title>Apache and phpMyAdmin</title> 520<title>Apache and phpMyAdmin</title>
336<section> 521<section>
337<body> 522<body>
523
524<p>
338<p>Next we'll set up apache and add an interface to interact with the database more easily. </p> 525Next we'll set up apache and add an interface to interact with the database
526more easily.
527</p>
528
339<pre caption="Setting up apache and phpmyadmin" > 529<pre caption="Setting up apache and phpmyadmin">
340# <i>emerge apache mod_php phpmyadmin</i> 530# <i>emerge apache mod_php phpmyadmin</i>
341</pre> 531</pre>
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> 532
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: 533<p>
534There are plenty of guides out there about how to set up apache with php. Like
535this one: <uri>http://www.linuxguruz.org/z.php?id=31</uri>. There are also
536numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve
537problems with the installation (search for 'apache php'). So, that said, I'm
538not going to cover it here. Set up the apache and php installs, then continue
539with this howto. Now, a word for the wise: .htaccess the directory that you put
540phpmyadmin in. If you do not do this, search engine spiders will come along and
541index the page which in turn will mean that anyone will be able to find your
542phpmyadmin page via google and in turn be able to come change your database
543however they want which is <e>BAD!</e> There are many howtos on this
544including: <uri>http://www.csoft.net/docs/micro/htaccess.html.en</uri>.
545</p>
546
547<p>
548Now we're going to install the Apache certificates we made previously. The
549Apache-SSL directives that you need to use the resulting cert are:
550</p>
551
344 <ul> 552<ul>
345<li>SSLCertificateFile /path/to/certs/new.cert.cert</li> 553 <li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
346<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li> 554 <li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
347</ul> 555</ul>
348</p> 556
349<pre caption="Install Apache SSL certificates" > 557<pre caption="Install Apache SSL certificates">
350# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i> 558# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i>
351# <i>cp /etc/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i> 559# <i>cp /etc/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i>
352# <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i> 560# <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i>
561
353<codenote>Change the following parameters</codenote> 562<comment>(Change the following parameters)</comment>
354 563
355ServerName host.domain.name 564ServerName host.domain.name
356ServerAdmin your@email.address 565ServerAdmin your@email.address
357SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert 566SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert
358SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key 567SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key
359 568
360# <i>/etc/init.d/apache restart</i> 569# <i>/etc/init.d/apache restart</i>
361</pre> 570</pre>
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> 571
572<note>
573If you have an existing apache install, you'll likely have to perform a full
574server reboot to install your new certificates. Check your logs to verify
575apache restarted successfully.
576</note>
577
578<p>
363<p>Next, configure phpMyAdmin.</p> 579Next, configure phpMyAdmin.
580</p>
581
364<pre caption="Configuring phpMyAdmin" > 582<pre caption="Configuring phpMyAdmin">
365# <i>nano -w /var/www/localhost/htdocs/phpmyadmin/config.inc.php</i> 583# <i>nano -w /var/www/localhost/htdocs/phpmyadmin/config.inc.php</i>
366<codenote>Change the following parameters</codenote> 584<comment>(Change the following parameters.)</comment>
367 585
368$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname 586$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
369$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings 587$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
370 // (this user must have read-only 588 // (this user must have read-only
371$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot; 589$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the "mysql/user"
372 // and &quot;mysql/db&quot; tables) 590 // and "mysql/db" tables)
373$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user 591$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
374$cfg['Servers'][$i]['password'] = '$password'; // MySQL password 592$cfg['Servers'][$i]['password'] = '$password'; // MySQL password
375</pre> 593</pre>
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> 594
595<p>
596Now enter the phpmyadmin page and browse the tables. You'll want to add in your
597local aliases, edit your user table to add a test user, and change your
598transport table to add information about your domains. The default values
599supplied with the dumpfile should be a sufficient guide to what values need to
600go where. Make sure that if you put information in the database that it is
601accurate. For instance, make sure the local users home dir exists and that the
602correct uid/gid values are in place. The maildirs should be created
603automatically by postfix when the user receives their first email. So, in
604general, it's a good idea to send a "Welcome" mail to a new user
605after you setup their account to make sure the .maildir gets created.
606</p>
607
377</body> 608</body>
378</section> 609</section>
379</chapter> 610</chapter>
611
380<chapter> 612<chapter>
381<title>The vmail user</title> 613<title>The vmail user</title>
382<section> 614<section>
383<body> 615<body>
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> 616
617<p>
618At this point you may be wondering what user and directory to use for virtual
619mail users, and rightly so. Let's set that up.
620</p>
621
385<pre caption="Adding the vmail user" > 622<pre caption="Adding the vmail user">
386# <i>adduser -d /home/vmail -s /bin/false vmail</i> 623# <i>adduser -d /home/vmail -s /bin/false vmail</i>
387# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i> 624# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i>
388# <i>groupadd -g $uid vmail</i> 625# <i>groupadd -g $uid vmail</i>
389# <i>mkdir /home/vmail</i> 626# <i>mkdir /home/vmail</i>
390# <i>chown vmail. /home/vmail</i> 627# <i>chown vmail: /home/vmail</i>
628</pre>
629
630<p>
631So now when you're setting up vmail accounts, use the vmail uid, gid, and
632homedir. When you're setting up local accounts, use that users uid, gid, and
633homedir. We've been meaning to create a php admin page for this setup but
634haven't gotten around to it yet, as phpmyadmin generally works fine for us.
391</pre> 635</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> 636
393</body> 637</body>
394</section> 638</section>
395</chapter> 639</chapter>
640
396<chapter> 641<chapter>
397<title>Configuring MySQL Authentication and vhosts</title> 642<title>Configuring MySQL Authentication and vhosts</title>
398<section> 643<section>
399<body> 644<body>
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> 645
401<pre> 646<p>
647Next we'll reconfigure our authentication to use the mailsql database in
648courier-imap and postfix. In all of the following examples, replace
649<c>$password</c> with the password you set for the mailsql mysql user.
650</p>
651
652<pre caption="Configuring authentication">
402# <i>emerge pam_mysql</i> 653# <i>emerge pam_mysql</i>
403# <i>nano -w /etc/pam.d/imap</i> 654# <i>nano -w /etc/pam.d/imap</i>
404<codenote>Comment out the existing auth lines and add the following as shown.</codenote> 655<comment>(Comment out the existing auth lines and add the following as shown.)</comment>
405 656
406#auth required pam_nologin.so 657#auth required pam_nologin.so
407#auth required pam_stack.so service=system-auth 658#auth required pam_stack.so service=system-auth
408#account required pam_stack.so service=system-auth 659#account required pam_stack.so service=system-auth
409#session required pam_stack.so service=system-auth 660#session required pam_stack.so service=system-auth
413account required pam_mysql.so host=localhost db=mailsql user=mailsql \ 664account required pam_mysql.so host=localhost db=mailsql user=mailsql \
414 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 665 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
415 666
416# <i>nano -w /etc/pam.d/pop3</i> 667# <i>nano -w /etc/pam.d/pop3</i>
417# <i>nano -w /etc/pam.d/smtp</i> 668# <i>nano -w /etc/pam.d/smtp</i>
418<codenote>Make the same changes to the pop3 and smtp files</codenote> 669<comment>(Make the same changes to the pop3 and smtp files.)</comment>
419</pre> 670</pre>
671
672<p>
420<p>Next, we need to edit courier's authentication config's.</p> 673Next, we need to edit courier's authentication config's.
421<pre> 674</p>
675
676<pre caption="Configuring authentication">
422# <i>nano -w /etc/courier-imap/authdaemonrc</i> 677# <i>nano -w /etc/courier-imap/authdaemonrc</i>
423authmodulelist=&quot;authmysql authpam&quot; 678authmodulelist="authmysql authpam"
424 679
425# <i>nano -w /etc/courier-imap/authdaemond.conf</i> 680# <i>nano -w /etc/courier-imap/authdaemond.conf</i>
426AUTHDAEMOND=&quot;authdaemond.mysql&quot; 681AUTHDAEMOND="authdaemond.mysql"
427 682
428# <i>nano -w /etc/courier-imap/authmysqlrc</i> 683# <i>nano -w /etc/courier-imap/authmysqlrc</i>
429MYSQL_SERVER localhost 684MYSQL_SERVER localhost
430MYSQL_USERNAME mailsql 685MYSQL_USERNAME mailsql
431MYSQL_PASSWORD $password 686MYSQL_PASSWORD $password
432MYSQL_DATABASE mailsql 687MYSQL_DATABASE mailsql
433MYSQL_USER_TABLE users 688MYSQL_USER_TABLE users
434#MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext) 689<comment>(Make sure the following line is commented out since we're storing plaintext.)</comment>
690#MYSQL_CRYPT_PWFIELD crypt
435MYSQL_CLEAR_PWFIELD clear 691MYSQL_CLEAR_PWFIELD clear
436MYSQL_UID_FIELD uid 692MYSQL_UID_FIELD uid
437MYSQL_GID_FIELD gid 693MYSQL_GID_FIELD gid
438MYSQL_LOGIN_FIELD email 694MYSQL_LOGIN_FIELD email
439MYSQL_HOME_FIELD homedir 695MYSQL_HOME_FIELD homedir
441MYSQL_MAILDIR_FIELD maildir 697MYSQL_MAILDIR_FIELD maildir
442 698
443# <i>/etc/init.d/authdaemond restart</i> 699# <i>/etc/init.d/authdaemond restart</i>
444# <i>/etc/init.d/saslauthd restart</i> 700# <i>/etc/init.d/saslauthd restart</i>
445</pre> 701</pre>
446<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> 702
703<p>
704We're almost there I promise! Next, set up the rest of the necessary config's
705for postfix to interract with the database for all it's other transport needs.
706</p>
707
447<pre caption="/etc/postfix/mysql-aliases.cf" > 708<pre caption="/etc/postfix/mysql-aliases.cf">
448# <i>nano -w /etc/postfix/mysql-aliases.cf</i> 709# <i>nano -w /etc/postfix/mysql-aliases.cf</i>
449# mysql-aliases.cf 710# mysql-aliases.cf
450 711
451user = mailsql 712user = mailsql
452password = $password 713password = $password
454table = alias 715table = alias
455select_field = destination 716select_field = destination
456where_field = alias 717where_field = alias
457hosts = unix:/var/run/mysqld/mysqld.sock 718hosts = unix:/var/run/mysqld/mysqld.sock
458</pre> 719</pre>
720
459<pre caption="/etc/postfix/mysql-relocated.cf" > 721<pre caption="/etc/postfix/mysql-relocated.cf">
460# <i>nano -w /etc/postfix/mysql-relocated.cf</i> 722# <i>nano -w /etc/postfix/mysql-relocated.cf</i>
461# mysql-relocated.cf 723# mysql-relocated.cf
462 724
463user = mailsql 725user = mailsql
464password = $password 726password = $password
466table = relocated 728table = relocated
467select_field = destination 729select_field = destination
468where_field = email 730where_field = email
469hosts = unix:/var/run/mysqld/mysqld.sock 731hosts = unix:/var/run/mysqld/mysqld.sock
470</pre> 732</pre>
733
471<pre caption="/etc/postfix/mysql-transport.cf (optional)" > 734<pre caption="/etc/postfix/mysql-transport.cf (optional)">
472# <i>nano -w /etc/postfix/mysql-transport.cf</i> 735# <i>nano -w /etc/postfix/mysql-transport.cf</i>
473# mysql-transport.cf 736# mysql-transport.cf
474 737
475user = mailsql 738user = mailsql
476password = $password 739password = $password
478table = transport 741table = transport
479select_field = destination 742select_field = destination
480where_field = domain 743where_field = domain
481hosts = unix:/var/run/mysqld/mysqld.sock 744hosts = unix:/var/run/mysqld/mysqld.sock
482</pre> 745</pre>
746
483<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" > 747<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)">
484# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i> 748# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>
485#myql-virtual-gid.cf 749#myql-virtual-gid.cf
486 750
487user = mailsql 751user = mailsql
488password = $password 752password = $password
491select_field = gid 755select_field = gid
492where_field = email 756where_field = email
493additional_conditions = and postfix = 'y' 757additional_conditions = and postfix = 'y'
494hosts = unix:/var/run/mysqld/mysqld.sock 758hosts = unix:/var/run/mysqld/mysqld.sock
495</pre> 759</pre>
760
496<pre caption="/etc/postfix/mysql-virtual-maps.cf" > 761<pre caption="/etc/postfix/mysql-virtual-maps.cf">
497# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i> 762# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>
498#myql-virtual-maps.cf 763#myql-virtual-maps.cf
499 764
500user = mailsql 765user = mailsql
501password = $password 766password = $password
504select_field = maildir 769select_field = maildir
505where_field = email 770where_field = email
506additional_conditions = and postfix = 'y' 771additional_conditions = and postfix = 'y'
507hosts = unix:/var/run/mysqld/mysqld.sock 772hosts = unix:/var/run/mysqld/mysqld.sock
508</pre> 773</pre>
774
509<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" > 775<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)">
510# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i> 776# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>
511# mysql-virtual-uid.cf 777# mysql-virtual-uid.cf
512 778
513user = mailsql 779user = mailsql
514password = $password 780password = $password
517select_field = uid 783select_field = uid
518where_field = email 784where_field = email
519additional_conditions = and postfix = 'y' 785additional_conditions = and postfix = 'y'
520hosts = unix:/var/run/mysqld/mysqld.sock 786hosts = unix:/var/run/mysqld/mysqld.sock
521</pre> 787</pre>
788
522<pre caption="/etc/postfix/mysql-virtual.cf" > 789<pre caption="/etc/postfix/mysql-virtual.cf">
523# <i>nano -w /etc/postfix/mysql-virtual.cf</i> 790# <i>nano -w /etc/postfix/mysql-virtual.cf</i>
524# mysql-virtual.cf 791# mysql-virtual.cf
525 792
526user = mailsql 793user = mailsql
527password = $password 794password = $password
529table = virtual 796table = virtual
530select_field = destination 797select_field = destination
531where_field = email 798where_field = email
532hosts = unix:/var/run/mysqld/mysqld.sock 799hosts = unix:/var/run/mysqld/mysqld.sock
533</pre> 800</pre>
801
802<p>
534<p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p> 803Lastly, edit <path>/etc/postfix/main.cf</path> one more time.
804</p>
805
535<pre caption="/etc/postfix/main.cf" > 806<pre caption="/etc/postfix/main.cf">
536# <i>nano -w /etc/postfix/main.cf</i> 807# <i>nano -w /etc/postfix/main.cf</i>
537alias_maps = mysql:/etc/postfix/mysql-aliases.cf 808alias_maps = mysql:/etc/postfix/mysql-aliases.cf
538relocated_maps = mysql:/etc/postfix/mysql-relocated.cf 809relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
539 810
540local_transport = local 811local_transport = local
562<pre caption="Changing file permission"> 833<pre caption="Changing file permission">
563# <i>chmod 640 /etc/postfix/mysql-*.cf</i> 834# <i>chmod 640 /etc/postfix/mysql-*.cf</i>
564# <i>chgrp postfix /etc/postfix/mysql-*.cf</i> 835# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>
565</pre> 836</pre>
566 837
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> 838<p>
839As of Postfix 2.0.x, there were a number of significant changes over the 1.1.x
840release. Notably the transport, virtual-gid, and virtual-uid tables are no
841longer necessary. The tables are still included if you wish to use them.
842</p>
843
844<note>
568<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note> 845It is recommended that you read VIRTUAL_README included with the postfix docs
846for more information.
847</note>
848
849<pre caption="Make postfix reload its tables">
569<pre># <i>postfix reload</i> 850# <i>postfix reload</i>
851</pre>
852
853<p>
854Now, if all went well, you should have a functioning mailhost. Users should be
855able to authenticate against the sql database, using their full email address,
856for pop3, imap, and smtp. I would highly suggest that you verify that
857everything is working at this point. If you run into problems (with as many
858things as this setup has going on, it's likely that you will) check the
859troubleshooting section of this howto.
570</pre> 860</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> 861
572</body> 862</body>
573</section> 863</section>
574</chapter> 864</chapter>
865
575<chapter> 866<chapter>
576<title>Squirrelmail</title> 867<title>Squirrelmail</title>
577<section> 868<section>
578<body> 869<body>
579<pre> 870
871<pre caption="Install squirrelmail">
580# <i>emerge squirrelmail</i> 872# <i>emerge squirrelmail</i>
581<codenote>I like to add a link to the htdocs space for a shorter url.</codenote> 873<comment>(Install squirrelmail to localhost so that it's accessed by http://localhost/mail)
874(Substitute 1.4.3a-r2 with the version you use)</comment>
582 875
583# <i>ln -s /var/www/localhost/htdocs/squirrelmail/ /var/www/localhost/htdocs/mail</i> 876# <i>webapp-config -I -h localhost -d /mail squirrelmail 1.4.3a-r2</i>
584# <i>cd /var/www/localhost/htdocs/mail/conf</i> 877# <i>cd /var/www/localhost/htdocs/mail/config</i>
585# <i>./conf.pl</i> 878# <i>perl ./conf.pl</i>
586<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote> 879<comment>(Change your Organization, Server, and Folder settings for squirrelmail.
587<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote> 880Now you should be able to login to squirrelmail, again - with your full email address,
588<codenote>and use your new webmail setup.</codenote> 881and use your new webmail setup.)</comment>
589</pre> 882</pre>
883
590</body> 884</body>
591</section> 885</section>
592</chapter> 886</chapter>
887
593<chapter> 888<chapter>
594<title>Mailman</title> 889<title>Mailman</title>
595<section> 890<section>
596<body> 891<body>
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> 892
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> 893<p>
894Last step: mailman. The new version of mailman has very nice virtual domain
895support, which is why I use it, not to mention it's really a great package. To
896get this package installed and working correctly for virtual domains is going
897to require a bit of hacking. I really recommend reading all of the mailman
898documentation, including README.POSTFIX.gz, to understand what's being done
899here.
900</p>
901
902<p>
903One further note, current versions of mailman install to /usr/local/mailman. If
904you're like me and wish to change the default install location, it can be
905overridden in the ebuild filoe by changing the INSTALLDIR variable.
906</p>
907
599<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild"> 908<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
600# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i> 909# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i>
601MAILGID="280" 910MAILGID="280"
602<codenote>Set MAILGID to the mailman group instead of nobody</codenote> 911<comment>(Set MAILGID to the mailman group instead of nobody
603<codenote>This is needed for postfix integration</codenote> 912This is needed for postfix integration.)</comment>
604</pre>
605<pre> 913</pre>
914
915<pre caption="Install mailman">
606# <i>emerge mailman</i> 916# <i>emerge mailman</i>
607<codenote>This package is currently masked as well, so you'll need to unmask it or give </codenote> 917<comment>(This package is currently masked as well, so you'll need to unmask it or give
608<codenote>emerge an explicit path to the ebuild. Once it's installed, follow the directions</codenote> 918emerge an explicit path to the ebuild. Once it's installed, follow the directions
609<codenote>in the README.gentoo.gz *except* do not add your aliases to /etc/mail/aliases.</codenote> 919in the README.gentoo.gz *except* do not add your aliases to /etc/mail/aliases.
610<codenote>We will instead be linking the entire alias db into postfix.</codenote> 920We will instead be linking the entire alias db into postfix.)</comment>
611 921
612# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i> 922# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i>
613</pre> 923</pre>
924
614<pre caption="Setting defaults: Mailman/Defaults.py"> 925<pre caption="Setting defaults: Mailman/Defaults.py">
615# <i> nano -w /var/mailman/Mailman/Defaults.py</i> 926# <i> nano -w /var/mailman/Mailman/Defaults.py</i>
616<codenote>Change the values below to reflect your primary domain, virtuals will be set next.</codenote> 927<comment>(Change the values below to reflect your primary domain, virtuals will be set next.)</comment>
617DEFAULT_EMAIL_HOST = 'domain.com' 928DEFAULT_EMAIL_HOST = 'domain.com'
618DEFAULT_URL_HOST = 'www.domain.com' 929DEFAULT_URL_HOST = 'www.domain.com'
619</pre> 930</pre>
931
620<pre caption="mailman config: mm_cfg.py"> 932<pre caption="mailman config: mm_cfg.py">
621# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i> 933# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i>
622MTA = "Postfix" 934MTA = "Postfix"
623POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com'] 935POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']
624add_virtualhost('www.virt.domain.com', 'virt.domain.com') 936add_virtualhost('www.virt.domain.com', 'virt.domain.com')
625add_virtualhost('www.virt.domain2.com', 'virt.domain2.com') 937add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')
626<codenote>This is required for your virtual domains for mailman to function.</codenote> 938<comment>(This is required for your virtual domains for mailman to function.)</comment>
627</pre>
628<pre> 939</pre>
940
941<pre caption="And last but not least">
629<codenote>Once that's finished, add your first list.</codenote> 942<comment>(Once that's finished, add your first list.)</comment>
630 943
631# <i>su mailman</i> 944# <i>su mailman</i>
632# <i>cd ~</i> 945# <i>cd ~</i>
633# <i>bin/newlist test</i> 946# <i>bin/newlist test</i>
634Enter the email of the person running the list: your@email.address 947Enter the email of the person running the list: <i>your@email.address</i>
635Initial test password: 948Initial test password:
636Hit enter to continue with test owner notification... 949Hit enter to continue with test owner notification...
637<codenote>Virtual domain lists may be specified with</codenote> 950<comment>(Virtual domain lists may be specified with
638<codenote>list@domain.com style list names</codenote> 951list@domain.com style list names.)</comment>
639# <i>bin/genaliases</i> 952# <i>bin/genaliases</i>
640<codenote>Now that your aliases have been generated,</codenote> 953<comment>(Now that your aliases have been generated,
641<codenote>verify that they were added successfully.</codenote> 954verify that they were added successfully.)</comment>
642 955
643# <i>nano -w data/aliases</i> 956# <i>nano -w data/aliases</i>
644# STANZA START: test 957# STANZA START: test
645# CREATED: 958# CREATED:
646test: "|/var/mailman/mail/mailman post test" 959test: "|/var/mailman/mail/mailman post test"
655test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test" 968test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test"
656# STANZA END: test 969# STANZA END: test
657 970
658# <i>/etc/init.d/mailman start</i> 971# <i>/etc/init.d/mailman start</i>
659# <i>rc-update add mailman default</i> 972# <i>rc-update add mailman default</i>
660<codenote>To start mailman at once and on every reboot</codenote> 973<comment>(To start mailman at once and on every reboot.)</comment>
661</pre> 974</pre>
662 975
663<pre caption="Adding mailman alias support to postfix"> 976<pre caption="Adding mailman alias support to postfix">
664# <i>nano -w /etc/postfix/main.cf</i> 977# <i>nano -w /etc/postfix/main.cf</i>
665owner_request_special = no 978owner_request_special = no
666recipient_delimiter = + 979recipient_delimiter = +
667<codenote>Read README.POSTFIX.gz for details on this</codenote> 980<comment>(Read README.POSTFIX.gz for details on this.)</comment>
668 981
669alias_maps = 982alias_maps =
670 hash:/var/mailman/data/aliases, 983 hash:/var/mailman/data/aliases,
671 mysql:/etc/postfix/mysql-aliases.cf 984 mysql:/etc/postfix/mysql-aliases.cf
672 985
673virtual_alias_maps = 986virtual_alias_maps =
674 hash:/var/mailman/data/virtual-mailman, 987 hash:/var/mailman/data/virtual-mailman,
675 mysql:/etc/postfix/mysql-virtual.cf 988 mysql:/etc/postfix/mysql-virtual.cf
676<codenote>This adds mailman alias file support to postfix</codenote> 989<comment>(This adds mailman alias file support to postfix
677<codenote>You may of course use the mysql tables for this,</codenote> 990You may of course use the mysql tables for this,
678<codenote>but I hate doing that by hand. Also, if you are not</codenote> 991but I hate doing that by hand. Also, if you are not
679<codenote>using virtual domains, adding the virtual alias maps</codenote> 992using virtual domains, adding the virtual alias maps
680<codenote>to postfix may cause problems, be warned.</codenote> 993to postfix may cause problems, be warned.)</comment>
994</pre>
995
996<p>
997You should now be able to setup mailing lists for any domain on your box. Last
998note on this, make sure you run all mailman commands as the user mailman (<c>su
999mailman</c>) or else the permissions will be wrong and you'll have to fix them.
1000Read the mailman doc's for more information on setting up and managing mailman
1001lists.
681</pre> 1002</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> 1003
683</body> 1004</body>
684</section> 1005</section>
685</chapter> 1006</chapter>
1007
686<chapter> 1008<chapter>
687<title>Content Filtering and Anti-Virus</title> 1009<title>Content Filtering and Anti-Virus</title>
688<section> 1010<section>
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> 1011<body>
1012
1013<p>
1014For content filtering and Anti-Virus, please consult our <uri
1015link="/doc/en/mailfilter-guide.xml">mail filtering gateway guide</uri>.
1016</p>
1017
1018</body>
690</section> 1019</section>
691</chapter> 1020</chapter>
1021
692<chapter> 1022<chapter>
693<title>Wrap Up</title> 1023<title>Wrap Up</title>
694<section> 1024<section>
695<body> 1025<body>
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> 1026
1027<p>
1028Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off
1029verbose mode for production use. You'll probably also want to add the services
1030to your startup routine to make sure everything comes back up on a reboot. Make
1031sure to add all the services you're using - apache, mysql, saslauthd, postfix,
1032courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all
1033up to your decision on what access you want to provide. I generally have all
1034the services enabled.
1035</p>
1036
697<pre caption="Wrap up" > 1037<pre caption="Wrap up">
698# <i>postfix reload</i> 1038# <i>postfix reload</i>
699# <i>rc-update add $service default</i> 1039# <i>rc-update add $service default</i>
700</pre> 1040</pre>
1041
701<p> 1042<p>
702<e>Have fun!</e> 1043<e>Have fun!</e>
703</p> 1044</p>
1045
704</body> 1046</body>
705</section> 1047</section>
706</chapter> 1048</chapter>
1049
707<chapter> 1050<chapter>
708<title>Troubleshooting</title> 1051<title>Troubleshooting</title>
709<section> 1052<section>
710<title>Introduction</title> 1053<title>Introduction</title>
711<body> 1054<body>
712<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> 1055
1056<p>
1057Troubleshooting: This is a short troubleshooting guide for the set up we've
1058detailed how to install here. It is not exhaustive, but meant as a place to get
1059you started in figuring out problems. With a complicated setup such as this,
1060it's imperative that you narrow down the problem to the particular component
1061that is malfunctioning. In general I do that by following a few steps. Start
1062from the base of the system and work your way up, ruling out components that
1063work along the way until you discover which component is having the problem.
1064</p>
1065
713</body> 1066</body>
714</section>
715<section> 1067</section>
1068<section>
716<title>Step 1: Check your config files.</title> 1069<title>Step 1: Check your config files</title>
717<body> 1070<body>
718<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> 1071
719<pre> 1072<p>
1073Typos are killers, especially when dealing with authentication systems. Scan
1074your config's and mailsql database for typo's. You can debug all you want, but
1075if you're not passing the right information back and forth to your mail system,
1076it's not going to work. If you make a change to a config file for a service,
1077make sure you restart that service so that the config change gets picked up.
1078</p>
1079
1080<pre caption="How to restart a service">
720# <i>/etc/init.d/service restart</i> 1081# <i>/etc/init.d/service restart</i>
721</pre> 1082</pre>
1083
722</body> 1084</body>
723</section> 1085</section>
724<section> 1086<section>
725<title>Step 2: Are all the necessary services actually running?</title> 1087<title>Step 2: Are all the necessary services actually running?</title>
726<body> 1088<body>
727<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> 1089
728<pre> 1090<p>
1091If it's not running, start it up. It's awful hard to debug a service that isn't
1092running. Sometimes a service will act like it's started but still not function.
1093Sometimes, when a bad config is used, or a bad transmission comes into a mail
1094component, the service will hang and keep the port from being used by another
1095process. Sometimes you can detect this with netstat. Or, if you've been at it
1096awhile, just take a break and reboot your box in the meantime. That will clear
1097out any hung services. Then you can come back fresh and try it again.
1098</p>
1099
1100<pre caption="Checking the status of a service">
729# <i>/etc/init.d/$service status</i> 1101# <i>/etc/init.d/$service status</i>
730# <i>netstat -a | grep $service (or $port)</i> 1102# <i>netstat -a | grep $service (or $port)</i>
731</pre> 1103</pre>
1104
732</body> 1105</body>
733</section> 1106</section>
734<section> 1107<section>
735<title>Step 3: Are all the service using the current config's?</title> 1108<title>Step 3: Are all the service using the current config's?</title>
736<body> 1109<body>
737<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> 1110
738<pre> 1111<p>
1112If you've recently made a change to a config file, restart that service to make
1113sure it's using the current version. Some of the components will dump their
1114current config's to you, like postfix.
1115</p>
1116
1117<pre caption="Some services can dump their current config">
739# <i>apachectl fullstatus</i> (needs lynx installed) 1118# <i>apachectl fullstatus</i> (needs lynx installed)
740# <i>apachectl configtest</i> (checks config sanity) 1119# <i>apachectl configtest</i> (checks config sanity)
741# <i>postconf -n</i> (will tell you exactly what param's postfix is using) 1120# <i>postconf -n</i> (will tell you exactly what param's postfix is using)
742# <i>/etc/init.d/$service restart</i> 1121# <i>/etc/init.d/$service restart</i>
743</pre> 1122</pre>
1123
744</body> 1124</body>
745</section>
746<section> 1125</section>
1126<section>
747<title>Step 4: Check the logs.</title> 1127<title>Step 4: Check the logs</title>
748<body> 1128<body>
749<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> 1129
750<pre> 1130<p>
1131Repeat after me, logs are my friend. My next troubleshooting stop is always the
1132logs. Sometimes it's helpful to try a failed operation again then check the
1133logs so that the error message is right at the bottom (or top depending on your
1134logger) instead of buried in there somewhere. See if there is any information
1135in your log that can help you diagnose the problem, or at the very least,
1136figure out which component is having the problem.
1137</p>
1138
1139<pre caption="Checking the logs">
751# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering) 1140# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)
752# <i>nano -w /var/log/mail/current</i> 1141# <i>nano -w /var/log/mail/current</i>
753# <i>cat /var/log/mysql/mysql.log</i> 1142# <i>cat /var/log/mysql/mysql.log</i>
754# <i>tail /var/log/apache/error_log</i> 1143# <i>tail /var/log/apache/error_log</i>
755</pre> 1144</pre>
756<p>You may also find the debug_peer parameters in main.cf helpful. Setting these will increase log output over just verbose mode.</p> 1145
1146<p>
1147You may also find the debug_peer parameters in main.cf helpful. Setting these
1148will increase log output over just verbose mode.
1149</p>
1150
757<pre caption="adding debug_peer support"> 1151<pre caption="adding debug_peer support">
758# <i>nano -w /etc/postfix/main.cf</i> 1152# <i>nano -w /etc/postfix/main.cf</i>
759debug_peer_level = 5 1153debug_peer_level = 5
760debug_peer_list = $host.domain.name 1154debug_peer_list = $host.domain.name
761<codenote>Uncomment one of the suggested debugger</codenote> 1155<comment>(Uncomment one of the suggested debugger
762<codenote>commands as well.</codenote> 1156commands as well.)</comment>
763</pre> 1157</pre>
1158
764</body> 1159</body>
765</section>
766<section> 1160</section>
1161<section>
767<title>Step 5: Talk to the service itself.</title> 1162<title>Step 5: Talk to the service itself</title>
768<body> 1163<body>
769<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> 1164
770<pre> 1165<p>
1166SMTP, IMAP, and POP3 all respond to telnet sessions. As we've seen earlier when
1167we verified postfix's config. Sometimes it's helpful to open a telnet session
1168to the service itself and see what's happening.
1169</p>
1170
1171<pre caption="Connect to a service with telnet">
771# <i>telnet localhost $port</i> 1172# <i>telnet localhost $port</i>
772<codenote>SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,</codenote> 1173<comment>(SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,
773<codenote>letting you know that the service is running and ready to respond to requests.</codenote> 1174letting you know that the service is running and ready to respond to requests.)</comment>
774 1175
775Trying 127.0.0.1... 1176Trying 127.0.0.1...
776Connected to localhost. 1177Connected to localhost.
777Escape character is '^]'. 1178Escape character is '^]'.
778* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. 1179* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.
779</pre> 1180</pre>
1181
780</body> 1182</body>
781</section>
782<section> 1183</section>
1184<section>
783<title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title> 1185<title>Step 6: Sometimes only the big guns will give you the information you need: strace</title>
784<body> 1186<body>
785<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> 1187
786<pre> 1188<p>
1189You should have this installed anyway. This is an invaluable tool for debugging
1190software. You can start commands from the command line with strace and watch
1191all the system calls as they happen. It often dumps a huge amount of
1192information, so you'll either need to watch it realtime as you retry a failed
1193transaction with the mail system, or dump the output to a file for review.
1194</p>
1195
1196<pre caption="Using strace">
787# <i>emerge strace</i> 1197# <i>emerge strace</i>
788# <i>strace $command</i> 1198# <i>strace $command</i>
789# <i>strace -p `ps -C $service -o pid=`</i> 1199# <i>strace -p `ps -C $service -o pid=`</i>
790</pre> 1200</pre>
1201
791</body> 1202</body>
792</section> 1203</section>
793<section> 1204<section>
794<title>Step 7: Research</title> 1205<title>Step 7: Research</title>
795<body> 1206<body>
796<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> 1207
1208<p>
1209Once you have the information, if you can diagnose and fix the problem, great!
1210If not, you'll probably need to go digging on the net for information that will
1211help you fix it. Here's a list of sites you can check to see if your error has
1212already been resolved. There's also a really good howto on setting up smtp-auth
1213which contains some great debugging ideas.
797<p> 1214</p>
1215
798<ul> 1216<ul>
799<li>
800<uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users</li> 1217 <li><uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users</li>
801<li> 1218 <li>
802<uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place to look for specific errors</li> 1219 <uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place
803<li> 1220 to look for specific errors
1221 </li>
804<uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto</li> 1222 <li><uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto</li>
805<li> 1223 <li>
806<uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing lists - searchable</li> 1224 <uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing
1225 lists - searchable
1226 </li>
807<li> 1227 <li>
808<uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - Courier-imap mailing list archives - not searchable</li> 1228 <uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> -
1229 Courier-imap mailing list archives - not searchable
1230 </li>
809<li> 1231 <li>
810<uri>http://www.google.com/</uri> - If all else fails, there's always google, which has never failed me</li> 1232 <uri>http://www.google.com/</uri> - If all else fails, there's always
1233 google, which has never failed me
1234 </li>
1235 <li>
811<li>I also spend a lot of time on irc.freenode.net #gentoo. Irc is a great place to go for help.</li> 1236 I also spend a lot of time on irc.freenode.net #gentoo. Irc is a great
1237 place to go for help.
1238 </li>
812</ul> 1239</ul>
813</p> 1240
814</body> 1241</body>
815</section> 1242</section>
816</chapter> 1243</chapter>
817</guide> 1244</guide>
818

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

  ViewVC Help
Powered by ViewVC 1.1.20