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

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.55

  ViewVC Help
Powered by ViewVC 1.1.20