/[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.2 Revision 1.28
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version = '1.0' encoding = 'UTF-8'?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/virt-mail-howto.xml,v 1.28 2004/03/04 18:24:44 swift Exp $ -->
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
3<guide link =" /doc/en/virt-mail-howto.xml"> 5<guide link=" /doc/en/virt-mail-howto.xml" >
4
5<title>Virtual Mailhosting System Guide</title> 6<title>Virtual Mailhosting System with Postfix Guide</title>
6<author title="Author"><mail link="ken@kickasskungfu.com">Ken Nowack</mail></author> 7<author title="Author" >
7<author title="Author"><mail link="ezra@kickasskungfu.com">Ezra Gorman</mail></author> 8<mail link="antifa@gentoo.org" >Ken Nowack</mail>
8<author title="Editor"><mail link="zhen@gentoo.org">John P. Davis</mail></author> 9</author>
9 10<author title="Author" >
11<mail link="ezra@revoltltd.org" >Ezra Gorman</mail>
12</author>
13<author title="Editor">
14<mail link="klasikahl@gentoo.org" >Zack Gilburd</mail>
15</author>
10<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract> 16<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract>
11
12<version>1.1</version> 17<version>1.0.10</version>
18<date>March 4, 2004</date>
19<!--
13 20
14<date>13 Jan 2003</date> 21Contents
15 22
23I. Introduction
24II. Postfix Basics
25III. Courier-imap
26IV. Cyrus-sasl
27V. SSL Certificates for Postfix and Apache
28VI. Adding SSL and SASL support to Postfix
29VII. MySQL
30VIII. Apache and phpMyAdmin
31IX. The vmail user
32X. Configuring MySQL Authentication and vhosts
33XI. Squirrelmail
34XII. Mailman
35XIII. Content Filtering and Anti-Virus
36XIV. Wrap Up
37XV. Troubleshooting
38
16<chapter> 39--><chapter>
17<title>Introduction</title> 40<title>Introduction</title>
41<section>
18 <body> 42<body>
19 <p>For most Gentoo users, a simple mail client implemented with fetchmail will do. However, if you're hosting a domain with your system, you'll need a full blown MTA (Mail Transfer Agent). And if you're hosting multiple domains, then you'll definitely need something more robust to handle all of the email for your users. This system was designed to be an elegant solution to that problem.</p> 43<p>For most gentoo users, a simple mail client and fetchmail will do. However, if you're hosting a domain with your system, you'll need a full blown MTA (Mail Transfer Agent). And if you're hosting multiple domains, then you'll definitely need something more robust to handle all of the email for your users. This system was designed to be an elegant solution to that problem.</p>
44<p>A virtual mail system needs to be able to handle email for numerous domains with multiple users over a variety of interfaces. This presents some issues that must be dealt with. For instance, what if you have two users on different domains that want the same user name? If you are providing imap access and smtp-auth, how do combine the various authentication daemons into a single system? How do you provide security for the numerous components that comprise the system? How do you manage it all?</p>
45<p>This howto will show you how to set up with a mail system capable of handling mail for as many domains as your hardware can handle, supports virtual mail users that don't require shell accounts, has domain specific user names, can authenticate web, imap, smtp, and pop3 clients against a single database, utilizes ssl for transport layer security, has a web interface, can handle mailing lists for any domain on the machine, and is controlled by a nice, central and easy mysql database. </p>
46<p>There are quite a variety of ways to go about setting up a virtual mailhosting system. With so may options, another may be the best choice for your specific needs. Consider investigating <uri>http://www.qmail.org/</uri> and <uri>http://www.exim.org/</uri> to explore your options. </p>
47<p>The following packages are used in this setup:
20 48
21 <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> 49 apache, courier-imap, pam_mysql, postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p>
50<p>Make sure to turn on the following USE variables in <path>/etc/make.conf</path> before compiling the packages: <c>USE=&quot;mysql imap libwww maildir sasl ssl&quot;</c>. Otherwise you will most likely have to recompile things to get the support you need for all the protocols. Further, it's a good idea to turn off any other mail and network variables, like ipv6.</p>
51<impo>This howto was written for postfix-2.0.x. If you are using postfix &lt; 2 some of the variables in this document will be different. It is recommended that you upgrade. Some other packages included in this howto are version sensitive as well. You are advised to read the documentation included with packages if you run into issues with this.</impo>
52<impo>This document uses apache-1.3.x. Apache-2 has been marked stable in portage. However there are still a number of issues with php integration. Until php support in apache-2.0.x is marked stable, this guide will continue to use the 1.3.x version.</impo>
53<impo>You need a domain name to run a public mail server, or at least an MX record for a domain. Ideally you would have control of at least two domains to take advantage of your new virtual domain functionality.</impo>
54<impo>Make sure <path>/etc/hostname</path> is set to the right hostname for your mail server. Verify your hostname is set correctly with <c>hostname</c>. Also verify that there are no conflicting entries in <path>/etc/hosts</path>.</impo>
55<note>It is recommended that you read this entire document and familiarize yourself with all the steps before attempting the install. If you run into problems with any of the steps, check the troubleshooting guide at the end of this document. Also, not all the referenced packages are necessary, this set up is very flexible. For instance, if you do not desire a web interface, feel free to skip the squirrelmail section.</note>
56</body>
57</section>
58</chapter>
59
60<chapter>
61<title>Postfix Basics</title>
62<section>
63<body>
64<pre caption="Install postfix" ># <i>emerge postfix</i>
65</pre>
66<warn>Verify that you have not installed any other MTA, such as ssmtp, exim, or qmail, or you will surely have BIG problems.</warn>
67<p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p>
68<pre caption="/etc/postfix/main.cf" >
69myhostname = $host.domain.name
70mydomain = $domain.name
71inet_interfaces = all
72mydestination = $myhostname, localhost.$mydomain $mydomain
73mynetworks = my.ip.net.work/24, 127.0.0.0/8
74home_mailbox = .maildir/
75local_destination_concurrency_limit = 2
76default_destination_concurrency_limit = 10 </pre>
77<p>Next change the following in <path>/etc/postfix/master.cf</path>. This will turn on verbose output for debugging:</p>
78<pre caption="/etc/postfix/master.cf" >
79# service type private unpriv chroot wakeup maxproc command + args
80# (yes) (yes) (yes) (never) (50)
81#
82==========================================================================
83smtp inet n - n - - smtpd -v
84
85<codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote>
86</pre>
87<p>Next, edit <path>/etc/mail/aliases</path> to add your local aliases. There should at least be an alias for root like: <c>root: your@email.address</c>.</p>
88<pre caption="Starting postfix for the first time" >
89# <i>/usr/bin/newaliases</i>
90<codenote>This will install the new aliases. You only need to do this </codenote>
91<codenote>when you update or install aliases.</codenote>
22 92
23 <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> 93# <i>/etc/init.d/postfix start</i>
94</pre>
95<p>Now that postfix is running, fire up your favorite console mail client and send yourself an email. I use <c>mutt</c> for all my console mail. Verify that postfix is delivering mail to local users, once that's done, we're on to the next step.</p>
96<note>I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto. </note>
97</body>
98</section>
99</chapter>
100<chapter>
101<title>Courier-imap</title>
102<section>
103<body>
104<pre caption="Install courier-imap" ># <i>emerge courier-imap</i>
105</pre>
106<pre caption="Courier-imap configuration" >
107# <i>cd /etc/courier-imap</i>
108<codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote>
109<codenote>you'll need to create certs for this purpose.</codenote>
110<codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote>
111
112# <i>nano -w pop3d.cnf</i>
113# <i>nano -w imapd.cnf</i>
114<codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote>
115
116# <i>mkpop3dcert</i>
117# <i>mkimapdcert</i>
118</pre>
119<pre caption="Start the courier services you need." >
120# <i>/etc/init.d/courier-imapd start</i>
121# <i>/etc/init.d/courier-imapd-ssl start</i>
122# <i>/etc/init.d/courier-pop3d start</i>
123# <i>/etc/init.d/courier-pop3d-ssl start</i>
124</pre>
125<p>Start up your favorite mail client and verify that all connections you've started work for receiving and sending mail. Now that the basics work, we're going to do a whole bunch of stuff at once to get the rest of the system running. Again, please verify that what we've installed already works before progressing.</p>
126</body>
127</section>
128</chapter>
129<chapter>
130<title>Cyrus-sasl</title>
131<section>
132<body>
133<p>Next we're going to install cyrus-sasl. Sasl is going to play the role of actually passing your auth variables to pam, which will in turn pass that information to mysql for authentication of smtp users. For this howto, we'll not even try to verify that sasl is working until mysql is set up and contains a test user. Which is fine since we'll be authenticating against mysql in the end anyway.</p>
134<note>Now for some reason, sasl will not play nicely with pam against the shadow file. I banged my head against this problem for, well, a long time. If anyone knows why sasl will not auth against the shadow file in its current gentoo incarnation, please <mail link="ken@kickasskungfu.com" >email me</mail> as I'd love to hear a solution to this.</note>
135<pre caption="Configuring and installing the cyrus-sasl ebuild" >
136# <i>USE='-ldap -mysql' emerge cyrus-sasl</i>
137<codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote>
138<codenote>so we need to turn them off for this build.</codenote>
139</pre>
140<p>Next, edit <path>/etc/sasl2/smtpd.conf</path>.</p>
141<pre caption="Starting sasl" >
142# <i>nano -w /etc/sasl2/smtpd.conf</i>
143pwcheck_method: saslauthd
144mech_list: LOGIN PLAIN
145<codenote>It's important to turn off auth methods we are not using.</codenote>
146<codenote>They cause problems for some mail clients.</codenote>
147# <i>/etc/init.d/saslauthd start</i>
148</pre>
149</body>
150</section>
151</chapter>
152<chapter>
153<title>SSL Certs for Postfix and Apache</title>
154<section>
155<body>
156<p>Next we're going to make a set of ssl certificates for postfix and apache.</p>
157<pre>
158# <i>cd /etc/ssl/</i>
159# <i>nano -w openssl.cnf</i>
160
161<codenote>Change the following default values for your domain:</codenote>
162countryName_default
163stateOrProvinceName_default
164localityName_default
1650.organizationName_default
166commonName_default
167emailAddress_default.
168
169<codenote>If the variables are not already present, just add them in a sensible place.</codenote>
170
171
172# <i>cd misc</i>
173# <i>nano -w CA.pl</i>
174<codenote>We need to add -nodes to the # create a certificate and</codenote>
175<codenote>#create a certificate request code in order to let our new ssl</codenote>
176<codenote>certs be loaded without a password. Otherwise when you</codenote>
177<codenote>reboot your ssl certs will not be available.</codenote>
178
179# create a certificate
180system (&quot;$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS&quot;);
181
182# create a certificate request
183system (&quot;$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS&quot;);
24 184
25 <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> 185# <i>./CA.pl -newca</i>
186# <i>./CA.pl -newreq</i>
187# <i>./CA.pl -sign</i>
188# <i>cp newcert.pem /etc/postfix</i>
189# <i>cp newreq.pem /etc/postfix</i>
190# <i>cp demoCA/cacert.pem /etc/postfix</i>
191<codenote>Now we do the same thing for apache</codenote>
26 192
27 193# <i>openssl req -new > new.cert.csr</i>
28 <p>The following packages are used in this setup: 194# <i>openssl rsa -in privkey.pem -out new.cert.key</i>
29 195# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>
30 apache, courier-imap, pam_mysql, postfix, mod_php, mod_ssl, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p> 196<codenote>Just leave the resulting certificates here for now.</codenote>
31 197<codenote>We'll install them after Apache is installed.</codenote>
32 <p>Make sure to turn on the following USE variables in <path>/etc/make.conf</path> before compiling the packages: <c>USE="mysql imap libwww maildir sasl ssl"</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> 198</pre>
33
34 <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>
35
36 <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>
37
38
39 <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>
40 </body> 199</body>
41 200</section>
42</chapter>
43
44<chapter> 201</chapter>
45<title>Postfix Basics</title> 202<chapter>
203<title>Adding SSL and SASL support to Postfix</title>
204<section>
46 <body> 205<body>
47 <pre caption="Install Postfix"># <c>emerge postfix</c></pre> 206<p>Now edit the postfix config's to make it aware of your new sasl and ssl capabilities. Add the following parameters to the end of the file where they will be easy to find.</p>
48
49
50 <warn>Verify that you have not installed any other MTA, such as ssmtp, exim, or qmail, or you will surely have BIG problems.</warn>
51
52 <p>After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>:</p>
53
54 <pre caption="/etc/postfix/main.cf"> 207<pre caption="/etc/postfix/main.cf" >
55 myhostname = $host.domain.name 208# <i>nano -w /etc/postfix/main.cf</i>
56 mydomain = $domain.name
57 myorigin = $mydomain
58 inet_interfaces = all
59 mydestination = $myhostname, localhost.$mydomain $mydomain
60 relay_domains = $mydestination
61 mynetworks = my.ip.net.work/24, 127.0.0.0/8
62 local_destination_concurrency_limit = 2
63 default_destination_concurrency_limit = 10 </pre>
64
65
66 <p>Next change the following in <path>/etc/postfix/master.cf</path>. This will turn on verbose output for debugging:</p>
67 209
68 210smtpd_sasl_auth_enable = yes
69 <pre caption="/etc/postfix/master.cf"> 211smtpd_sasl2_auth_enable = yes
70 # service type private unpriv chroot wakeup maxproc command + args 212smtpd_sasl_security_options = noanonymous
71 # (yes) (yes) (yes) (never) (50) 213broken_sasl_auth_clients = yes
72 # 214smtpd_sasl_local_domain =
73 ========================================================================== 215
74 smtp inet n - n - - smtpd -v 216<codenote>The broken_sasl_auth_clients option and the login auth method </codenote>
75 217<codenote>are for outlook and outlook express only and are undocumented.</codenote>
76 <codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote> 218<codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote>
77 </pre> 219<codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote>
220<codenote>smtp-auth. Make sure it's blank or your user names will get</codenote>
221<codenote>mangled by postfix and be unable to auth.</codenote>
222
223smtpd_recipient_restrictions =
224 permit_sasl_authenticated,
225 permit_mynetworks,
226 reject_unauth_destination
78 227
79 <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>
80 228
81
82 <pre caption="Starting postfix for the first time">
83 # <c>/usr/bin/newaliases</c>
84
85 <codenote>This will install the new aliases. You only need to do this </codenote>
86 <codenote>when you update or install aliases.</codenote>
87
88 # <c>/etc/init.d/postfix start</c>
89 </pre>
90
91 <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, and once that's done, we're on to the next step.</p>
92
93
94 <note>I strongly recommend that you verify this basic Postfix setup is functioning before you progress to the next step of the howto. </note>
95 </body>
96
97</chapter>
98
99
100<chapter>
101<title>Courier-imap</title>
102 <body>
103 <pre caption="Install courier-imap"># <c>emerge courier-imap</c></pre>
104
105
106 <pre caption="Courier-imap configuration">
107 # <c>cd /etc/courier-imap</c>
108
109 <codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote>
110 <codenote>you'll need to create certs for this purpose.</codenote>
111 <codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote>
112
113 # <c>nano -w pop3d.cnf</c>
114 # <c>nano -w imapd.cnf</c>
115
116 <codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote>
117
118 # <i>mkpop3dcert</i>
119 # <i>mkimapdcert</i>
120 </pre>
121
122 <pre caption="Start the courier services you need.">
123 # <c>courier-imapd start</c>
124 # <c>courier-imapd-ssl start</c>
125 # <c>courier-pop3d start</c>
126 # <c>courier-pop3d-ssl start</c>
127 </pre>
128
129 <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>
130
131 </body>
132</chapter>
133
134<chapter>
135<title>Cyrus-sasl</title>
136 <body>
137 <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>
138
139 <note>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>
140
141 <p>Just to get sasl installed is going to require a bit of hacking. Open up the ebuild file and change the configure flags to disable digest and cram. Here's why: mail clients will try to authenticate against the <e>first</e> method presented to it, usually cram-md5. Since we're not going to set that up, cram authentication will fail and most clients will not by default try another method. This is mostly due to the way mail clients are currently put together. So we're going to disable auth methods we're not using in order to not confuse the clients out there.</p>
142
143
144 <pre caption="Configuring and installing the cyrus-sasl ebuild">
145 # <c>cd /usr/portage/dev-libs/cyrus-sasl</c>
146 # <c>nano -w cyrus-sasl.$currentversion.ebuild</c>
147
148 <codenote>Disable digest and cram as show below.</codenote>
149
150 econf \
151 --with-saslauthd=/var/lib/sasl2 \
152 --with-pwcheck=/var/lib/sasl2 \
153 --with-configdir=/etc/sasl2 \
154 --with-openssl \
155 --with-plugindir=/usr/lib/sasl2 \
156 --with-dbpath=/etc/sasl2/sasldb2 \
157 --with-des \
158 --with-rc4 \
159 --disable-krb4 \
160 --with-gnu-ld \
161 --enable-shared \
162 --disable-sample \
163 --enable-login \
164 --disable-cram \
165 --disable-digest \
166 ${myconf} || die "bad ./configure"
167
168 # <c>USE='-ldap -mysql' emerge cyrus-sasl</c>
169
170 <codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote>
171 <codenote>so we need to turn them off for this build.</codenote>
172 </pre>
173
174 <p>Now check that the directory <path>/var/lib/sasl2</path> exists. If it wasn't installed you need to create it. If it's there, go ahead and start sasl.</p>
175
176 <pre caption="Starting sasl">
177 # <c>mkdir /var/lib/sasl2 </c>
178
179<!--Ken, perhaps submit the above as a bug? The ebuild should take care of creating this dir. //zhen -->
180
181 <codenote>If saslauthd can't find the dir it will spew errors at you and refuse to start.</codenote>
182
183 # <i>/etc/init.d/saslauthd start</i>
184 </pre>
185 </body>
186</chapter>
187
188<chapter>
189<title>SSL Certs for Postfix and Apache</title>
190 <body>
191
192 <p>Next we're going to make a set of ssl certificates for postfix and apache.</p>
193
194 <pre>
195 # <c>cd /usr/lib/ssl/</c>
196 # <c>nano -w openssl.cnf</c>
197
198 <codenote>Change the following default values for your domain:</codenote>
199
200 countryName_default
201 stateOrProvinceName_default
202 localityName_default
203 0.organizationName_default
204 commonName_default
205 emailAddress_default.
206
207 <codenote>If the variables are not already present, just add them in a sensible place.</codenote>
208
209
210 # <c>cd misc</c>
211 # <c>nano -w CA.pl</c>
212
213 <codenote>We need to add -nodes to the # create a certificate and</codenote>
214 <codenote>#create a certificate request code in order to let our new ssl</codenote>
215 <codenote>certs be loaded without a password. Otherwise when you</codenote>
216 <codenote>reboot your ssl certs will not be available.</codenote>
217
218 # create a certificate
219 system ("$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS");
220
221 # create a certificate request
222 system ("$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS");
223
224 # <c>./CA.pl -newca</c>
225 # <c>./CA.pl -newreq</c>
226 # <c>./CA.pl -sign</c>
227 # <c>cp newcert.pem /etc/postfix</c>
228 # <c>cp newreq.pem /etc/postfix</c>
229 # <c>cp demoCA/cacert.pem /etc/postfix</c>
230
231 <codenote>Now we do the same thing for apache</codenote>
232
233
234 # <c>openssl req -new > new.cert.csr</c>
235 # <c>openssl rsa -in privkey.pem -out new.cert.key</c>
236 # <c>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</c>
237
238 <codenote>Just leave the resulting certificates here for now.</codenote>
239 <codenote>We'll install them after Apache is installed.</codenote>
240 </pre>
241 </body>
242</chapter>
243
244<chapter>
245<title>Adding SSL and SASL support to Postfix</title>
246 <body>
247 <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>
248
249 <pre caption="/etc/postfix/main.cf">
250 # <c>nano -w /etc/postfix/main.cf</c>
251
252 smtpd_sasl_auth_enable = yes
253 smtpd_sasl2_auth_enable = yes
254 smtpd_sasl_security_options = noanonymous
255 broken_sasl_auth_clients = yes
256 smtpd_sasl_local_domain =
257
258 <codenote>The broken_sasl_auth_clients option and the login auth method </codenote>
259 <codenote>are for outlook and outlook express only and are undocumented.</codenote>
260 <codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote>
261 <codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote>
262
263 <codenote>smtp-auth. Make sure it's blank or your user names will get</codenote>
264 <codenote>mangled by postfix and be unable to auth.</codenote>
265
266 smtpd_recipient_restrictions =
267 permit_sasl_authenticated,
268 permit_mynetworks,
269 check_relay_domains,
270 permit
271
272 smtpd_use_tls = yes 229smtpd_use_tls = yes
273 #smtpd_tls_auth_only = yes 230#smtpd_tls_auth_only = yes
274 smtpd_tls_key_file = /etc/postfix/newreq.pem 231smtpd_tls_key_file = /etc/postfix/newreq.pem
275 smtpd_tls_cert_file = /etc/postfix/newcert.pem 232smtpd_tls_cert_file = /etc/postfix/newcert.pem
276 smtpd_tls_CAfile = /etc/postfix/cacert.pem 233smtpd_tls_CAfile = /etc/postfix/cacert.pem
277 smtpd_tls_loglevel = 3 234smtpd_tls_loglevel = 3
278 smtpd_tls_received_header = yes 235smtpd_tls_received_header = yes
279 smtpd_tls_session_cache_timeout = 3600s 236smtpd_tls_session_cache_timeout = 3600s
280 tls_random_source = dev:/dev/urandom 237tls_random_source = dev:/dev/urandom
281 238
282 <codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote> 239<codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote>
283 <codenote>You can turn this on later if you desire.</codenote> 240<codenote>You can turn this on later if you desire.</codenote>
284 241
285 # <c>postfix reload</c> 242# <i>postfix reload</i>
286 </pre> 243</pre>
287
288 <p>Now we're going to verify that the config's we added were picked up by postfix.</p> 244<p>Now we're going to verify that the config's we added were picked up by postfix.</p>
289
290 <pre caption="Verifying sasl and tls support"> 245<pre caption="Verifying sasl and tls support" >
291 # <i>telnet localhost 25</i> 246# <i>telnet localhost 25</i>
292 247
293 Trying 127.0.0.1... 248Trying 127.0.0.1...
294 Connected to localhost. 249Connected to localhost.
295 Escape character is '^]'. 250Escape character is '^]'.
296 220 mail.domain.com ESMTP Postfix 251220 mail.domain.com ESMTP Postfix
297 <i>EHLO domain.com</i> 252<i>EHLO domain.com</i>
298 250-mail.domain.com 253250-mail.domain.com
299 250-PIPELINING 254250-PIPELINING
300 250-SIZE 10240000 255250-SIZE 10240000
301 250-VRFY 256250-VRFY
302 250-ETRN 257250-ETRN
303 250-STARTTLS 258250-STARTTLS
304 250-AUTH LOGIN PLAIN OTP 259250-AUTH LOGIN PLAIN
305 250-AUTH=LOGIN PLAIN OTP 260250-AUTH=LOGIN PLAIN
306 250-XVERP 261250-XVERP
307 250 8BITMIME 262250 8BITMIME
308 <i>^]</i> 263<i>^]</i>
309 telnet> <i>quit</i> 264telnet> <i>quit</i>
310 </pre> 265</pre>
311
312 <p>Verify that the above AUTH and STARTTLS lines now appear in your postfix install. As I said before, as it stands now AUTH will not work. that's because sasl will try to auth against it's sasldb, instead of the shadow file for some unknown reason, which we have not set up. So we're going to just plow through and set up mysql to hold all of our auth and virtual domain information. 266<p>Verify that the above AUTH and STARTTLS lines now appear in your postfix install. As I said before, as it stands now AUTH will not work. that's because sasl will try to auth against it's sasldb, instead of the shadow file for some unknown reason, which we have not set up. So we're going to just plow through and set up mysql to hold all of our auth and virtual domain information.
313 </p> 267 </p>
314
315 </body> 268</body>
269</section>
316</chapter> 270</chapter>
317
318<chapter> 271<chapter>
319<title>MySQL</title> 272<title>MySQL</title>
273<section>
320 <body> 274<body>
321
322 <p>Next we're going to install and configure MySQL. You'll need the <uri link="http://kickasskungfu.com/~ken/genericmailsql.sql">genericmailsql.sql</uri> dumpfile for this step.</p> 275<p>Next we're going to install and configure MySQL. You'll need the <uri link="http://kickasskungfu.com/~ken/genericmailsql.sql" >genericmailsql.sql</uri> dumpfile for this step.</p>
323
324 <pre caption="Installing and configuring MySQL"> 276<pre caption="Installing and configuring MySQL" >
325 # <c>emerge mysql</c> 277# <i>emerge mysql</i>
326 278
327 # <c>/usr/sbin/mysql_install_db</c> 279# <i>/usr/bin/mysql_install_db</i>
328
329 <codenote>After this command runs follow the onscreen directions</codenote> 280<codenote>After this command runs follow the onscreen directions</codenote>
330 <codenote>for adding a root password with mysql,</codenote> 281<codenote>for adding a root password with mysql,</codenote>
331 <codenote>not mysqladmin, otherwise your db will be wide open.</codenote> 282<codenote>not mysqladmin, otherwise your db will be wide open.</codenote>
332 283
333 # <c>/etc/init.d/mysql start</c> 284# <i>/etc/init.d/mysql start</i>
334 # <c>mysqladmin -u root -p create mailsql</c> 285# <i>mysqladmin -u root -p create mailsql</i>
335 # <c>mysql -u root -p --opt mailsql &lt; genericmailsql.sql</c> 286# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>
336 287
337 # <i>mysql -u root -p mysql</i> 288# <i>mysql -u root -p mysql</i>
338 mysql> <i>GRANT SELECT,INSERT,UPDATE,DELETE</i> 289mysql> <i>GRANT SELECT,INSERT,UPDATE,DELETE</i>
339 -> <i>ON mailsql.*</i> 290 -> <i>ON mailsql.*</i>
340 -> <i>TO mailsql@localhost</i> 291 -> <i>TO mailsql@localhost</i>
341 -> <i>IDENTIFIED BY '$password';</i> 292 -> <i>IDENTIFIED BY '$password';</i>
342 293
343 -> <i>quit</i> 294 -> <i>quit</i>
344
345 <codenote>Verify that the new mailsql user can connect to the mysql server.</codenote> 295<codenote>Verify that the new mailsql user can connect to the mysql server.</codenote>
346 296
347 # <c>mysql -u mailsql -p mailsql</c> 297# <i>mysql -u mailsql -p mailsql</i>
348 </pre> 298</pre>
349
350 <p>Your new database has default values and tables set up for two domains. The following tables are included: 299<p>Your new database has default values and tables set up for two domains. The following tables are included:
351 <ul> 300 <ul>
352 <li>alias - local email alias and mailman alias information.</li> 301<li>alias - local email alias and mailman alias information.</li>
353 <li>relocated - relocated user email address maps</li> 302<li>relocated - relocated user email address maps</li>
354 <li>transport - default mail transport information for all domains you are hosting</li> 303<li>transport - default mail transport information for all domains you are hosting</li>
355 <li>users - all user account information</li> 304<li>users - all user account information</li>
356 <li>virtual - virtual domain email alias maps</li> 305<li>virtual - virtual domain email alias maps</li>
357 </ul> 306</ul>
358 </p> 307</p>
359
360 <pre caption="alias table sample"> 308<pre caption="alias table sample" >
361 id alias destination 309id alias destination
362 1 root foo@bar.com 3101 root foo@bar.com
363 2 postmaster foo@bar.com 3112 postmaster foo@bar.com
364 </pre> 312</pre>
365
366 <pre caption="user table sample"> 313<pre caption="user table sample" >
367 id email clear name uid gid homedir maildir quota postfix 314<codenote>Line wrapped for clarity</codenote>
368 10 foo@virt-bar.org $password realname virtid virtid /home/vmail /home/vmail/virt-bar.org/foo/.maildir/ y 315id email clear name uid gid homedir \
369 13 foo@bar.com $password realname localid localid /home/foo /home/foo/.maildir/ y 316 maildir quota postfix
31710 foo@virt-bar.org $password realname virtid virtid /home/vmail \
318 /home/vmail/virt-bar.org/foo/.maildir/ y
31913 foo@bar.com $password realname localid localid /home/foo \
320 /home/foo/.maildir/ y
370 </pre> 321</pre>
371
372 <pre caption="transport table sample"> 322<pre caption="transport table sample" >
373 id domain destination 323id domain destination
374 1 bar.com local: 3241 bar.com local:
375 2 virt-bar.org virtual: 3252 virt-bar.org virtual:
376 </pre> 326</pre>
377
378 <pre caption="virtual table sample"> 327<pre caption="virtual table sample" >
379 id email destination 328id email destination
380 3 root@virt-bar.org other@email.address 3293 root@virt-bar.org other@email.address
381 </pre> 330</pre>
382 </body> 331</body>
383 332</section>
384</chapter> 333</chapter>
385
386<chapter> 334<chapter>
387<title>Apache and phpMyAdmin</title> 335<title>Apache and phpMyAdmin</title>
336<section>
388 <body> 337<body>
389 <p>Next we'll set up apache and add an interface to interact with the database more easily. </p> 338<p>Next we'll set up apache and add an interface to interact with the database more easily. </p>
390
391 <pre caption="Setting up apache and phpmyadmin"> 339<pre caption="Setting up apache and phpmyadmin" >
392 # <c>emerge apache php mod_php mod_ssl phpmyadmin</c> 340# <i>emerge apache mod_php phpmyadmin</i>
393 </pre> 341</pre>
394
395 <p>There are plenty of guides out there about how to set up apache with php. Like this one: <uri>http://www.linuxguruz.org/z.php?id=31</uri>. There are also numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve problems with the installation (search for 'apache php'). So, that said, I'm not going to cover it here. Set up the apache and php installs, then continue with this howto. Now, a word for the wise: .htaccess the directory that you put phpmyadmin in. If you do not do this, search engine spiders will come along and index the page which in turn will mean that anyone will be able to find your phpmyadmin page via google and in turn be able to come change your database however they want which is <e>BAD!</e> There are many howtos on this including: <uri>http://docs.csoft.net/micro/black-htaccess.html</uri>.</p> 342<p>There are plenty of guides out there about how to set up apache with php. Like this one: <uri>http://www.linuxguruz.org/z.php?id=31</uri>. There are also numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve problems with the installation (search for 'apache php'). So, that said, I'm not going to cover it here. Set up the apache and php installs, then continue with this howto. Now, a word for the wise: .htaccess the directory that you put phpmyadmin in. If you do not do this, search engine spiders will come along and index the page which in turn will mean that anyone will be able to find your phpmyadmin page via google and in turn be able to come change your database however they want which is <e>BAD!</e> There are many howtos on this including: <uri>http://www.csoft.net/docs/micro/htaccess.html.en</uri>.</p>
396
397 <p>Now we're going to install the Apache certificates we made previously. The Apache-SSL directives that you need to use the resulting cert are: 343<p>Now we're going to install the Apache certificates we made previously. The Apache-SSL directives that you need to use the resulting cert are:
398 <ul> 344 <ul>
399 <li>SSLCertificateFile /path/to/certs/new.cert.cert</li> 345<li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
400 <li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li> 346<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
401 </ul></p> 347</ul>
402 348</p>
403 <pre caption="Install Apache SSL certificates"> 349<pre caption="Install Apache SSL certificates" >
404 # <c>cp /usr/lib/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</c> 350# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i>
405 # <c>cp /usr/lib/ssl/misc/new.cert.key /etc/apache/conf/ssl/</c> 351# <i>cp /etc/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i>
406 # <c>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</c> 352# <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i>
407
408 <codenote>Change the following parameters</codenote> 353<codenote>Change the following parameters</codenote>
409 354
410 ServerName host.domain.name 355ServerName host.domain.name
411 ServerAdmin your@email.address 356ServerAdmin your@email.address
412 SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert 357SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert
413 SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key 358SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key
414 359
415 # <c>/etc/init.d/apache restart</c> 360# <i>/etc/init.d/apache restart</i>
416 </pre> 361</pre>
417
418 <note>If you have an existing apache install, you'll likely have to perform a full server reboot to install your new certificates. Check your logs to verify apache restarted successfully.</note> 362<note>If you have an existing apache install, you'll likely have to perform a full server reboot to install your new certificates. Check your logs to verify apache restarted successfully.</note>
419
420 <p>Next, configure phpMyAdmin.</p> 363<p>Next, configure phpMyAdmin.</p>
421
422 <pre caption="Configuring phpMyAdmin"> 364<pre caption="Configuring phpMyAdmin" >
423 # <c>nano -w /home/httpd/htdocs/phpmyadmin/config.inc.php</c> 365# <i>nano -w /var/www/localhost/htdocs/phpmyadmin/config.inc.php</i>
424
425 <codenote>Change the following parameters</codenote> 366<codenote>Change the following parameters</codenote>
426 367
427 $cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname 368$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
428 $cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings 369$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
429 // (this user must have read-only 370 // (this user must have read-only
430 $cfg['Servers'][$i]['controlpass'] = '$password'; // access to the "mysql/user" 371$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot;
431 // and "mysql/db" tables) 372 // and &quot;mysql/db&quot; tables)
432 $cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user 373$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
433 $cfg['Servers'][$i]['password'] = '$password'; // MySQL password 374$cfg['Servers'][$i]['password'] = '$password'; // MySQL password
434 </pre> 375</pre>
435
436 <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 "Welcome" mail to a new user after you setup their account to make sure the .maildir gets created. </p> 376<p>Now enter the phpmyadmin page and browse the tables. You'll want to add in your local aliases, edit your user table to add a test user, and change your transport table to add information about your domains. The default values supplied with the dumpfile should be a sufficient guide to what values need to go where. Make sure that if you put information in the database that it is accurate. For instance, make sure the local users home dir exists and that the correct uid/gid values are in place. The maildirs should be created automatically by postfix when the user receives their first email. So, in general, it's a good idea to send a &quot;Welcome&quot; mail to a new user after you setup their account to make sure the .maildir gets created. </p>
437 </body> 377</body>
378</section>
438</chapter> 379</chapter>
439
440<chapter> 380<chapter>
441<title>The vmail user</title> 381<title>The vmail user</title>
382<section>
442 <body> 383<body>
443 <p>At this point you may be wondering what user and directory to use for virtual mail users, and rightly so. Let's set that up.</p> 384<p>At this point you may be wondering what user and directory to use for virtual mail users, and rightly so. Let's set that up.</p>
444
445 <pre caption="Adding the vmail user"> 385<pre caption="Adding the vmail user" >
446 # <i>adduser -d /home/vmail -s /bin/false vmail</i> 386# <i>adduser -d /home/vmail -s /bin/false vmail</i>
447 # <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i> 387# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i>
448 # <i>groupadd -g $uid vmail</i> 388# <i>groupadd -g $uid vmail</i>
449 # <i>mkdir /home/vmail</i> 389# <i>mkdir /home/vmail</i>
450 # <i>chown vmail. /home/vmail</i> 390# <i>chown vmail. /home/vmail</i>
451 </pre> 391</pre>
452
453 <p>So now when you're setting up vmail accounts, use the vmail uid, gid, and homedir. When you're setting up local accounts, use that users uid, gid, and homedir. We've been meaning to create a php admin page for this setup but haven't gotten around to it yet, as phpmyadmin generally works fine for us.</p> 392<p>So now when you're setting up vmail accounts, use the vmail uid, gid, and homedir. When you're setting up local accounts, use that users uid, gid, and homedir. We've been meaning to create a php admin page for this setup but haven't gotten around to it yet, as phpmyadmin generally works fine for us.</p>
454 </body> 393</body>
394</section>
455</chapter> 395</chapter>
456
457<chapter> 396<chapter>
458<title>Configuring MySQL Authentication and vhosts</title> 397<title>Configuring MySQL Authentication and vhosts</title>
398<section>
459 <body> 399<body>
460
461 <p>Next we'll reconfigure our authentication to use the mailsql database in courier-imap and postfix. In all of the following examples, replace $password with the password you set for the mailsql mysql user.</p> 400<p>Next we'll reconfigure our authentication to use the mailsql database in courier-imap and postfix. In all of the following examples, replace $password with the password you set for the mailsql mysql user.</p>
462
463 <pre> 401<pre>
464 # <i>emerge /usr/portage/sys-libs/pam_mysql/pam_mysql-$currentversion.ebuild</i> 402# <i>emerge pam_mysql</i>
465
466 <codenote>This package is currently masked so you'll have to give it an explicit path </codenote>
467 <codenote>or unmask the package. This is subject to change when the package is unmasked</codenote>
468 <codenote>in the portage tree.</codenote>
469
470 # <c>nano -w /etc/pam.d/imap</c> 403# <i>nano -w /etc/pam.d/imap</i>
471
472 <codenote>Comment out the existing auth lines and add the following as shown.</codenote> 404<codenote>Comment out the existing auth lines and add the following as shown.</codenote>
473 405
474 #auth required pam_nologin.so 406#auth required pam_nologin.so
475 #auth required pam_stack.so service=system-auth 407#auth required pam_stack.so service=system-auth
476 #account required pam_stack.so service=system-auth 408#account required pam_stack.so service=system-auth
477 #session required pam_stack.so service=system-auth 409#session required pam_stack.so service=system-auth
478 410
479 auth optional pam_mysql.so server=localhost db=mailsql user=mailsql \ 411auth optional pam_mysql.so host=localhost db=mailsql user=mailsql \
480 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 412 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
481 account required pam_mysql.so server=localhost db=mailsql user=mailsql \ 413account required pam_mysql.so host=localhost db=mailsql user=mailsql \
482 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 414 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
483 415
484 # <c>nano -w /etc/pam.d/pop3</c> 416# <i>nano -w /etc/pam.d/pop3</i>
485 # <c>nano -w /etc/pam.d/smtp</c> 417# <i>nano -w /etc/pam.d/smtp</i>
486
487 <codenote>Make the same changes to the pop3 and smtp files</codenote> 418<codenote>Make the same changes to the pop3 and smtp files</codenote>
488 </pre> 419</pre>
489
490 <p>Next, we need to edit courier's authentication config's.</p> 420<p>Next, we need to edit courier's authentication config's.</p>
491
492 <pre> 421<pre>
493 # <c>nano -w /etc/courier-imap/authdaemonrc</c> 422# <i>nano -w /etc/courier-imap/authdaemonrc</i>
494 authmodulelist="authmysql authpam" 423authmodulelist=&quot;authmysql authpam&quot;
495 424
496 # <c>nano -w /etc/courier-imap/authdaemond.conf</c> 425# <i>nano -w /etc/courier-imap/authdaemond.conf</i>
497 AUTHDAEMOND="authdaemond.mysql" 426AUTHDAEMOND=&quot;authdaemond.mysql&quot;
498 427
499 # <c>nano -w /etc/courier-imap/authmysqlrc</c> 428# <i>nano -w /etc/courier-imap/authmysqlrc</i>
500 MYSQL_SERVER localhost 429MYSQL_SERVER localhost
501 MYSQL_USERNAME mailsql 430MYSQL_USERNAME mailsql
502 MYSQL_PASSWORD $password 431MYSQL_PASSWORD $password
503 MYSQL_DATABASE mailsql 432MYSQL_DATABASE mailsql
504 MYSQL_USER_TABLE users 433MYSQL_USER_TABLE users
505 #MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext) 434#MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext)
506 MYSQL_CLEAR_PWFIELD clear 435MYSQL_CLEAR_PWFIELD clear
507 MYSQL_UID_FIELD uid 436MYSQL_UID_FIELD uid
508 MYSQL_GID_FIELD gid 437MYSQL_GID_FIELD gid
509 MYSQL_LOGIN_FIELD email 438MYSQL_LOGIN_FIELD email
510 MYSQL_HOME_FIELD homedir 439MYSQL_HOME_FIELD homedir
511 MYSQL_NAME_FIELD name 440MYSQL_NAME_FIELD name
512 MYSQL_MAILDIR_FIELD maildir 441MYSQL_MAILDIR_FIELD maildir
513 442
514 # <i>/etc/init.d/authdaemond restart</i> 443# <i>/etc/init.d/authdaemond restart</i>
515 # <i>/etc/init.d/saslauthd restart</i> 444# <i>/etc/init.d/saslauthd restart</i>
516 </pre> 445</pre>
517
518 <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> 446<p>We're almost there I promise! Next, set up the rest of the necessary config's for postfix to interract with the database for all it's other transport needs.</p>
519
520 <pre caption="/etc/postfix/mysql-aliases.cf"> 447<pre caption="/etc/postfix/mysql-aliases.cf" >
521 # <c>nano -w /etc/postfix/mysql-aliases.cf</c> 448# <i>nano -w /etc/postfix/mysql-aliases.cf</i>
522 # mysql-aliases.cf 449# mysql-aliases.cf
523 450
524 user = mailsql 451user = mailsql
525 password = $password 452password = $password
526 dbname = mailsql 453dbname = mailsql
527 table = alias 454table = alias
528 select_field = destination 455select_field = destination
529 where_field = alias 456where_field = alias
530 hosts = 127.0.0.1 457hosts = unix:/var/run/mysqld/mysqld.sock
531 </pre> 458</pre>
532
533 <pre caption="/etc/postfix/mysql-relocated.cf"> 459<pre caption="/etc/postfix/mysql-relocated.cf" >
534 # <c>nano -w /etc/postfix/mysql-relocated.cf</c> 460# <i>nano -w /etc/postfix/mysql-relocated.cf</i>
535 # mysql-relocated.cf 461# mysql-relocated.cf
536 462
537 user = mailsql 463user = mailsql
538 password = $password 464password = $password
539 dbname = mailsql 465dbname = mailsql
540 table = relocated 466table = relocated
541 select_field = destination 467select_field = destination
542 where_field = email 468where_field = email
543 hosts = 127.0.0.1 469hosts = unix:/var/run/mysqld/mysqld.sock
544 </pre> 470</pre>
545
546 <pre caption="/etc/postfix/mysql-transport.cf"> 471<pre caption="/etc/postfix/mysql-transport.cf (optional)" >
547 # <c>nano -w /etc/postfix/mysql-transport.cf</c> 472# <i>nano -w /etc/postfix/mysql-transport.cf</i>
548 # mysql-transport.cf 473# mysql-transport.cf
549 474
550 user = mailsql 475user = mailsql
551 password = $password 476password = $password
552 dbname = mailsql 477dbname = mailsql
553 table = transport 478table = transport
554 select_field = destination 479select_field = destination
555 where_field = domain 480where_field = domain
556 hosts = 127.0.0.1 481hosts = unix:/var/run/mysqld/mysqld.sock
557 </pre> 482</pre>
558
559 <pre caption="/etc/postfix/mysql-virtual-gid.cf"> 483<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" >
560 # <c>nano -w /etc/postfix/mysql-virtual-gid.cf</c> 484# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>
561 #myql-virtual-gid.cf 485#myql-virtual-gid.cf
562 486
563 user = mailsql 487user = mailsql
564 password = $password 488password = $password
565 dbname = mailsql 489dbname = mailsql
566 table = users 490table = users
567 select_field = gid 491select_field = gid
568 where_field = email 492where_field = email
569 additional_conditions = and postfix = 'y' 493additional_conditions = and postfix = 'y'
570 hosts = 127.0.0.1 494hosts = unix:/var/run/mysqld/mysqld.sock
571 </pre> 495</pre>
572
573 <pre caption="/etc/postfix/mysql-virtual-maps.cf"> 496<pre caption="/etc/postfix/mysql-virtual-maps.cf" >
574 # <c>nano -w /etc/postfix/mysql-virtual-maps.cf</c> 497# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>
575 #myql-virtual-maps.cf 498#myql-virtual-maps.cf
576 499
577 user = mailsql 500user = mailsql
578 password = $password 501password = $password
579 dbname = mailsql 502dbname = mailsql
580 table = users 503table = users
581 select_field = maildir 504select_field = maildir
582 where_field = email 505where_field = email
583 additional_conditions = and postfix = 'y' 506additional_conditions = and postfix = 'y'
584 hosts = 127.0.0.1 507hosts = unix:/var/run/mysqld/mysqld.sock
585 </pre> 508</pre>
586
587 <pre caption="/etc/postfix/mysql-virtual-uid.cf"> 509<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" >
588 # <c>nano -w /etc/postfix/mysql-virtual-uid.cf</c> 510# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>
589 # mysql-virtual-uid.cf 511# mysql-virtual-uid.cf
590 512
591 user = mailsql 513user = mailsql
592 password = $password 514password = $password
593 dbname = mailsql 515dbname = mailsql
594 table = users 516table = users
595 select_field = uid 517select_field = uid
596 where_field = email 518where_field = email
597 additional_conditions = and postfix = 'y' 519additional_conditions = and postfix = 'y'
598 hosts = 127.0.0.1 520hosts = unix:/var/run/mysqld/mysqld.sock
599 </pre> 521</pre>
600
601 <pre caption="/etc/postfix/mysql-virtual.cf"> 522<pre caption="/etc/postfix/mysql-virtual.cf" >
602 # <c>nano -w /etc/postfix/mysql-virtual.cf</c> 523# <i>nano -w /etc/postfix/mysql-virtual.cf</i>
603 # mysql-virtual.cf 524# mysql-virtual.cf
604 525
605 user = mailsql 526user = mailsql
606 password = $password 527password = $password
607 dbname = mailsql 528dbname = mailsql
608 table = virtual 529table = virtual
609 select_field = destination 530select_field = destination
610 where_field = email 531where_field = email
611 hosts = 127.0.0.1 532hosts = unix:/var/run/mysqld/mysqld.sock
612 </pre> 533</pre>
613
614 <p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p> 534<p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p>
615
616 <pre caption="/etc/postfix/main.cf"> 535<pre caption="/etc/postfix/main.cf" >
617 # <c>nano -w /etc/postfix/main.cf</c> 536# <i>nano -w /etc/postfix/main.cf</i>
618 alias_maps = mysql:/etc/postfix/mysql-aliases.cf 537alias_maps = mysql:/etc/postfix/mysql-aliases.cf
619 relocated_maps = mysql:/etc/postfix/mysql-relocated.cf 538relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
620 transport_maps = mysql:/etc/postfix/mysql-transport.cf 539
621 virtual_gid_maps = mysql:/etc/postfix/mysql-virtual-gid.cf 540local_transport = local
541local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname
542
543virtual_transport = virtual
544virtual_mailbox_domains =
545 virt-bar.com,
546 $other-virtual-domain.com
547
548virtual_minimum_uid = 1000
549virtual_gid_maps = static:$vmail-gid
622 virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf 550virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf
623 virtual_maps = mysql:/etc/postfix/mysql-virtual.cf 551virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
624 virtual_uid_maps = mysql:/etc/postfix/mysql-virtual-uid.cf 552virtual_uid_maps = static:$vmail-uid
625 virtual_mailbox_base = / 553virtual_mailbox_base = /
554#virtual_mailbox_limit =
626 </pre> 555</pre>
627
628 <p>Shew! Alright now, let's restart postfix and see how all that went.</p>
629 556
557<p>
558For security reasons you should change the permissions of the various
559<path>/etc/mail/mysql-*.cf</path>:
560</p>
561
562<pre caption="Changing file permission">
563# <i>chmod 640 /etc/postfix/mysql-*.cf</i>
564# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>
565</pre>
566
567<p>As of Postfix 2.0.x, there were a number of significant changes over the 1.1.x release. Notably the transport, virtual-gid, and virtual-uid tables are no longer necessary. The tables are still included if you wish to use them.</p>
568<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note>
630 <pre># <c>postfix reload</c></pre> 569<pre># <i>postfix reload</i>
631 570</pre>
632 <p>Now, if all went well, you should have a functioning mailhost. Users should be able to authenticate against the sql database, using their full email address, for pop3, imap, and smtp. I would highly suggest that you verify that everything is working at this point. If you run into problems (with as many things as this setup has going on, it's likely that you will) check the troubleshooting section of this howto.</p> 571<p>Now, if all went well, you should have a functioning mailhost. Users should be able to authenticate against the sql database, using their full email address, for pop3, imap, and smtp. I would highly suggest that you verify that everything is working at this point. If you run into problems (with as many things as this setup has going on, it's likely that you will) check the troubleshooting section of this howto.</p>
633 </body> 572</body>
573</section>
634</chapter> 574</chapter>
635
636<chapter> 575<chapter>
637<title>Squirrelmail</title> 576<title>Squirrelmail</title>
577<section>
638 <body> 578<body>
639 <pre> 579<pre>
640 # <c>emerge squirrelmail</c> 580# <i>emerge squirrelmail</i>
641
642 <codenote>I like to add a link to the htdocs space for a shorter url.</codenote> 581<codenote>I like to add a link to the htdocs space for a shorter url.</codenote>
643 582
644 # <c>ln -s /home/httpd/htdocs/squirrelmail/ /home/httpd/htdocs/mail</c> 583# <i>ln -s /var/www/localhost/htdocs/squirrelmail/ /var/www/localhost/htdocs/mail</i>
645 # <c>cd /home/httpd/htdocs/mail/conf</c> 584# <i>cd /var/www/localhost/htdocs/mail/conf</i>
646 # <c>./conf.pl</c> 585# <i>./conf.pl</i>
647
648 <codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote> 586<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote>
649 <codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote> 587<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote>
650 <codenote>and use your new webmail setup.</codenote> 588<codenote>and use your new webmail setup.</codenote>
651 </pre> 589</pre>
652 </body> 590</body>
653 591</section>
654</chapter> 592</chapter>
655
656<chapter> 593<chapter>
657<title>Mailman</title> 594<title>Mailman</title>
595<section>
658 <body> 596<body>
659 <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.</p> 597<p>Last step: mailman. The new version of mailman has very nice virtual domain support, which is why I use it, not to mention it's really a great package. To get this package installed and working correctly for virtual domains is going to require a bit of hacking. I really recommend reading all of the mailman documentation, including README.POSTFIX.gz, to understand what's being done here.</p>
660 598<p>One further note, current versions of mailman install to /usr/local/mailman. If you're like me and wish to change the default install location, it can be overridden in the ebuild filoe by changing the INSTALLDIR variable.</p>
599<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
600# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i>
601MAILGID="280"
602<codenote>Set MAILGID to the mailman group instead of nobody</codenote>
603<codenote>This is needed for postfix integration</codenote>
604</pre>
661 <pre> 605<pre>
662 # <c>emerge mailman</c> 606# <i>emerge mailman</i>
663
664 <codenote>This package is currently masked as well, so you'll need to unmask it or give </codenote> 607<codenote>This package is currently masked as well, so you'll need to unmask it or give </codenote>
665 <codenote>emerge an explicit path to the ebuild. Once it's installed, follow the directions</codenote> 608<codenote>emerge an explicit path to the ebuild. Once it's installed, follow the directions</codenote>
666 <codenote>in the README.gentoo</codenote> 609<codenote>in the README.gentoo.gz *except* do not add your aliases to /etc/mail/aliases.</codenote>
610<codenote>We will instead be linking the entire alias db into postfix.</codenote>
667 611
668 # <c>nano -w /usr/share/doc/mailman-$ver/README.gentoo</c> 612# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i>
669 613</pre>
670 <codenote>Follow the rest of the install instructions in the README.</codenote> 614<pre caption="Setting defaults: Mailman/Defaults.py">
615# <i> nano -w /var/mailman/Mailman/Defaults.py</i>
616<codenote>Change the values below to reflect your primary domain, virtuals will be set next.</codenote>
617DEFAULT_EMAIL_HOST = 'domain.com'
618DEFAULT_URL_HOST = 'www.domain.com'
619</pre>
620<pre caption="mailman config: mm_cfg.py">
621# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i>
622MTA = "Postfix"
623POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']
624add_virtualhost('www.virt.domain.com', 'virt.domain.com')
625add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')
626<codenote>This is required for your virtual domains for mailman to function.</codenote>
627</pre>
628<pre>
671 <codenote>Once that's finished, add your first list.</codenote> 629<codenote>Once that's finished, add your first list.</codenote>
672 630
673 # <c>su mailman</c> 631# <i>su mailman</i>
674 # <c>cd ~</c> 632# <i>cd ~</i>
675 # <c>bin/newlist $listname</c> 633# <i>bin/newlist test</i>
676
677 Enter the email of the person running the list: your@email.address 634Enter the email of the person running the list: your@email.address
678 Initial test password: 635Initial test password:
679 Entry for aliases file:
680
681 ## test mailing list
682 ## created: 10-Jan-2003 root
683 $listname: "|/var/mailman/mail/wrapper post $listname"
684 $listname-admin: "|/var/mailman/mail/wrapper mailowner $listname"
685 $listname-request: "|/var/mailman/mail/wrapper mailcmd $listname"
686 $listname-owner: $listname-admin
687
688 Hit enter to continue with test owner notification... 636Hit enter to continue with test owner notification...
637<codenote>Virtual domain lists may be specified with</codenote>
638<codenote>list@domain.com style list names</codenote>
639# <i>bin/genaliases</i>
640<codenote>Now that your aliases have been generated,</codenote>
641<codenote>verify that they were added successfully.</codenote>
642
643# <i>nano -w data/aliases</i>
644# STANZA START: test
645# CREATED:
646test: "|/var/mailman/mail/mailman post test"
647test-admin: "|/var/mailman/mail/mailman admin test"
648test-bounces: "|/var/mailman/mail/mailman bounces test"
649test-confirm: "|/var/mailman/mail/mailman confirm test"
650test-join: "|/var/mailman/mail/mailman join test"
651test-leave: "|/var/mailman/mail/mailman leave test"
652test-owner: "|/var/mailman/mail/mailman owner test"
653test-request: "|/var/mailman/mail/mailman request test"
654test-subscribe: "|/var/mailman/mail/mailman subscribe test"
655test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test"
656# STANZA END: test
657
658# <i>/etc/init.d/mailman start</i>
659# <i>rc-update add mailman default</i>
660<codenote>To start mailman at once and on every reboot</codenote>
689 </pre> 661</pre>
690 662
691 <p>Add those aliases to the alias table in mailsql. You'll be tempted to add colons to the alias names in mailsql (because that's how the script gives them to you) DON'T DO IT! It won't work if you do. You should now be able to setup mailing lists for any domain on your box. When you log in to the mailman admin page for your new list, at the bottom of the general options page there is a space to declare what domain the list belongs to. With that selection you can add lists for any virtual domain you are hosting. 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> 663<pre caption="Adding mailman alias support to postfix">
664# <i>nano -w /etc/postfix/main.cf</i>
665owner_request_special = no
666recipient_delimiter = +
667<codenote>Read README.POSTFIX.gz for details on this</codenote>
668
669alias_maps =
670 hash:/var/mailman/data/aliases,
671 mysql:/etc/postfix/mysql-aliases.cf
672
673virtual_alias_maps =
674 hash:/var/mailman/data/virtual-mailman,
675 mysql:/etc/postfix/mysql-virtual.cf
676<codenote>This adds mailman alias file support to postfix</codenote>
677<codenote>You may of course use the mysql tables for this,</codenote>
678<codenote>but I hate doing that by hand. Also, if you are not</codenote>
679<codenote>using virtual domains, adding the virtual alias maps</codenote>
680<codenote>to postfix may cause problems, be warned.</codenote>
681</pre>
682<p> You should now be able to setup mailing lists for any domain on your box. Last note on this, make sure you run all mailman commands as the user mailman (<c>su mailman</c>) or else the permissions will be wrong and you'll have to fix them. Read the mailman doc's for more information on setting up and managing mailman lists.</p>
692 </body> 683</body>
684</section>
685</chapter>
693</chapter> 686<chapter>
694 687<title>Content Filtering and Anti-Virus</title>
688<section>
689<body><p>Coming soon...it would be done already but I need some perl help and testing to make it so. If you'd like to volunteer for that, please email me.</p></body>
690</section>
691</chapter>
695<chapter> 692<chapter>
696<title>Wrap Up</title> 693<title>Wrap Up</title>
694<section>
697 <body> 695<body>
698
699 <p>Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off verbose mode for production use. You'll probably also want to add the services to your startup routine to make sure everything comes back up on a reboot. Make sure to add all the services you're using - apache, mysql, saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all up to your decision on what access you want to provide. I generally have all the services enabled.</p> 696<p>Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off verbose mode for production use. You'll probably also want to add the services to your startup routine to make sure everything comes back up on a reboot. Make sure to add all the services you're using - apache, mysql, saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all up to your decision on what access you want to provide. I generally have all the services enabled.</p>
700
701 <pre caption="Wrap up"> 697<pre caption="Wrap up" >
702 # <c>postfix reload</c> 698# <i>postfix reload</i>
703 # <c>rc-update add $service default</c> 699# <i>rc-update add $service default</i>
704 </pre> 700</pre>
705 701<p>
706 <p><e>Have fun!</e></p> 702<e>Have fun!</e>
703</p>
707 </body> 704</body>
705</section>
708</chapter> 706</chapter>
709
710<chapter> 707<chapter>
711<title>Troubleshooting</title> 708<title>Troubleshooting</title>
712<section> 709<section>
713 <title>Introduction</title> 710<title>Introduction</title>
714 <body> 711<body>
715 <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> 712<p>Troubleshooting: This is a short troubleshooting guide for the set up we've detailed how to install here. It is not exhaustive, but meant as a place to get you started in figuring out problems. With a complicated setup such as this, it's imperative that you narrow down the problem to the particular component that is malfunctioning. In general I do that by following a few steps. Start from the base of the system and work your way up, ruling out components that work along the way until you discover which component is having the problem.</p>
716 </body> 713</body>
717</section>
718<section> 714</section>
715<section>
719 <title>Step 1: Check your config files.</title> 716<title>Step 1: Check your config files.</title>
720 <body> 717<body>
721 <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> 718<p>Typos are killers, especially when dealing with authentication systems. Scan your config's and mailsql database for typo's. You can debug all you want, but if you're not passing the right information back and forth to your mail system, it's not going to work. If you make a change to a config file for a service, make sure you restart that service so that the config change gets picked up.</p>
722
723 <pre> 719<pre>
724 # <c>/etc/init.d/service restart</c> 720# <i>/etc/init.d/service restart</i>
725 </pre> 721</pre>
726 </body> 722</body>
727</section>
728<section> 723</section>
729 724<section>
730 <title>Step 2: Are all the necessary services actually running?</title> 725<title>Step 2: Are all the necessary services actually running?</title>
731 <body> 726<body>
732 <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> 727<p>If it's not running, start it up. It's awful hard to debug a service that isn't running. Sometimes a service will act like it's started but still not function. Sometimes, when a bad config is used, or a bad transmission comes into a mail component, the service will hang and keep the port from being used by another process. Sometimes you can detect this with netstat. Or, if you've been at it awhile, just take a break and reboot your box in the meantime. That will clear out any hung services. Then you can come back fresh and try it again.</p>
733
734 <pre> 728<pre>
735 # <c>/etc/init.d/$service status</c> 729# <i>/etc/init.d/$service status</i>
736 # <c>netstat -a | grep $service (or $port)</c> 730# <i>netstat -a | grep $service (or $port)</i>
737 </pre> 731</pre>
738 </body> 732</body>
739</section>
740<section> 733</section>
734<section>
741 <title>Step 3: Are all the service using the current config's?</title> 735<title>Step 3: Are all the service using the current config's?</title>
742 <body> 736<body>
743
744 <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> 737<p>If you've recently made a change to a config file, restart that service to make sure it's using the current version. Some of the components will dump their current config's to you, like postfix.</p>
745
746 <pre> 738<pre>
747 # <c>apachectl fullstatus</c> (needs lynx installed) 739# <i>apachectl fullstatus</i> (needs lynx installed)
748 # <c>apachectl configtest</c> (checks config sanity) 740# <i>apachectl configtest</i> (checks config sanity)
749 # <c>postconf -n</c> (will tell you exactly what param's postfix is using) 741# <i>postconf -n</i> (will tell you exactly what param's postfix is using)
750 # <c>/etc/init.d/$service restart</c> 742# <i>/etc/init.d/$service restart</i>
751 </pre> 743</pre>
752 </body> 744</body>
753</section>
754<section> 745</section>
746<section>
755 <title>Step 4: Check the logs.</title> 747<title>Step 4: Check the logs.</title>
756 <body> 748<body>
757 <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> 749<p>Repeat after me, logs are my friend. My next troubleshooting stop is always the logs. Sometimes it's helpful to try a failed operation again then check the logs so that the error message is right at the bottom (or top depending on your logger) instead of buried in there somewhere. See if there is any information in your log that can help you diagnose the problem, or at the very least, figure out which component is having the problem.</p>
758
759 <pre> 750<pre>
760 # <c>kill -USR1 `ps -C metalog -o pid=`</c>(to turn off metalog buffering) 751# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)
761 # <c>nano -w /var/log/mail/current</c> 752# <i>nano -w /var/log/mail/current</i>
762 # <c>cat /var/log/mysql/mysql.log</c> 753# <i>cat /var/log/mysql/mysql.log</i>
763 # <c>tail /var/log/apache/error_log</c> 754# <i>tail /var/log/apache/error_log</i>
764 </pre> 755</pre>
756<p>You may also find the debug_peer parameters in main.cf helpful. Setting these will increase log output over just verbose mode.</p>
757<pre caption="adding debug_peer support">
758# <i>nano -w /etc/postfix/main.cf</i>
759debug_peer_level = 5
760debug_peer_list = $host.domain.name
761<codenote>Uncomment one of the suggested debugger</codenote>
762<codenote>commands as well.</codenote>
763</pre>
765 </body> 764</body>
766
767</section>
768<section> 765</section>
766<section>
769 <title>Step 5: Talk to the service itself.</title> 767<title>Step 5: Talk to the service itself.</title>
770 <body> 768<body>
771 <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> 769<p>SMTP, IMAP, and POP3 all respond to telnet sessions. As we've seen earlier when we verified postfix's config. Sometimes it's helpful to open a telnet session to the service itself and see what's happening.</p>
772
773 <pre> 770<pre>
774 # <c>telnet localhost $port</c> 771# <i>telnet localhost $port</i>
775
776 <codenote>SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,</codenote> 772<codenote>SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,</codenote>
777 <codenote>letting you know that the service is running and ready to respond to requests.</codenote> 773<codenote>letting you know that the service is running and ready to respond to requests.</codenote>
778 774
779 Trying 127.0.0.1... 775Trying 127.0.0.1...
780 Connected to localhost. 776Connected to localhost.
781 Escape character is '^]'. 777Escape character is '^]'.
782 * OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. See COPYING for distribution information. 778* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.
783 </pre> 779</pre>
784 </body> 780</body>
785</section>
786<section> 781</section>
782<section>
787 <title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title> 783<title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title>
788
789 <body> 784<body>
790 <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> 785<p>You should have this installed anyway. This is an invaluable tool for debugging software. You can start commands from the command line with strace and watch all the system calls as they happen. It often dumps a huge amount of information, so you'll either need to watch it realtime as you retry a failed transaction with the mail system, or dump the output to a file for review.</p>
791
792 <pre> 786<pre>
793 # <c>emerge strace</c> 787# <i>emerge strace</i>
794 # <c>strace $command</c> 788# <i>strace $command</i>
795 # <c>strace -p `ps -C $service -o pid=`</c> 789# <i>strace -p `ps -C $service -o pid=`</i>
796 </pre> 790</pre>
797 </body> 791</body>
798</section>
799<section> 792</section>
793<section>
800 <title>Step 7: Research</title> 794<title>Step 7: Research</title>
801 <body> 795<body>
802 <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> 796<p>Once you have the information, if you can diagnose and fix the problem, great! If not, you'll probably need to go digging on the net for information that will help you fix it. Here's a list of sites you can check to see if your error has already been resolved. There's also a really good howto on setting up smtp-auth which contains some great debugging ideas.</p>
803
804 <p> 797<p>
805 <ul> 798<ul>
799<li>
806 <li><uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users</li> 800<uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users</li>
801<li>
807 <li><uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place to look for specific errors</li> 802<uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place to look for specific errors</li>
803<li>
808 <li><uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto</li> 804<uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto</li>
805<li>
809 <li><uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing lists - searchable</li> 806<uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing lists - searchable</li>
807<li>
810 <li><uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - Courier-imap mailing list archives - not searchable</li> 808<uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - Courier-imap mailing list archives - not searchable</li>
809<li>
811 <li><uri>http://www.google.com/</uri> - If all else fails, there's always google, which has never failed me</li> 810<uri>http://www.google.com/</uri> - If all else fails, there's always google, which has never failed me</li>
812 <li>I also spend a lot of time on irc.freenode.net #gentoo. Irc is a great place to go for help.</li> 811<li>I also spend a lot of time on irc.freenode.net #gentoo. Irc is a great place to go for help.</li>
813 </ul> 812</ul>
814 </p> 813</p>
815
816 </body> 814</body>
817</section> 815</section>
818
819</chapter> 816</chapter>
820
821</guide> 817</guide>
822 818
823

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

  ViewVC Help
Powered by ViewVC 1.1.20