/[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.21 Revision 1.41
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.21 2003/12/07 18:21:26 pylon Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/virt-mail-howto.xml,v 1.41 2005/02/05 15:24:39 swift 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 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<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract> 14<author title="Editor">
15 <mail link="klasikahl@gentoo.org">Zack Gilburd</mail>
16</author>
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
14<version>1.0.6</version> 23<version>1.0.18</version>
15<date>December 7, 2003</date> 24<date>2005-02-05</date>
25
16<!-- 26<!--
17
18Contents 27Contents
19 28
20I. Introduction 29I. Introduction
21II. Postfix Basics 30II. Postfix Basics
22III. Courier-imap 31III. Courier-imap
30XI. Squirrelmail 39XI. Squirrelmail
31XII. Mailman 40XII. Mailman
32XIII. Content Filtering and Anti-Virus 41XIII. Content Filtering and Anti-Virus
33XIV. Wrap Up 42XIV. Wrap Up
34XV. Troubleshooting 43XV. Troubleshooting
44-->
35 45
36--><chapter> 46<chapter>
37<title>Introduction</title> 47<title>Introduction</title>
38<body> 48<section>
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:
44
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> 49<body>
50
51<p>
52For most gentoo users, a simple mail client and fetchmail will do. However, if
53you're hosting a domain with your system, you'll need a full blown MTA (Mail
54Transfer Agent). And if you're hosting multiple domains, then you'll definitely
55need something more robust to handle all of the email for your users. This
56system was designed to be an elegant solution to that problem.
57</p>
58
59<p>
60A virtual mail system needs to be able to handle email for numerous domains
61with multiple users over a variety of interfaces. This presents some issues
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
136</body>
137</section>
53</chapter> 138</chapter>
139
54<chapter> 140<chapter>
55<title>Postfix Basics</title> 141<title>Postfix Basics</title>
142<section>
56<body> 143<body>
57<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>:
58</pre> 157</p>
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> 158
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" > 159<pre caption="/etc/postfix/main.cf">
62myhostname = $host.domain.name 160myhostname = $host.domain.name
63mydomain = $domain.name 161mydomain = $domain.name
64inet_interfaces = all 162inet_interfaces = all
65mydestination = $myhostname, localhost.$mydomain $mydomain 163mydestination = $myhostname, localhost.$mydomain $mydomain
66mynetworks = my.ip.net.work/24, 127.0.0.0/8 164mynetworks = my.ip.net.work/24, 127.0.0.0/8
67home_mailbox = .maildir/ 165home_mailbox = .maildir/
68local_destination_concurrency_limit = 2 166local_destination_concurrency_limit = 2
69default_destination_concurrency_limit = 10 </pre> 167default_destination_concurrency_limit = 10
168</pre>
169
170<p>
70<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
71<pre caption="/etc/postfix/master.cf" > 175<pre caption="/etc/postfix/master.cf">
72# service type private unpriv chroot wakeup maxproc command + args 176# service type private unpriv chroot wakeup maxproc command + args
73# (yes) (yes) (yes) (never) (50) 177# (yes) (yes) (yes) (never) (50)
74# 178#
75========================================================================== 179==========================================================================
180<comment>(Just add the "-v" after the smtpd in the following line)</comment>
76smtp inet n - n - - smtpd -v 181smtp inet n - n - - smtpd -v
182</pre>
77 183
78<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>.
79</pre> 187</p>
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> 188
81<pre caption="Starting postfix for the first time" > 189<pre caption="Starting postfix for the first time">
82# <i>/usr/bin/newaliases</i> 190# <i>/usr/bin/newaliases</i>
83<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
84<codenote>when you update or install aliases.</codenote> 192when you update or install aliases.)</comment>
85 193
86# <i>/etc/init.d/postfix start</i> 194# <i>/etc/init.d/postfix start</i>
87</pre> 195</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> 196
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> 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
90</body> 209</body>
210</section>
91</chapter> 211</chapter>
212
92<chapter> 213<chapter>
93<title>Courier-imap</title> 214<title>Courier-imap</title>
215<section>
94<body> 216<body>
95<pre caption="Install courier-imap" ># <i>emerge courier-imap</i> 217
218<pre caption="Install courier-imap">
219# <i>emerge courier-imap</i>
96</pre> 220</pre>
221
97<pre caption="Courier-imap configuration" > 222<pre caption="Courier-imap configuration">
98# <i>cd /etc/courier-imap</i> 223# <i>cd /etc/courier-imap</i>
99<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,
100<codenote>you'll need to create certs for this purpose.</codenote> 225you'll need to create certs for this purpose.
101<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>
102 227
103# <i>nano -w pop3d.cnf</i> 228# <i>nano -w pop3d.cnf</i>
104# <i>nano -w imapd.cnf</i> 229# <i>nano -w imapd.cnf</i>
105<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>
106 231
107# <i>mkpop3dcert</i> 232# <i>mkpop3dcert</i>
108# <i>mkimapdcert</i> 233# <i>mkimapdcert</i>
109</pre> 234</pre>
235
110<pre caption="Start the courier services you need." > 236<pre caption="Start the courier services you need.">
111# <i>/etc/init.d/courier-imapd start</i> 237# <i>/etc/init.d/courier-imapd start</i>
112# <i>/etc/init.d/courier-imapd-ssl start</i> 238# <i>/etc/init.d/courier-imapd-ssl start</i>
113# <i>/etc/init.d/courier-pop3d start</i> 239# <i>/etc/init.d/courier-pop3d start</i>
114# <i>/etc/init.d/courier-pop3d-ssl start</i> 240# <i>/etc/init.d/courier-pop3d-ssl start</i>
115</pre> 241</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> 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
117</body> 251</body>
252</section>
118</chapter> 253</chapter>
254
119<chapter> 255<chapter>
120<title>Cyrus-sasl</title> 256<title>Cyrus-sasl</title>
257<section>
121<body> 258<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> 259
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> 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
124<pre caption="Configuring and installing the cyrus-sasl ebuild" > 269<pre caption="Configuring and installing the cyrus-sasl ebuild">
125# <i>USE='-ldap -mysql' emerge cyrus-sasl</i> 270# <i>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> 271</pre>
272
273<p>
129<p>Next, edit <path>/usr/lib/sasl2/smtp.conf</path>.</p> 274Next, edit <path>/etc/sasl2/smtpd.conf</path>.
275</p>
276
130<pre caption="Starting sasl" > 277<pre caption="Starting sasl">
131# <i>nano -w /usr/lib/sasl2/smtp.conf</i> 278# <i>nano -w /etc/sasl2/smtpd.conf</i>
279mech_list: PLAIN LOGIN
132pwcheck_method: saslauthd 280pwcheck_method: saslauthd
133mech_list: LOGIN PLAIN 281# <i>nano -w /etc/conf.d/saslauthd</i>
134<codenote>It's important to turn off auth mehtods we are not using.</codenote> 282SASLAUTHD_OPTS="${SASLAUTH_MECH} -a pam -r"
135<codenote>They cause problems for some mail clients.</codenote>
136# <i>/etc/init.d/saslauthd start</i> 283# <i>/etc/init.d/saslauthd start</i>
137</pre> 284</pre>
285
138</body> 286</body>
287</section>
139</chapter> 288</chapter>
289
140<chapter> 290<chapter>
141<title>SSL Certs for Postfix and Apache</title> 291<title>SSL Certs for Postfix and Apache</title>
292<section>
142<body> 293<body>
294
295<p>
143<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.
144<pre> 297</p>
298
299<pre caption="Making ssl certicates">
145# <i>cd /etc/ssl/</i> 300# <i>cd /etc/ssl/</i>
146# <i>nano -w openssl.cnf</i> 301# <i>nano -w openssl.cnf</i>
147 302
148<codenote>Change the following default values for your domain:</codenote> 303<comment>Change the following default values for your domain:</comment>
149countryName_default 304countryName_default
150stateOrProvinceName_default 305stateOrProvinceName_default
151localityName_default 306localityName_default
1520.organizationName_default 3070.organizationName_default
153commonName_default 308commonName_default
154emailAddress_default. 309emailAddress_default.
155 310
156<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>
157
158 312
159# <i>cd misc</i> 313# <i>cd misc</i>
160# <i>nano -w CA.pl</i> 314# <i>nano -w CA.pl</i>
161<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
162<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
163<codenote>certs be loaded without a password. Otherwise when you</codenote> 317certs be loaded without a password. Otherwise when you
164<codenote>reboot your ssl certs will not be available.</codenote> 318reboot your ssl certs will not be available.)</comment>
165 319
166# create a certificate 320# create a certificate
167system (&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");
168 322
169# create a certificate request 323# create a certificate request
170system (&quot;$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS&quot;); 324system ("$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS");
171 325
172# <i>./CA.pl -newca</i> 326# <i>./CA.pl -newca</i>
173# <i>./CA.pl -newreq</i> 327# <i>./CA.pl -newreq</i>
174# <i>./CA.pl -sign</i> 328# <i>./CA.pl -sign</i>
175# <i>cp newcert.pem /etc/postfix</i> 329# <i>cp newcert.pem /etc/postfix</i>
176# <i>cp newreq.pem /etc/postfix</i> 330# <i>cp newreq.pem /etc/postfix</i>
177# <i>cp demoCA/cacert.pem /etc/postfix</i> 331# <i>cp demoCA/cacert.pem /etc/postfix</i>
178<codenote>Now we do the same thing for apache</codenote> 332<comment>(Now we do the same thing for apache.)</comment>
179 333
180# <i>openssl req -new > new.cert.csr</i> 334# <i>openssl req -new > new.cert.csr</i>
181# <i>openssl rsa -in privkey.pem -out new.cert.key</i> 335# <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> 336# <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> 337<comment>(Just leave the resulting certificates here for now.
184<codenote>We'll install them after Apache is installed.</codenote> 338We'll install them after Apache is installed.)</comment>
185</pre> 339</pre>
340
186</body> 341</body>
342</section>
343
187</chapter> 344</chapter>
188<chapter> 345<chapter>
189<title>Adding SSL and SASL support to Postfix</title> 346<title>Adding SSL and SASL support to Postfix</title>
347<section>
190<body> 348<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> 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
192<pre caption="/etc/postfix/main.cf" > 356<pre caption="/etc/postfix/main.cf">
193# <i>nano -w /etc/postfix/main.cf</i> 357# <i>nano -w /etc/postfix/main.cf</i>
194 358
195smtpd_sasl_auth_enable = yes 359smtpd_sasl_auth_enable = yes
196smtpd_sasl2_auth_enable = yes 360smtpd_sasl2_auth_enable = yes
197smtpd_sasl_security_options = noanonymous 361smtpd_sasl_security_options = noanonymous
198broken_sasl_auth_clients = yes 362broken_sasl_auth_clients = yes
199smtpd_sasl_local_domain = 363smtpd_sasl_local_domain =
200 364
201<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
202<codenote>are for outlook and outlook express only and are undocumented.</codenote> 366are for outlook and outlook express only and are undocumented.
203<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?
204<codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote> 368smtpd_sasl_local_domain appends a domain name to clients using
205<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
206<codenote>mangled by postfix and be unable to auth.</codenote> 370mangled by postfix and be unable to auth.)</comment>
207 371
208smtpd_recipient_restrictions = 372smtpd_recipient_restrictions =
209 permit_sasl_authenticated, 373 permit_sasl_authenticated,
210 permit_mynetworks, 374 permit_mynetworks,
211 reject_unauth_destination 375 reject_unauth_destination
219smtpd_tls_loglevel = 3 383smtpd_tls_loglevel = 3
220smtpd_tls_received_header = yes 384smtpd_tls_received_header = yes
221smtpd_tls_session_cache_timeout = 3600s 385smtpd_tls_session_cache_timeout = 3600s
222tls_random_source = dev:/dev/urandom 386tls_random_source = dev:/dev/urandom
223 387
224<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.
225<codenote>You can turn this on later if you desire.</codenote> 389You can turn this on later if you desire.)</comment>
226 390
227# <i>postfix reload</i> 391# <i>postfix reload</i>
228</pre> 392</pre>
393
394<p>
229<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
230<pre caption="Verifying sasl and tls support" > 398<pre caption="Verifying sasl and tls support">
231# <i>telnet localhost 25</i> 399# <i>telnet localhost 25</i>
232 400
233Trying 127.0.0.1... 401Trying 127.0.0.1...
234Connected to localhost. 402Connected to localhost.
235Escape character is '^]'. 403Escape character is '^]'.
246250-XVERP 414250-XVERP
247250 8BITMIME 415250 8BITMIME
248<i>^]</i> 416<i>^]</i>
249telnet> <i>quit</i> 417telnet> <i>quit</i>
250</pre> 418</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. 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.
252 </p> 426</p>
427
253</body> 428</body>
429</section>
254</chapter> 430</chapter>
431
255<chapter> 432<chapter>
256<title>MySQL</title> 433<title>MySQL</title>
434<section>
257<body> 435<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> 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
259<pre caption="Installing and configuring MySQL" > 443<pre caption="Installing and configuring MySQL">
260# <i>emerge mysql</i> 444# <i>emerge mysql</i>
261 445
262# <i>/usr/bin/mysql_install_db</i> 446# <i>/usr/bin/mysql_install_db</i>
263<codenote>After this command runs follow the onscreen directions</codenote> 447<comment>(After this command runs follow the onscreen directions
264<codenote>for adding a root password with mysql,</codenote> 448for adding a root password with mysql,
265<codenote>not mysqladmin, otherwise your db will be wide open.</codenote> 449not mysqladmin, otherwise your db will be wide open.)</comment>
266 450
267# <i>/etc/init.d/mysql start</i> 451# <i>/etc/init.d/mysql start</i>
268# <i>mysqladmin -u root -p create mailsql</i> 452# <i>mysqladmin -u root -p create mailsql</i>
269# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i> 453# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>
270 454
273 -> <i>ON mailsql.*</i> 457 -> <i>ON mailsql.*</i>
274 -> <i>TO mailsql@localhost</i> 458 -> <i>TO mailsql@localhost</i>
275 -> <i>IDENTIFIED BY '$password';</i> 459 -> <i>IDENTIFIED BY '$password';</i>
276 460
277 -> <i>quit</i> 461 -> <i>quit</i>
278<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>
279 463
280# <i>mysql -u mailsql -p mailsql</i> 464# <i>mysql -u mailsql -p mailsql</i>
281</pre> 465</pre>
466
467<p>
282<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
283 <ul> 472<ul>
284<li>alias - local email alias and mailman alias information.</li> 473 <li>alias - local email alias and mailman alias information.</li>
285<li>relocated - relocated user email address maps</li> 474 <li>relocated - relocated user email address maps</li>
475 <li>
286<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>
287<li>users - all user account information</li> 479 <li>users - all user account information</li>
288<li>virtual - virtual domain email alias maps</li> 480 <li>virtual - virtual domain email alias maps</li>
289</ul> 481</ul>
290</p> 482
291<pre caption="alias table sample" > 483<pre caption="alias table sample">
292id alias destination 484id alias destination
2931 root foo@bar.com 4851 root foo@bar.com
2942 postmaster foo@bar.com 4862 postmaster foo@bar.com
295</pre> 487</pre>
488
296<pre caption="user table sample" > 489<pre caption="user table sample">
297<codenote>Line wrapped for clarity</codenote> 490<comment>(Line wrapped for clarity.)</comment>
298id email clear name uid gid homedir \ 491id email clear name uid gid homedir \
299 maildir quota postfix 492 maildir quota postfix
30010 foo@virt-bar.org $password realname virtid virtid /home/vmail \ 49310 foo@virt-bar.org $password realname virtid virtid /home/vmail \
301 /home/vmail/virt-bar.org/foo/.maildir/ y 494 /home/vmail/virt-bar.org/foo/.maildir/ y
30213 foo@bar.com $password realname localid localid /home/foo \ 49513 foo@bar.com $password realname localid localid /home/foo \
303 /home/foo/.maildir/ y 496 /home/foo/.maildir/ y
304</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
305<pre caption="transport table sample" > 504<pre caption="transport table sample">
306id domain destination 505id domain destination
3071 bar.com local: 5061 bar.com local:
3082 virt-bar.org virtual: 5072 virt-bar.org virtual:
309</pre> 508</pre>
509
310<pre caption="virtual table sample" > 510<pre caption="virtual table sample">
311id email destination 511id email destination
3123 root@virt-bar.org other@email.address 5123 root@virt-bar.org other@email.address
313</pre> 513</pre>
514
314</body> 515</body>
516</section>
315</chapter> 517</chapter>
518
316<chapter> 519<chapter>
317<title>Apache and phpMyAdmin</title> 520<title>Apache and phpMyAdmin</title>
521<section>
318<body> 522<body>
523
524<p>
319<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
320<pre caption="Setting up apache and phpmyadmin" > 529<pre caption="Setting up apache and phpmyadmin">
321# <i>emerge apache mod_php phpmyadmin</i> 530# <i>emerge apache mod_php phpmyadmin</i>
322</pre> 531</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> 532
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: 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
325 <ul> 552<ul>
326<li>SSLCertificateFile /path/to/certs/new.cert.cert</li> 553 <li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
327<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li> 554 <li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
328</ul> 555</ul>
329</p> 556
330<pre caption="Install Apache SSL certificates" > 557<pre caption="Install Apache SSL certificates">
331# <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>
332# <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>
333# <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
334<codenote>Change the following parameters</codenote> 562<comment>(Change the following parameters)</comment>
335 563
336ServerName host.domain.name 564ServerName host.domain.name
337ServerAdmin your@email.address 565ServerAdmin your@email.address
338SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert 566SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert
339SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key 567SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key
340 568
341# <i>/etc/init.d/apache restart</i> 569# <i>/etc/init.d/apache restart</i>
342</pre> 570</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> 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>
344<p>Next, configure phpMyAdmin.</p> 579Next, configure phpMyAdmin.
580</p>
581
345<pre caption="Configuring phpMyAdmin" > 582<pre caption="Configuring phpMyAdmin">
346# <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>
347<codenote>Change the following parameters</codenote> 584<comment>(Change the following parameters.)</comment>
348 585
349$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname 586$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
350$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings 587$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
351 // (this user must have read-only 588 // (this user must have read-only
352$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot; 589$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the "mysql/user"
353 // and &quot;mysql/db&quot; tables) 590 // and "mysql/db" tables)
354$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user 591$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
355$cfg['Servers'][$i]['password'] = '$password'; // MySQL password 592$cfg['Servers'][$i]['password'] = '$password'; // MySQL password
356</pre> 593</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> 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
358</body> 608</body>
609</section>
359</chapter> 610</chapter>
611
360<chapter> 612<chapter>
361<title>The vmail user</title> 613<title>The vmail user</title>
614<section>
362<body> 615<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> 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
364<pre caption="Adding the vmail user" > 622<pre caption="Adding the vmail user">
365# <i>adduser -d /home/vmail -s /bin/false vmail</i> 623# <i>adduser -d /home/vmail -s /bin/false vmail</i>
366# <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>
367# <i>groupadd -g $uid vmail</i> 625# <i>groupadd -g $uid vmail</i>
368# <i>mkdir /home/vmail</i> 626# <i>mkdir /home/vmail</i>
369# <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.
370</pre> 635</p>
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> 636
372</body> 637</body>
638</section>
373</chapter> 639</chapter>
640
374<chapter> 641<chapter>
375<title>Configuring MySQL Authentication and vhosts</title> 642<title>Configuring MySQL Authentication and vhosts</title>
643<section>
376<body> 644<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> 645
378<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">
379# <i>emerge pam_mysql</i> 653# <i>emerge pam_mysql</i>
380# <i>nano -w /etc/pam.d/imap</i> 654# <i>nano -w /etc/pam.d/imap</i>
381<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>
382 656
383#auth required pam_nologin.so 657#auth required pam_nologin.so
384#auth required pam_stack.so service=system-auth 658#auth required pam_stack.so service=system-auth
385#account required pam_stack.so service=system-auth 659#account required pam_stack.so service=system-auth
386#session required pam_stack.so service=system-auth 660#session required pam_stack.so service=system-auth
390account required pam_mysql.so host=localhost db=mailsql user=mailsql \ 664account required pam_mysql.so host=localhost db=mailsql user=mailsql \
391 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 665 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
392 666
393# <i>nano -w /etc/pam.d/pop3</i> 667# <i>nano -w /etc/pam.d/pop3</i>
394# <i>nano -w /etc/pam.d/smtp</i> 668# <i>nano -w /etc/pam.d/smtp</i>
395<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>
396</pre> 670</pre>
671
672<p>
397<p>Next, we need to edit courier's authentication config's.</p> 673Next, we need to edit courier's authentication config's.
398<pre> 674</p>
675
676<pre caption="Configuring authentication">
399# <i>nano -w /etc/courier-imap/authdaemonrc</i> 677# <i>nano -w /etc/courier-imap/authdaemonrc</i>
400authmodulelist=&quot;authmysql authpam&quot; 678authmodulelist="authmysql authpam"
401 679
402# <i>nano -w /etc/courier-imap/authdaemond.conf</i> 680# <i>nano -w /etc/courier-imap/authdaemond.conf</i>
403AUTHDAEMOND=&quot;authdaemond.mysql&quot; 681AUTHDAEMOND="authdaemond.mysql"
404 682
405# <i>nano -w /etc/courier-imap/authmysqlrc</i> 683# <i>nano -w /etc/courier-imap/authmysqlrc</i>
406MYSQL_SERVER localhost 684MYSQL_SERVER localhost
407MYSQL_USERNAME mailsql 685MYSQL_USERNAME mailsql
408MYSQL_PASSWORD $password 686MYSQL_PASSWORD $password
409MYSQL_DATABASE mailsql 687MYSQL_DATABASE mailsql
410MYSQL_USER_TABLE users 688MYSQL_USER_TABLE users
411#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
412MYSQL_CLEAR_PWFIELD clear 691MYSQL_CLEAR_PWFIELD clear
413MYSQL_UID_FIELD uid 692MYSQL_UID_FIELD uid
414MYSQL_GID_FIELD gid 693MYSQL_GID_FIELD gid
415MYSQL_LOGIN_FIELD email 694MYSQL_LOGIN_FIELD email
416MYSQL_HOME_FIELD homedir 695MYSQL_HOME_FIELD homedir
418MYSQL_MAILDIR_FIELD maildir 697MYSQL_MAILDIR_FIELD maildir
419 698
420# <i>/etc/init.d/authdaemond restart</i> 699# <i>/etc/init.d/authdaemond restart</i>
421# <i>/etc/init.d/saslauthd restart</i> 700# <i>/etc/init.d/saslauthd restart</i>
422</pre> 701</pre>
423<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
424<pre caption="/etc/postfix/mysql-aliases.cf" > 708<pre caption="/etc/postfix/mysql-aliases.cf">
425# <i>nano -w /etc/postfix/mysql-aliases.cf</i> 709# <i>nano -w /etc/postfix/mysql-aliases.cf</i>
426# mysql-aliases.cf 710# mysql-aliases.cf
427 711
428user = mailsql 712user = mailsql
429password = $password 713password = $password
431table = alias 715table = alias
432select_field = destination 716select_field = destination
433where_field = alias 717where_field = alias
434hosts = unix:/var/run/mysqld/mysqld.sock 718hosts = unix:/var/run/mysqld/mysqld.sock
435</pre> 719</pre>
720
436<pre caption="/etc/postfix/mysql-relocated.cf" > 721<pre caption="/etc/postfix/mysql-relocated.cf">
437# <i>nano -w /etc/postfix/mysql-relocated.cf</i> 722# <i>nano -w /etc/postfix/mysql-relocated.cf</i>
438# mysql-relocated.cf 723# mysql-relocated.cf
439 724
440user = mailsql 725user = mailsql
441password = $password 726password = $password
443table = relocated 728table = relocated
444select_field = destination 729select_field = destination
445where_field = email 730where_field = email
446hosts = unix:/var/run/mysqld/mysqld.sock 731hosts = unix:/var/run/mysqld/mysqld.sock
447</pre> 732</pre>
733
448<pre caption="/etc/postfix/mysql-transport.cf (optional)" > 734<pre caption="/etc/postfix/mysql-transport.cf (optional)">
449# <i>nano -w /etc/postfix/mysql-transport.cf</i> 735# <i>nano -w /etc/postfix/mysql-transport.cf</i>
450# mysql-transport.cf 736# mysql-transport.cf
451 737
452user = mailsql 738user = mailsql
453password = $password 739password = $password
455table = transport 741table = transport
456select_field = destination 742select_field = destination
457where_field = domain 743where_field = domain
458hosts = unix:/var/run/mysqld/mysqld.sock 744hosts = unix:/var/run/mysqld/mysqld.sock
459</pre> 745</pre>
746
460<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" > 747<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)">
461# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i> 748# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>
462#myql-virtual-gid.cf 749#myql-virtual-gid.cf
463 750
464user = mailsql 751user = mailsql
465password = $password 752password = $password
468select_field = gid 755select_field = gid
469where_field = email 756where_field = email
470additional_conditions = and postfix = 'y' 757additional_conditions = and postfix = 'y'
471hosts = unix:/var/run/mysqld/mysqld.sock 758hosts = unix:/var/run/mysqld/mysqld.sock
472</pre> 759</pre>
760
473<pre caption="/etc/postfix/mysql-virtual-maps.cf" > 761<pre caption="/etc/postfix/mysql-virtual-maps.cf">
474# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i> 762# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>
475#myql-virtual-maps.cf 763#myql-virtual-maps.cf
476 764
477user = mailsql 765user = mailsql
478password = $password 766password = $password
481select_field = maildir 769select_field = maildir
482where_field = email 770where_field = email
483additional_conditions = and postfix = 'y' 771additional_conditions = and postfix = 'y'
484hosts = unix:/var/run/mysqld/mysqld.sock 772hosts = unix:/var/run/mysqld/mysqld.sock
485</pre> 773</pre>
774
486<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" > 775<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)">
487# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i> 776# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>
488# mysql-virtual-uid.cf 777# mysql-virtual-uid.cf
489 778
490user = mailsql 779user = mailsql
491password = $password 780password = $password
494select_field = uid 783select_field = uid
495where_field = email 784where_field = email
496additional_conditions = and postfix = 'y' 785additional_conditions = and postfix = 'y'
497hosts = unix:/var/run/mysqld/mysqld.sock 786hosts = unix:/var/run/mysqld/mysqld.sock
498</pre> 787</pre>
788
499<pre caption="/etc/postfix/mysql-virtual.cf" > 789<pre caption="/etc/postfix/mysql-virtual.cf">
500# <i>nano -w /etc/postfix/mysql-virtual.cf</i> 790# <i>nano -w /etc/postfix/mysql-virtual.cf</i>
501# mysql-virtual.cf 791# mysql-virtual.cf
502 792
503user = mailsql 793user = mailsql
504password = $password 794password = $password
506table = virtual 796table = virtual
507select_field = destination 797select_field = destination
508where_field = email 798where_field = email
509hosts = unix:/var/run/mysqld/mysqld.sock 799hosts = unix:/var/run/mysqld/mysqld.sock
510</pre> 800</pre>
801
802<p>
511<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
512<pre caption="/etc/postfix/main.cf" > 806<pre caption="/etc/postfix/main.cf">
513# <i>nano -w /etc/postfix/main.cf</i> 807# <i>nano -w /etc/postfix/main.cf</i>
514alias_maps = mysql:/etc/postfix/mysql-aliases.cf 808alias_maps = mysql:/etc/postfix/mysql-aliases.cf
515relocated_maps = mysql:/etc/postfix/mysql-relocated.cf 809relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
516 810
517local_transport = local 811local_transport = local
528virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf 822virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
529virtual_uid_maps = static:$vmail-uid 823virtual_uid_maps = static:$vmail-uid
530virtual_mailbox_base = / 824virtual_mailbox_base = /
531#virtual_mailbox_limit = 825#virtual_mailbox_limit =
532</pre> 826</pre>
533<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> 827
828<p>
829For security reasons you should change the permissions of the various
830<path>/etc/mail/mysql-*.cf</path>:
831</p>
832
833<pre caption="Changing file permission">
834# <i>chmod 640 /etc/postfix/mysql-*.cf</i>
835# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>
836</pre>
837
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>
534<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">
535<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.
536</pre> 860</p>
537<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
538</body> 862</body>
863</section>
539</chapter> 864</chapter>
865
540<chapter> 866<chapter>
541<title>Squirrelmail</title> 867<title>Squirrelmail</title>
868<section>
542<body> 869<body>
543<pre> 870
871<pre caption="Install squirrelmail">
544# <i>emerge squirrelmail</i> 872# <i>emerge squirrelmail</i>
545<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>
546 875
547# <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>
548# <i>cd /var/www/localhost/htdocs/mail/conf</i> 877# <i>cd /var/www/localhost/htdocs/mail/config</i>
549# <i>./conf.pl</i> 878# <i>perl ./conf.pl</i>
550<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote> 879<comment>(Change your Organization, Server, and Folder settings for squirrelmail.
551<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,
552<codenote>and use your new webmail setup.</codenote> 881and use your new webmail setup.)</comment>
553</pre> 882</pre>
883
554</body> 884</body>
885</section>
555</chapter> 886</chapter>
887
556<chapter> 888<chapter>
557<title>Mailman</title> 889<title>Mailman</title>
890<section>
558<body> 891<body>
559<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
560<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
561<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild"> 908<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
562# <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>
563MAILGID="280" 910MAILGID="280"
564<codenote>Set MAILGID to the mailman group instead of nobody</codenote> 911<comment>(Set MAILGID to the mailman group instead of nobody
565<codenote>This is needed for postfix integration</codenote> 912This is needed for postfix integration.)</comment>
566</pre>
567<pre> 913</pre>
914
915<pre caption="Install mailman">
568# <i>emerge mailman</i> 916# <i>emerge mailman</i>
569<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
570<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
571<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.
572<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>
573 921
574# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i> 922# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i>
575</pre> 923</pre>
924
576<pre caption="Setting defaults: Mailman/Defaults.py"> 925<pre caption="Setting defaults: Mailman/Defaults.py">
577# <i> nano -w /var/mailman/Mailman/Defaults.py</i> 926# <i> nano -w /var/mailman/Mailman/Defaults.py</i>
578<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>
579DEFAULT_EMAIL_HOST = 'domain.com' 928DEFAULT_EMAIL_HOST = 'domain.com'
580DEFAULT_URL_HOST = 'www.domain.com' 929DEFAULT_URL_HOST = 'www.domain.com'
581</pre> 930</pre>
931
582<pre caption="mailman config: mm_cfg.py"> 932<pre caption="mailman config: mm_cfg.py">
583# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i> 933# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i>
584MTA = "Postfix" 934MTA = "Postfix"
585POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com'] 935POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']
586add_virtualhost('www.virt.domain.com', 'virt.domain.com') 936add_virtualhost('www.virt.domain.com', 'virt.domain.com')
587add_virtualhost('www.virt.domain2.com', 'virt.domain2.com') 937add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')
588<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>
589</pre>
590<pre> 939</pre>
940
941<pre caption="And last but not least">
591<codenote>Once that's finished, add your first list.</codenote> 942<comment>(Once that's finished, add your first list.)</comment>
592 943
593# <i>su mailman</i> 944# <i>su mailman</i>
594# <i>cd ~</i> 945# <i>cd ~</i>
595# <i>bin/newlist test</i> 946# <i>bin/newlist test</i>
596Enter 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>
597Initial test password: 948Initial test password:
598Hit enter to continue with test owner notification... 949Hit enter to continue with test owner notification...
599<codenote>Virtual domain lists may be specified with</codenote> 950<comment>(Virtual domain lists may be specified with
600<codenote>list@domain.com style list names</codenote> 951list@domain.com style list names.)</comment>
601# <i>bin/genaliases</i> 952# <i>bin/genaliases</i>
602<codenote>Now that your aliases have been generated,</codenote> 953<comment>(Now that your aliases have been generated,
603<codenote>verify that they were added successfully.</codenote> 954verify that they were added successfully.)</comment>
604 955
605# <i>nano -w data/aliases</i> 956# <i>nano -w data/aliases</i>
606# STANZA START: test 957# STANZA START: test
607# CREATED: 958# CREATED:
608test: "|/var/mailman/mail/mailman post test" 959test: "|/var/mailman/mail/mailman post test"
617test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test" 968test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test"
618# STANZA END: test 969# STANZA END: test
619 970
620# <i>/etc/init.d/mailman start</i> 971# <i>/etc/init.d/mailman start</i>
621# <i>rc-update add mailman default</i> 972# <i>rc-update add mailman default</i>
622<codenote>To start mailman at once and on every reboot</codenote> 973<comment>(To start mailman at once and on every reboot.)</comment>
623</pre> 974</pre>
624 975
625<pre caption="Adding mailman alias support to postfix"> 976<pre caption="Adding mailman alias support to postfix">
626# <i>nano -w /etc/postfix/main.cf</i> 977# <i>nano -w /etc/postfix/main.cf</i>
627owner_request_special = no 978owner_request_special = no
628recipient_delimiter = + 979recipient_delimiter = +
629<codenote>Read README.POSTFIX.gz for details on this</codenote> 980<comment>(Read README.POSTFIX.gz for details on this.)</comment>
630 981
631alias_maps = 982alias_maps =
632 hash:/var/mailman/data/aliases, 983 hash:/var/mailman/data/aliases,
633 mysql:/etc/postfix/mysql-aliases.cf 984 mysql:/etc/postfix/mysql-aliases.cf
634 985
635virtual_alias_maps = 986virtual_alias_maps =
636 hash:/var/mailman/data/virtual-mailman, 987 hash:/var/mailman/data/virtual-mailman,
637 mysql:/etc/postfix/mysql-virtual.cf 988 mysql:/etc/postfix/mysql-virtual.cf
638<codenote>This adds mailman alias file support to postfix</codenote> 989<comment>(This adds mailman alias file support to postfix
639<codenote>You may of course use the mysql tables for this,</codenote> 990You may of course use the mysql tables for this,
640<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
641<codenote>using virtual domains, adding the virtual alias maps</codenote> 992using virtual domains, adding the virtual alias maps
642<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.
643</pre> 1002</p>
644<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
645</body> 1004</body>
1005</section>
646</chapter> 1006</chapter>
1007
647<chapter> 1008<chapter>
648<title>Content Filtering and Anti-Virus</title> 1009<title>Content Filtering and Anti-Virus</title>
649<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> 1010<section>
1011<body>
1012
1013<p>
1014Coming soon...it would be done already but I need some perl help and testing to
1015make it so. If you'd like to volunteer for that, please email me.
1016</p>
1017
1018</body>
1019</section>
650</chapter> 1020</chapter>
1021
651<chapter> 1022<chapter>
652<title>Wrap Up</title> 1023<title>Wrap Up</title>
1024<section>
653<body> 1025<body>
654<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
655<pre caption="Wrap up" > 1037<pre caption="Wrap up">
656# <i>postfix reload</i> 1038# <i>postfix reload</i>
657# <i>rc-update add $service default</i> 1039# <i>rc-update add $service default</i>
658</pre> 1040</pre>
1041
659<p> 1042<p>
660<e>Have fun!</e> 1043<e>Have fun!</e>
661</p> 1044</p>
1045
662</body> 1046</body>
1047</section>
663</chapter> 1048</chapter>
1049
664<chapter> 1050<chapter>
665<title>Troubleshooting</title> 1051<title>Troubleshooting</title>
666<section> 1052<section>
667<title>Introduction</title> 1053<title>Introduction</title>
668<body> 1054<body>
669<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
670</body> 1066</body>
671</section>
672<section> 1067</section>
1068<section>
673<title>Step 1: Check your config files.</title> 1069<title>Step 1: Check your config files</title>
674<body> 1070<body>
675<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
676<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">
677# <i>/etc/init.d/service restart</i> 1081# <i>/etc/init.d/service restart</i>
678</pre> 1082</pre>
1083
679</body> 1084</body>
680</section> 1085</section>
681<section> 1086<section>
682<title>Step 2: Are all the necessary services actually running?</title> 1087<title>Step 2: Are all the necessary services actually running?</title>
683<body> 1088<body>
684<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
685<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">
686# <i>/etc/init.d/$service status</i> 1101# <i>/etc/init.d/$service status</i>
687# <i>netstat -a | grep $service (or $port)</i> 1102# <i>netstat -a | grep $service (or $port)</i>
688</pre> 1103</pre>
1104
689</body> 1105</body>
690</section> 1106</section>
691<section> 1107<section>
692<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>
693<body> 1109<body>
694<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
695<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">
696# <i>apachectl fullstatus</i> (needs lynx installed) 1118# <i>apachectl fullstatus</i> (needs lynx installed)
697# <i>apachectl configtest</i> (checks config sanity) 1119# <i>apachectl configtest</i> (checks config sanity)
698# <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)
699# <i>/etc/init.d/$service restart</i> 1121# <i>/etc/init.d/$service restart</i>
700</pre> 1122</pre>
1123
701</body> 1124</body>
702</section>
703<section> 1125</section>
1126<section>
704<title>Step 4: Check the logs.</title> 1127<title>Step 4: Check the logs</title>
705<body> 1128<body>
706<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
707<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">
708# <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)
709# <i>nano -w /var/log/mail/current</i> 1141# <i>nano -w /var/log/mail/current</i>
710# <i>cat /var/log/mysql/mysql.log</i> 1142# <i>cat /var/log/mysql/mysql.log</i>
711# <i>tail /var/log/apache/error_log</i> 1143# <i>tail /var/log/apache/error_log</i>
712</pre> 1144</pre>
713<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
714<pre caption="adding debug_peer support"> 1151<pre caption="adding debug_peer support">
715# <i>nano -w /etc/postfix/main.cf</i> 1152# <i>nano -w /etc/postfix/main.cf</i>
716debug_peer_level = 5 1153debug_peer_level = 5
717debug_peer_list = $host.domain.name 1154debug_peer_list = $host.domain.name
718<codenote>Uncomment one of the suggested debugger</codenote> 1155<comment>(Uncomment one of the suggested debugger
719<codenote>commands as well.</codenote> 1156commands as well.)</comment>
720</pre> 1157</pre>
1158
721</body> 1159</body>
722</section>
723<section> 1160</section>
1161<section>
724<title>Step 5: Talk to the service itself.</title> 1162<title>Step 5: Talk to the service itself</title>
725<body> 1163<body>
726<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
727<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">
728# <i>telnet localhost $port</i> 1172# <i>telnet localhost $port</i>
729<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,
730<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>
731 1175
732Trying 127.0.0.1... 1176Trying 127.0.0.1...
733Connected to localhost. 1177Connected to localhost.
734Escape character is '^]'. 1178Escape character is '^]'.
735* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. 1179* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.
736</pre> 1180</pre>
1181
737</body> 1182</body>
738</section>
739<section> 1183</section>
1184<section>
740<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>
741<body> 1186<body>
742<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
743<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">
744# <i>emerge strace</i> 1197# <i>emerge strace</i>
745# <i>strace $command</i> 1198# <i>strace $command</i>
746# <i>strace -p `ps -C $service -o pid=`</i> 1199# <i>strace -p `ps -C $service -o pid=`</i>
747</pre> 1200</pre>
1201
748</body> 1202</body>
749</section> 1203</section>
750<section> 1204<section>
751<title>Step 7: Research</title> 1205<title>Step 7: Research</title>
752<body> 1206<body>
753<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.
754<p> 1214</p>
1215
755<ul> 1216<ul>
756<li>
757<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>
758<li> 1218 <li>
759<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
760<li> 1220 to look for specific errors
1221 </li>
761<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>
762<li> 1223 <li>
763<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>
764<li> 1227 <li>
765<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>
766<li> 1231 <li>
767<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>
768<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>
769</ul> 1239</ul>
770</p> 1240
771</body> 1241</body>
772</section> 1242</section>
773</chapter> 1243</chapter>
774</guide> 1244</guide>
775

Legend:
Removed from v.1.21  
changed lines
  Added in v.1.41

  ViewVC Help
Powered by ViewVC 1.1.20