/[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.15
7</author> 7</author>
8<author title="Author" > 8<author title="Author" >
9<mail link="ezra@revoltltd.org" >Ezra Gorman</mail> 9<mail link="ezra@revoltltd.org" >Ezra Gorman</mail>
10</author> 10</author>
11<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract> 11<abstract>This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl. </abstract>
12<version>1.0</version> 12<version>1.0.2</version>
13<date>30 April 2003</date> 13<date>7 Aug 2003</date>
14<!-- 14<!--
15 15
16Contents 16Contents
17 17
18I. Introduction 18I. Introduction
41<p>The following packages are used in this setup: 41<p>The following packages are used in this setup:
42 42
43 apache, courier-imap, pam_mysql, postfix, mod_php, mod_ssl, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman.</p> 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> 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> 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>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>
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>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<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<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</body>
50</chapter> 51</chapter>
54<pre caption="Install postfix" ># <i>emerge postfix</i> 55<pre caption="Install postfix" ># <i>emerge postfix</i>
55</pre> 56</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<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<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<pre caption="/etc/postfix/main.cf" >
59 myhostname = $host.domain.name 60myhostname = $host.domain.name
60 mydomain = $domain.name 61mydomain = $domain.name
61 inet_interfaces = all 62inet_interfaces = all
62 mydestination = $myhostname, localhost.$mydomain $mydomain 63mydestination = $myhostname, localhost.$mydomain $mydomain
63 mynetworks = my.ip.net.work/24, 127.0.0.0/8 64mynetworks = my.ip.net.work/24, 127.0.0.0/8
64 home_mailbox = .maildir/ 65home_mailbox = .maildir/
65 local_destination_concurrency_limit = 2 66local_destination_concurrency_limit = 2
66 default_destination_concurrency_limit = 10 </pre> 67default_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<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<pre caption="/etc/postfix/master.cf" >
69 # service type private unpriv chroot wakeup maxproc command + args 70# service type private unpriv chroot wakeup maxproc command + args
70 # (yes) (yes) (yes) (never) (50) 71# (yes) (yes) (yes) (never) (50)
71 # 72#
72 ========================================================================== 73==========================================================================
73 smtp inet n - n - - smtpd -v 74smtp inet n - n - - smtpd -v
74 75
75 <codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote> 76<codenote>Just add the <c>-v</c> after the smtpd in the above line</codenote>
76</pre> 77</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<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<pre caption="Starting postfix for the first time" >
79 # <i>/usr/bin/newaliases</i> 80# <i>/usr/bin/newaliases</i>
80<codenote>This will install the new aliases. You only need to do this </codenote> 81<codenote>This will install the new aliases. You only need to do this </codenote>
81<codenote>when you update or install aliases.</codenote> 82<codenote>when you update or install aliases.</codenote>
82 83
83 # <i>/etc/init.d/postfix start</i> 84# <i>/etc/init.d/postfix start</i>
84</pre> 85</pre>
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> 86<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>
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> 87<note>I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto. </note>
87</body> 88</body>
88</chapter> 89</chapter>
90<title>Courier-imap</title> 91<title>Courier-imap</title>
91<body> 92<body>
92<pre caption="Install courier-imap" ># <i>emerge courier-imap</i> 93<pre caption="Install courier-imap" ># <i>emerge courier-imap</i>
93</pre> 94</pre>
94<pre caption="Courier-imap configuration" > 95<pre caption="Courier-imap configuration" >
95 # <i>cd /etc/courier-imap</i> 96# <i>cd /etc/courier-imap</i>
96<codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote> 97<codenote>If you want to use the ssl capabilities of courier-imap or pop3, </codenote>
97<codenote>you'll need to create certs for this purpose.</codenote> 98<codenote>you'll need to create certs for this purpose.</codenote>
98<codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote> 99<codenote>This step is recommended. If you do not want to use ssl, skip this step.</codenote>
99 100
100 # <i>nano -w pop3d.cnf</i> 101# <i>nano -w pop3d.cnf</i>
101 # <i>nano -w imapd.cnf</i> 102# <i>nano -w imapd.cnf</i>
102<codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote> 103<codenote>Change the C, ST, L, CN, and email parameters to match your server.</codenote>
103 104
104 # <i>mkpop3dcert</i> 105# <i>mkpop3dcert</i>
105 # <i>mkimapdcert</i> 106# <i>mkimapdcert</i>
106</pre> 107</pre>
107<pre caption="Start the courier services you need." > 108<pre caption="Start the courier services you need." >
108 # <i>/etc/init.d/courier-imapd start</i> 109# <i>/etc/init.d/courier-imapd start</i>
109 # <i>/etc/init.d/courier-imapd-ssl start</i> 110# <i>/etc/init.d/courier-imapd-ssl start</i>
110 # <i>/etc/init.d/courier-pop3d start</i> 111# <i>/etc/init.d/courier-pop3d start</i>
111 # <i>/etc/init.d/courier-pop3d-ssl start</i> 112# <i>/etc/init.d/courier-pop3d-ssl start</i>
112</pre> 113</pre>
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> 114<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>
114</body> 115</body>
115</chapter> 116</chapter>
116<chapter> 117<chapter>
117<title>Cyrus-sasl</title> 118<title>Cyrus-sasl</title>
118<body> 119<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> 120<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>
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> 121<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>
121<pre caption="Configuring and installing the cyrus-sasl ebuild" > 122<pre caption="Configuring and installing the cyrus-sasl ebuild" >
122 # <i>USE='-ldap -mysql' emerge cyrus-sasl</i> 123# <i>USE='-ldap -mysql' emerge cyrus-sasl</i>
123<codenote>We don't have ldap and we're not using sasl's mysql capabilities </codenote> 124<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<codenote>so we need to turn them off for this build.</codenote>
125</pre> 126</pre>
126<p>Next, edit <path>/var/lib/sasl2/smtp.conf</path>.</p> 127<p>Next, edit <path>/usr/lib/sasl2/smtp.conf</path>.</p>
127<pre caption="Starting sasl" > 128<pre caption="Starting sasl" >
128 # <i>nano -w /var/lib/sasl2/smtp.conf</i> 129# <i>nano -w /usr/lib/sasl2/smtp.conf</i>
129 pwcheck_method: saslauthd 130pwcheck_method: saslauthd
130 mech_list: LOGIN PLAIN 131mech_list: LOGIN PLAIN
131<codenote>It's important to turn off auth mehtods we are not using.</codenote> 132<codenote>It's important to turn off auth mehtods we are not using.</codenote>
132<codenote>They cause problems for some mail clients.</codenote> 133<codenote>They cause problems for some mail clients.</codenote>
133 # <i>/etc/init.d/saslauthd start</i> 134# <i>/etc/init.d/saslauthd start</i>
134</pre> 135</pre>
135</body> 136</body>
136</chapter> 137</chapter>
137<chapter> 138<chapter>
138<title>SSL Certs for Postfix and Apache</title> 139<title>SSL Certs for Postfix and Apache</title>
139<body> 140<body>
140<p>Next we're going to make a set of ssl certificates for postfix and apache.</p> 141<p>Next we're going to make a set of ssl certificates for postfix and apache.</p>
141<pre> 142<pre>
142 # <i>cd /etc/ssl/</i> 143# <i>cd /etc/ssl/</i>
143 # <i>nano -w openssl.cnf</i> 144# <i>nano -w openssl.cnf</i>
145
144<codenote>Change the following default values for your domain:</codenote> 146<codenote>Change the following default values for your domain:</codenote>
145
146 countryName_default 147countryName_default
147 stateOrProvinceName_default 148stateOrProvinceName_default
148 localityName_default 149localityName_default
149 0.organizationName_default 1500.organizationName_default
150 commonName_default 151commonName_default
151 emailAddress_default. 152emailAddress_default.
152 153
153 <codenote>If the variables are not already present, just add them in a sensible place.</codenote> 154<codenote>If the variables are not already present, just add them in a sensible place.</codenote>
154 155
155 156
156 # <i>cd misc</i> 157# <i>cd misc</i>
157 # <i>nano -w CA.pl</i> 158# <i>nano -w CA.pl</i>
158<codenote>We need to add -nodes to the # create a certificate and</codenote> 159<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>#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>certs be loaded without a password. Otherwise when you</codenote>
161<codenote>reboot your ssl certs will not be available.</codenote> 162<codenote>reboot your ssl certs will not be available.</codenote>
163
164# create a certificate
165system (&quot;$REQ -new -nodes -x509 -keyout newreq.pem -out newreq.pem $DAYS&quot;);
166
167# create a certificate request
168system (&quot;$REQ -new -nodes -keyout newreq.pem -out newreq.pem $DAYS&quot;);
162 169
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> 170# <i>./CA.pl -newca</i>
170 # <i>./CA.pl -newreq</i> 171# <i>./CA.pl -newreq</i>
171 # <i>./CA.pl -sign</i> 172# <i>./CA.pl -sign</i>
172 # <i>cp newcert.pem /etc/postfix</i> 173# <i>cp newcert.pem /etc/postfix</i>
173 # <i>cp newreq.pem /etc/postfix</i> 174# <i>cp newreq.pem /etc/postfix</i>
174 # <i>cp demoCA/cacert.pem /etc/postfix</i> 175# <i>cp demoCA/cacert.pem /etc/postfix</i>
175<codenote>Now we do the same thing for apache</codenote> 176<codenote>Now we do the same thing for apache</codenote>
176 177
177
178 # <i>openssl req -new > new.cert.csr</i> 178# <i>openssl req -new > new.cert.csr</i>
179 # <i>openssl rsa -in privkey.pem -out new.cert.key</i> 179# <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> 180# <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> 181<codenote>Just leave the resulting certificates here for now.</codenote>
182<codenote>We'll install them after Apache is installed.</codenote> 182<codenote>We'll install them after Apache is installed.</codenote>
183</pre> 183</pre>
184</body> 184</body>
185</chapter> 185</chapter>
186<chapter> 186<chapter>
187<title>Adding SSL and SASL support to Postfix</title> 187<title>Adding SSL and SASL support to Postfix</title>
188<body> 188<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> 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>
190<pre caption="/etc/postfix/main.cf" > 190<pre caption="/etc/postfix/main.cf" >
191 # <i>nano -w /etc/postfix/main.cf</i> 191# <i>nano -w /etc/postfix/main.cf</i>
192 192
193 smtpd_sasl_auth_enable = yes 193smtpd_sasl_auth_enable = yes
194 smtpd_sasl2_auth_enable = yes 194smtpd_sasl2_auth_enable = yes
195 smtpd_sasl_security_options = noanonymous 195smtpd_sasl_security_options = noanonymous
196 broken_sasl_auth_clients = yes 196broken_sasl_auth_clients = yes
197 smtpd_sasl_local_domain = 197smtpd_sasl_local_domain =
198 198
199 <codenote>The broken_sasl_auth_clients option and the login auth method </codenote> 199<codenote>The broken_sasl_auth_clients option and the login auth method </codenote>
200<codenote>are for outlook and outlook express only and are undocumented.</codenote> 200<codenote>are for outlook and outlook express only and are undocumented.</codenote>
201<codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote> 201<codenote>Isn't having to hack software for stupid, broken, M$ BS great?</codenote>
202<codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote> 202<codenote>smtpd_sasl_local_domain appends a domain name to clients using</codenote>
203<codenote>smtp-auth. Make sure it's blank or your user names will get</codenote> 203<codenote>smtp-auth. Make sure it's blank or your user names will get</codenote>
204<codenote>mangled by postfix and be unable to auth.</codenote> 204<codenote>mangled by postfix and be unable to auth.</codenote>
205 205
206 smtpd_recipient_restrictions = 206smtpd_recipient_restrictions =
207 permit_sasl_authenticated, 207 permit_sasl_authenticated,
208 permit_mynetworks, 208 permit_mynetworks,
209 reject_unauth_destination 209 reject_unauth_destination
210 210
211 211
212 smtpd_use_tls = yes 212smtpd_use_tls = yes
213 #smtpd_tls_auth_only = yes 213#smtpd_tls_auth_only = yes
214 smtpd_tls_key_file = /etc/postfix/newreq.pem 214smtpd_tls_key_file = /etc/postfix/newreq.pem
215 smtpd_tls_cert_file = /etc/postfix/newcert.pem 215smtpd_tls_cert_file = /etc/postfix/newcert.pem
216 smtpd_tls_CAfile = /etc/postfix/cacert.pem 216smtpd_tls_CAfile = /etc/postfix/cacert.pem
217 smtpd_tls_loglevel = 3 217smtpd_tls_loglevel = 3
218 smtpd_tls_received_header = yes 218smtpd_tls_received_header = yes
219 smtpd_tls_session_cache_timeout = 3600s 219smtpd_tls_session_cache_timeout = 3600s
220 tls_random_source = dev:/dev/urandom 220tls_random_source = dev:/dev/urandom
221 221
222 <codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote> 222<codenote>smtpd_tls_auth_only is commented out to ease testing the system. </codenote>
223<codenote>You can turn this on later if you desire.</codenote> 223<codenote>You can turn this on later if you desire.</codenote>
224 224
225 # <i>postfix reload</i> 225# <i>postfix reload</i>
226</pre> 226</pre>
227<p>Now we're going to verify that the config's we added were picked up by postfix.</p> 227<p>Now we're going to verify that the config's we added were picked up by postfix.</p>
228<pre caption="Verifying sasl and tls support" > 228<pre caption="Verifying sasl and tls support" >
229 # <i>telnet localhost 25</i> 229# <i>telnet localhost 25</i>
230 230
231 Trying 127.0.0.1... 231Trying 127.0.0.1...
232 Connected to localhost. 232Connected to localhost.
233 Escape character is '^]'. 233Escape character is '^]'.
234 220 mail.domain.com ESMTP Postfix 234220 mail.domain.com ESMTP Postfix
235 <i>EHLO domain.com</i> 235<i>EHLO domain.com</i>
236 250-mail.domain.com 236250-mail.domain.com
237 250-PIPELINING 237250-PIPELINING
238 250-SIZE 10240000 238250-SIZE 10240000
239 250-VRFY 239250-VRFY
240 250-ETRN 240250-ETRN
241 250-STARTTLS 241250-STARTTLS
242 250-AUTH LOGIN PLAIN 242250-AUTH LOGIN PLAIN
243 250-AUTH=LOGIN PLAIN 243250-AUTH=LOGIN PLAIN
244 250-XVERP 244250-XVERP
245 250 8BITMIME 245250 8BITMIME
246 <i>^]</i> 246<i>^]</i>
247 telnet> <i>quit</i> 247telnet> <i>quit</i>
248</pre> 248</pre>
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. 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.
250 </p> 250 </p>
251</body> 251</body>
252</chapter> 252</chapter>
253<chapter> 253<chapter>
254<title>MySQL</title> 254<title>MySQL</title>
255<body> 255<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> 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>
257<pre caption="Installing and configuring MySQL" > 257<pre caption="Installing and configuring MySQL" >
258 # <i>emerge mysql</i> 258# <i>emerge mysql</i>
259 259
260 # <i>/usr/sbin/mysql_install_db</i> 260# <i>/usr/bin/mysql_install_db</i>
261<codenote>After this command runs follow the onscreen directions</codenote> 261<codenote>After this command runs follow the onscreen directions</codenote>
262<codenote>for adding a root password with mysql,</codenote> 262<codenote>for adding a root password with mysql,</codenote>
263<codenote>not mysqladmin, otherwise your db will be wide open.</codenote> 263<codenote>not mysqladmin, otherwise your db will be wide open.</codenote>
264 264
265 # <i>/etc/init.d/mysql start</i> 265# <i>/etc/init.d/mysql start</i>
266 # <i>mysqladmin -u root -p create mailsql</i> 266# <i>mysqladmin -u root -p create mailsql</i>
267 # <i>mysql -u root -p --opt mailsql &lt; genericmailsql.sql</i> 267# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>
268 268
269 # <i>mysql -u root -p mysql</i> 269# <i>mysql -u root -p mysql</i>
270 mysql> <i>GRANT SELECT,INSERT,UPDATE,DELETE</i> 270mysql> <i>GRANT SELECT,INSERT,UPDATE,DELETE</i>
271 -> <i>ON mailsql.*</i> 271 -> <i>ON mailsql.*</i>
272 -> <i>TO mailsql@localhost</i> 272 -> <i>TO mailsql@localhost</i>
273 -> <i>IDENTIFIED BY '$password';</i> 273 -> <i>IDENTIFIED BY '$password';</i>
274 274
275 -> <i>quit</i> 275 -> <i>quit</i>
276<codenote>Verify that the new mailsql user can connect to the mysql server.</codenote> 276<codenote>Verify that the new mailsql user can connect to the mysql server.</codenote>
277 277
278 # <i>mysql -u mailsql -p mailsql</i> 278# <i>mysql -u mailsql -p mailsql</i>
279</pre> 279</pre>
280<p>Your new database has default values and tables set up for two domains. The following tables are included: 280<p>Your new database has default values and tables set up for two domains. The following tables are included:
281 <ul> 281 <ul>
282<li>alias - local email alias and mailman alias information.</li> 282<li>alias - local email alias and mailman alias information.</li>
283<li>relocated - relocated user email address maps</li> 283<li>relocated - relocated user email address maps</li>
285<li>users - all user account information</li> 285<li>users - all user account information</li>
286<li>virtual - virtual domain email alias maps</li> 286<li>virtual - virtual domain email alias maps</li>
287</ul> 287</ul>
288</p> 288</p>
289<pre caption="alias table sample" > 289<pre caption="alias table sample" >
290 id alias destination 290id alias destination
291 1 root foo@bar.com 2911 root foo@bar.com
292 2 postmaster foo@bar.com 2922 postmaster foo@bar.com
293 </pre> 293</pre>
294<pre caption="user table sample" > 294<pre caption="user table sample" >
295 id email clear name uid gid homedir maildir quota postfix 295<codenote>Line wrapped for clarity</codenote>
296 10 foo@virt-bar.org $password realname virtid virtid /home/vmail /home/vmail/virt-bar.org/foo/.maildir/ y 296id email clear name uid gid homedir \
297 13 foo@bar.com $password realname localid localid /home/foo /home/foo/.maildir/ y 297 maildir quota postfix
29810 foo@virt-bar.org $password realname virtid virtid /home/vmail \
299 /home/vmail/virt-bar.org/foo/.maildir/ y
30013 foo@bar.com $password realname localid localid /home/foo \
301 /home/foo/.maildir/ y
298 </pre> 302</pre>
299<pre caption="transport table sample" > 303<pre caption="transport table sample" >
300 id domain destination 304id domain destination
301 1 bar.com local: 3051 bar.com local:
302 2 virt-bar.org virtual: 3062 virt-bar.org virtual:
303 </pre> 307</pre>
304<pre caption="virtual table sample" > 308<pre caption="virtual table sample" >
305 id email destination 309id email destination
306 3 root@virt-bar.org other@email.address 3103 root@virt-bar.org other@email.address
307 </pre> 311</pre>
308</body> 312</body>
309</chapter> 313</chapter>
310<chapter> 314<chapter>
311<title>Apache and phpMyAdmin</title> 315<title>Apache and phpMyAdmin</title>
312<body> 316<body>
313<p>Next we'll set up apache and add an interface to interact with the database more easily. </p> 317<p>Next we'll set up apache and add an interface to interact with the database more easily. </p>
314<pre caption="Setting up apache and phpmyadmin" > 318<pre caption="Setting up apache and phpmyadmin" >
315 # <i>emerge apache mod_php mod_ssl phpmyadmin</i> 319# <i>emerge apache mod_php mod_ssl phpmyadmin</i>
316</pre> 320</pre>
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> 321<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>
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: 322<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:
319 <ul> 323 <ul>
320<li>SSLCertificateFile /path/to/certs/new.cert.cert</li> 324<li>SSLCertificateFile /path/to/certs/new.cert.cert</li>
321<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li> 325<li>SSLCertificateKeyFile /path/to/certs/new.cert.key</li>
322</ul> 326</ul>
323</p> 327</p>
324<pre caption="Install Apache SSL certificates" > 328<pre caption="Install Apache SSL certificates" >
325 # <i>cp /usr/lib/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i> 329# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache/conf/ssl/</i>
326 # <i>cp /usr/lib/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i> 330# <i>cp /etc/ssl/misc/new.cert.key /etc/apache/conf/ssl/</i>
327 # <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i> 331# <i>nano -w /etc/apache/conf/vhosts/ssl.default-vhost.conf</i>
328<codenote>Change the following parameters</codenote> 332<codenote>Change the following parameters</codenote>
329 333
330 ServerName host.domain.name 334ServerName host.domain.name
331 ServerAdmin your@email.address 335ServerAdmin your@email.address
332 SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert 336SSLCertificateFile /etc/apache/conf/ssl/new.cert.cert
333 SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key 337SSLCertificateKeyFile /etc/apache/conf/ssl/new.cert.key
334 338
335 # <i>/etc/init.d/apache restart</i> 339# <i>/etc/init.d/apache restart</i>
336</pre> 340</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> 341<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>
338<p>Next, configure phpMyAdmin.</p> 342<p>Next, configure phpMyAdmin.</p>
339<pre caption="Configuring phpMyAdmin" > 343<pre caption="Configuring phpMyAdmin" >
340 # <i>nano -w /home/httpd/htdocs/phpmyadmin/config.inc.php</i> 344# <i>nano -w /home/httpd/htdocs/phpmyadmin/config.inc.php</i>
341<codenote>Change the following parameters</codenote> 345<codenote>Change the following parameters</codenote>
342 346
343 $cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname 347$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
344 $cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings 348$cfg['Servers'][$i]['controluser'] = 'mailsql'; // MySQL control user settings
345 // (this user must have read-only 349 // (this user must have read-only
346 $cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot; 350$cfg['Servers'][$i]['controlpass'] = '$password'; // access to the &quot;mysql/user&quot;
347 // and &quot;mysql/db&quot; tables) 351 // and &quot;mysql/db&quot; tables)
348 $cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user 352$cfg['Servers'][$i]['user'] = 'mailsql'; // MySQL user
349 $cfg['Servers'][$i]['password'] = '$password'; // MySQL password 353$cfg['Servers'][$i]['password'] = '$password'; // MySQL password
350 </pre> 354</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> 355<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>
352</body> 356</body>
353</chapter> 357</chapter>
354<chapter> 358<chapter>
355<title>The vmail user</title> 359<title>The vmail user</title>
356<body> 360<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> 361<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>
358<pre caption="Adding the vmail user" > 362<pre caption="Adding the vmail user" >
359 # <i>adduser -d /home/vmail -s /bin/false vmail</i> 363# <i>adduser -d /home/vmail -s /bin/false vmail</i>
360 # <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i> 364# <i>uid=`cat /etc/passwd | grep vmail | cut -f 3 -d :`</i>
361 # <i>groupadd -g $uid vmail</i> 365# <i>groupadd -g $uid vmail</i>
362 # <i>mkdir /home/vmail</i> 366# <i>mkdir /home/vmail</i>
363 # <i>chown vmail. /home/vmail</i> 367# <i>chown vmail. /home/vmail</i>
364</pre> 368</pre>
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> 369<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>
366</body> 370</body>
367</chapter> 371</chapter>
368<chapter> 372<chapter>
369<title>Configuring MySQL Authentication and vhosts</title> 373<title>Configuring MySQL Authentication and vhosts</title>
370<body> 374<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> 375<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>
372<pre> 376<pre>
373 # <i>emerge /usr/portage/sys-libs/pam_mysql/pam_mysql-$currentversion.ebuild</i> 377# <i>emerge /usr/portage/sys-libs/pam_mysql/pam_mysql-$currentversion.ebuild</i>
374<codenote>This package is currently masked so you'll have to give it an explicit path </codenote> 378<codenote>This package is currently masked so you'll have to give it an explicit path </codenote>
375<codenote>or unmask the package. This is subject to change when the package is unmasked</codenote> 379<codenote>or unmask the package. This is subject to change when the package is unmasked</codenote>
376<codenote>in the portage tree.</codenote> 380<codenote>in the portage tree.</codenote>
377 381
378 # <i>nano -w /etc/pam.d/imap</i> 382# <i>nano -w /etc/pam.d/imap</i>
379<codenote>Comment out the existing auth lines and add the following as shown.</codenote> 383<codenote>Comment out the existing auth lines and add the following as shown.</codenote>
380 384
381 #auth required pam_nologin.so 385#auth required pam_nologin.so
382 #auth required pam_stack.so service=system-auth 386#auth required pam_stack.so service=system-auth
383 #account required pam_stack.so service=system-auth 387#account required pam_stack.so service=system-auth
384 #session required pam_stack.so service=system-auth 388#session required pam_stack.so service=system-auth
385 389
386 auth optional pam_mysql.so server=localhost db=mailsql user=mailsql \ 390auth optional pam_mysql.so server=localhost db=mailsql user=mailsql \
387 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 391 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
388 account required pam_mysql.so server=localhost db=mailsql user=mailsql \ 392account required pam_mysql.so server=localhost db=mailsql user=mailsql \
389 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0 393 passwd=$password table=users usercolumn=email passwdcolumn=clear crypt=0
390 394
391 # <i>nano -w /etc/pam.d/pop3</i> 395# <i>nano -w /etc/pam.d/pop3</i>
392 # <i>nano -w /etc/pam.d/smtp</i> 396# <i>nano -w /etc/pam.d/smtp</i>
393<codenote>Make the same changes to the pop3 and smtp files</codenote> 397<codenote>Make the same changes to the pop3 and smtp files</codenote>
394</pre> 398</pre>
395<p>Next, we need to edit courier's authentication config's.</p> 399<p>Next, we need to edit courier's authentication config's.</p>
396<pre> 400<pre>
397 # <i>nano -w /etc/courier-imap/authdaemonrc</i> 401# <i>nano -w /etc/courier-imap/authdaemonrc</i>
398 authmodulelist=&quot;authmysql authpam&quot; 402authmodulelist=&quot;authmysql authpam&quot;
399 403
400 # <i>nano -w /etc/courier-imap/authdaemond.conf</i> 404# <i>nano -w /etc/courier-imap/authdaemond.conf</i>
401 AUTHDAEMOND=&quot;authdaemond.mysql&quot; 405AUTHDAEMOND=&quot;authdaemond.mysql&quot;
402 406
403 # <i>nano -w /etc/courier-imap/authmysqlrc</i> 407# <i>nano -w /etc/courier-imap/authmysqlrc</i>
404 MYSQL_SERVER localhost 408MYSQL_SERVER localhost
405 MYSQL_USERNAME mailsql 409MYSQL_USERNAME mailsql
406 MYSQL_PASSWORD $password 410MYSQL_PASSWORD $password
407 MYSQL_DATABASE mailsql 411MYSQL_DATABASE mailsql
408 MYSQL_USER_TABLE users 412MYSQL_USER_TABLE users
409 #MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext) 413#MYSQL_CRYPT_PWFIELD crypt (make sure this is commented out since we're storing plaintext)
410 MYSQL_CLEAR_PWFIELD clear 414MYSQL_CLEAR_PWFIELD clear
411 MYSQL_UID_FIELD uid 415MYSQL_UID_FIELD uid
412 MYSQL_GID_FIELD gid 416MYSQL_GID_FIELD gid
413 MYSQL_LOGIN_FIELD email 417MYSQL_LOGIN_FIELD email
414 MYSQL_HOME_FIELD homedir 418MYSQL_HOME_FIELD homedir
415 MYSQL_NAME_FIELD name 419MYSQL_NAME_FIELD name
416 MYSQL_MAILDIR_FIELD maildir 420MYSQL_MAILDIR_FIELD maildir
417 421
418 # <i>/etc/init.d/authdaemond restart</i> 422# <i>/etc/init.d/authdaemond restart</i>
419 # <i>/etc/init.d/saslauthd restart</i> 423# <i>/etc/init.d/saslauthd restart</i>
420</pre> 424</pre>
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> 425<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>
422<pre caption="/etc/postfix/mysql-aliases.cf" > 426<pre caption="/etc/postfix/mysql-aliases.cf" >
423 # <i>nano -w /etc/postfix/mysql-aliases.cf</i> 427# <i>nano -w /etc/postfix/mysql-aliases.cf</i>
424 # mysql-aliases.cf 428# mysql-aliases.cf
425 429
426 user = mailsql 430user = mailsql
427 password = $password 431password = $password
428 dbname = mailsql 432dbname = mailsql
429 table = alias 433table = alias
430 select_field = destination 434select_field = destination
431 where_field = alias 435where_field = alias
432 hosts = unix:/var/run/mysqld/mysqld.sock 436hosts = unix:/var/run/mysqld/mysqld.sock
433 </pre> 437</pre>
434<pre caption="/etc/postfix/mysql-relocated.cf" > 438<pre caption="/etc/postfix/mysql-relocated.cf" >
435 # <i>nano -w /etc/postfix/mysql-relocated.cf</i> 439# <i>nano -w /etc/postfix/mysql-relocated.cf</i>
436 # mysql-relocated.cf 440# mysql-relocated.cf
437 441
438 user = mailsql 442user = mailsql
439 password = $password 443password = $password
440 dbname = mailsql 444dbname = mailsql
441 table = relocated 445table = relocated
442 select_field = destination 446select_field = destination
443 where_field = email 447where_field = email
444 hosts = unix:/var/run/mysqld/mysqld.sock 448hosts = unix:/var/run/mysqld/mysqld.sock
445 </pre> 449</pre>
446<pre caption="/etc/postfix/mysql-transport.cf (optional)" > 450<pre caption="/etc/postfix/mysql-transport.cf (optional)" >
447 # <i>nano -w /etc/postfix/mysql-transport.cf</i> 451# <i>nano -w /etc/postfix/mysql-transport.cf</i>
448 # mysql-transport.cf 452# mysql-transport.cf
449 453
450 user = mailsql 454user = mailsql
451 password = $password 455password = $password
452 dbname = mailsql 456dbname = mailsql
453 table = transport 457table = transport
454 select_field = destination 458select_field = destination
455 where_field = domain 459where_field = domain
456 hosts = unix:/var/run/mysqld/mysqld.sock 460hosts = unix:/var/run/mysqld/mysqld.sock
457 </pre> 461</pre>
458<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" > 462<pre caption="/etc/postfix/mysql-virtual-gid.cf (optional)" >
459 # <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i> 463# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>
460 #myql-virtual-gid.cf 464#myql-virtual-gid.cf
461 465
462 user = mailsql 466user = mailsql
463 password = $password 467password = $password
464 dbname = mailsql 468dbname = mailsql
465 table = users 469table = users
466 select_field = gid 470select_field = gid
467 where_field = email 471where_field = email
468 additional_conditions = and postfix = 'y' 472additional_conditions = and postfix = 'y'
469 hosts = unix:/var/run/mysqld/mysqld.sock 473hosts = unix:/var/run/mysqld/mysqld.sock
470 </pre> 474</pre>
471<pre caption="/etc/postfix/mysql-virtual-maps.cf" > 475<pre caption="/etc/postfix/mysql-virtual-maps.cf" >
472 # <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i> 476# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>
473 #myql-virtual-maps.cf 477#myql-virtual-maps.cf
474 478
475 user = mailsql 479user = mailsql
476 password = $password 480password = $password
477 dbname = mailsql 481dbname = mailsql
478 table = users 482table = users
479 select_field = maildir 483select_field = maildir
480 where_field = email 484where_field = email
481 additional_conditions = and postfix = 'y' 485additional_conditions = and postfix = 'y'
482 hosts = unix:/var/run/mysqld/mysqld.sock 486hosts = unix:/var/run/mysqld/mysqld.sock
483 </pre> 487</pre>
484<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" > 488<pre caption="/etc/postfix/mysql-virtual-uid.cf (optional)" >
485 # <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i> 489# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>
486 # mysql-virtual-uid.cf 490# mysql-virtual-uid.cf
487 491
488 user = mailsql 492user = mailsql
489 password = $password 493password = $password
490 dbname = mailsql 494dbname = mailsql
491 table = users 495table = users
492 select_field = uid 496select_field = uid
493 where_field = email 497where_field = email
494 additional_conditions = and postfix = 'y' 498additional_conditions = and postfix = 'y'
495 hosts = unix:/var/run/mysqld/mysqld.sock 499hosts = unix:/var/run/mysqld/mysqld.sock
496 </pre> 500</pre>
497<pre caption="/etc/postfix/mysql-virtual.cf" > 501<pre caption="/etc/postfix/mysql-virtual.cf" >
498 # <i>nano -w /etc/postfix/mysql-virtual.cf</i> 502# <i>nano -w /etc/postfix/mysql-virtual.cf</i>
499 # mysql-virtual.cf 503# mysql-virtual.cf
500 504
501 user = mailsql 505user = mailsql
502 password = $password 506password = $password
503 dbname = mailsql 507dbname = mailsql
504 table = virtual 508table = virtual
505 select_field = destination 509select_field = destination
506 where_field = email 510where_field = email
507 hosts = unix:/var/run/mysqld/mysqld.sock 511hosts = unix:/var/run/mysqld/mysqld.sock
508 </pre> 512</pre>
509<p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p> 513<p>Lastly, edit <path>/etc/postfix/main.cf</path> one more time.</p>
510<pre caption="/etc/postfix/main.cf" > 514<pre caption="/etc/postfix/main.cf" >
511 # <i>nano -w /etc/postfix/main.cf</i> 515# <i>nano -w /etc/postfix/main.cf</i>
512 alias_maps = mysql:/etc/postfix/mysql-aliases.cf 516alias_maps = mysql:/etc/postfix/mysql-aliases.cf
513 relocated_maps = mysql:/etc/postfix/mysql-relocated.cf 517relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
514 518
515 local_transport = local 519local_transport = local
516 local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname 520local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname
517 521
518 virtual_transport = virtual 522virtual_transport = virtual
519 virtual_mailbox_domains = 523virtual_mailbox_domains =
520 virt-bar.com, 524 virt-bar.com,
521 $other-virtual-domain.com 525 $other-virtual-domain.com
522 526
523 virtual_minimum_uid = 1000 527virtual_minimum_uid = 1000
524 virtual_gid_maps = static:$vmail-gid 528virtual_gid_maps = static:$vmail-gid
525 virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf 529virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf
526 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf 530virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
527 virtual_uid_maps = static:$vmail-uid 531virtual_uid_maps = static:$vmail-uid
528 virtual_mailbox_base = / 532virtual_mailbox_base = /
529 #virtual_mailbox_limit = 533#virtual_mailbox_limit =
530 </pre> 534</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> 535<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>
532<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note> 536<note>It is recommended tha you read VIRTUAL_README included with the postfix doc's for more information.</note>
533<pre># <i>postfix reload</i> 537<pre># <i>postfix reload</i>
534</pre> 538</pre>
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> 539<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>
537</chapter> 541</chapter>
538<chapter> 542<chapter>
539<title>Squirrelmail</title> 543<title>Squirrelmail</title>
540<body> 544<body>
541<pre> 545<pre>
542 # <i>emerge squirrelmail</i> 546# <i>emerge squirrelmail</i>
543<codenote>I like to add a link to the htdocs space for a shorter url.</codenote> 547<codenote>I like to add a link to the htdocs space for a shorter url.</codenote>
544 548
545 # <i>ln -s /home/httpd/htdocs/squirrelmail/ /home/httpd/htdocs/mail</i> 549# <i>ln -s /home/httpd/htdocs/squirrelmail/ /home/httpd/htdocs/mail</i>
546 # <i>cd /home/httpd/htdocs/mail/conf</i> 550# <i>cd /home/httpd/htdocs/mail/conf</i>
547 # <i>./conf.pl</i> 551# <i>./conf.pl</i>
548<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote> 552<codenote>Change your Organization, Server, and Folder settings for squirrelmail.</codenote>
549<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote> 553<codenote>Now you should be able to login to squirrelmail, again - with your full email address,</codenote>
550<codenote>and use your new webmail setup.</codenote> 554<codenote>and use your new webmail setup.</codenote>
551</pre> 555</pre>
552</body> 556</body>
553</chapter> 557</chapter>
554<chapter> 558<chapter>
555<title>Mailman</title> 559<title>Mailman</title>
556<body> 560<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> 561<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>
562<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>
558<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild"> 563<pre caption="/usr/portage/net-mail/mailman/mailman-$ver.ebuild">
559 # <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i> 564# <i>nano -w /usr/portage/net-mail/mailman/mailman-$ver.ebuild</i>
560 MAILGID="280" 565MAILGID="280"
561 <codenote>Set MAILGID to the mailman group instead of nobody</codenote> 566<codenote>Set MAILGID to the mailman group instead of nobody</codenote>
562 <codenote>This is needed for postfix integration</codenote> 567<codenote>This is needed for postfix integration</codenote>
563</pre>
564<pre> 568</pre>
569<pre>
565 # <i>emerge mailman</i> 570# <i>emerge mailman</i>
566<codenote>This package is currently masked as well, so you'll need to unmask it or give </codenote> 571<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> 572<codenote>emerge an explicit path to the ebuild. Once it's installed, follow the directions</codenote>
568<codenote>in the README.gentoo.gz</codenote> 573<codenote>in the README.gentoo.gz *except* do not add your aliases to /etc/mail/aliases.</codenote>
574<codenote>We will instead be linking the entire alias db into postfix.</codenote>
569 575
570 # <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i> 576# <i>zless /usr/share/doc/mailman-$ver/README.gentoo.gz</i>
577</pre>
578<pre caption="Setting defaults: Mailman/Defaults.py">
579# <i> nano -w /var/mailman/Mailman/Defaults.py</i>
580<codenote>Change the values below to reflect your primary domain, virtuals will be set next.</codenote>
581DEFAULT_EMAIL_HOST = 'domain.com'
582DEFAULT_URL_HOST = 'www.domain.com'
571</pre> 583</pre>
572<pre caption="mailman config: mm_cfg.py"> 584<pre caption="mailman config: mm_cfg.py">
573 # <i>nano -w /var/mailman/Mailman/mm_cfg.py</i> 585# <i>nano -w /var/mailman/Mailman/mm_cfg.py</i>
574 MTA = "Postfix" 586MTA = "Postfix"
575 POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com'] 587POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']
576 add_virtualhost('www.virt.domain.com', 'virt.domain.com') 588add_virtualhost('www.virt.domain.com', 'virt.domain.com')
577 add_virtualhost('www.virt.domain2.com', 'virt.domain2.com') 589add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')
578<codenote>This is required for your virtual domains for mailman to function.</codenote> 590<codenote>This is required for your virtual domains for mailman to function.</codenote>
579</pre> 591</pre>
580<pre> 592<pre>
581<codenote>Once that's finished, add your first list.</codenote> 593<codenote>Once that's finished, add your first list.</codenote>
582 594
583 # <i>su mailman</i> 595# <i>su mailman</i>
584 # <i>cd ~</i> 596# <i>cd ~</i>
585 # <i>bin/newlist test</i> 597# <i>bin/newlist test</i>
586 Enter the email of the person running the list: your@email.address 598Enter the email of the person running the list: your@email.address
587 Initial test password: 599Initial test password:
588 Hit enter to continue with test owner notification... 600Hit enter to continue with test owner notification...
589 <codenote>Virtual domain lists may be specified with</codenote> 601<codenote>Virtual domain lists may be specified with</codenote>
590 <codenote>list@domain.com style list names</codenote> 602<codenote>list@domain.com style list names</codenote>
591 # <i>bin/genaliases</i> 603# <i>bin/genaliases</i>
592 <codenote>Now that your aliases have been generated,</codenote> 604<codenote>Now that your aliases have been generated,</codenote>
593 <codenote>verify that they were added successfully.</codenote> 605<codenote>verify that they were added successfully.</codenote>
594 606
595 # <i>nano -w data/aliases</i> 607# <i>nano -w data/aliases</i>
596 # STANZA START: test 608# STANZA START: test
597 # CREATED: 609# CREATED:
598 test: "|/var/mailman/mail/mailman post test" 610test: "|/var/mailman/mail/mailman post test"
599 test-admin: "|/var/mailman/mail/mailman admin test" 611test-admin: "|/var/mailman/mail/mailman admin test"
600 test-bounces: "|/var/mailman/mail/mailman bounces test" 612test-bounces: "|/var/mailman/mail/mailman bounces test"
601 test-confirm: "|/var/mailman/mail/mailman confirm test" 613test-confirm: "|/var/mailman/mail/mailman confirm test"
602 test-join: "|/var/mailman/mail/mailman join test" 614test-join: "|/var/mailman/mail/mailman join test"
603 test-leave: "|/var/mailman/mail/mailman leave test" 615test-leave: "|/var/mailman/mail/mailman leave test"
604 test-owner: "|/var/mailman/mail/mailman owner test" 616test-owner: "|/var/mailman/mail/mailman owner test"
605 test-request: "|/var/mailman/mail/mailman request test" 617test-request: "|/var/mailman/mail/mailman request test"
606 test-subscribe: "|/var/mailman/mail/mailman subscribe test" 618test-subscribe: "|/var/mailman/mail/mailman subscribe test"
607 test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test" 619test-unsubscribe: "|/var/mailman/mail/mailman unsubscribe test"
608 # STANZA END: test 620# STANZA END: test
609 621
610 # <i>/etc/init.d/mailman start</i> 622# <i>/etc/init.d/mailman start</i>
611 # <i>rc-update add mailman default</i> 623# <i>rc-update add mailman default</i>
612 <codenote>To start mailman at once and on every reboot</codenote> 624<codenote>To start mailman at once and on every reboot</codenote>
613</pre> 625</pre>
614 626
615<pre caption="Adding mailman alias support to postfix"> 627<pre caption="Adding mailman alias support to postfix">
616 # <i>nano -w /etc/postfix/main.cf</i> 628# <i>nano -w /etc/postfix/main.cf</i>
617 owner_request_special = no 629owner_request_special = no
618 recipient_delimiter = + 630recipient_delimiter = +
619 <codenote>Read README.POSTFIX.gz for details on this</codenote> 631<codenote>Read README.POSTFIX.gz for details on this</codenote>
620 632
621 alias_maps = 633alias_maps =
622 hash:/var/mailman/data/aliases, 634 hash:/var/mailman/data/aliases,
623 mysql:/etc/postfix/mysql-aliases.cf 635 mysql:/etc/postfix/mysql-aliases.cf
624 636
625 virtual_alias_maps = 637virtual_alias_maps =
626 hash:/var/mailman/data/virtual-mailman, 638 hash:/var/mailman/data/virtual-mailman,
627 mysql:/etc/postfix/mysql-virtual.cf 639 mysql:/etc/postfix/mysql-virtual.cf
628 <codenote>This adds mailman alias file support to postfix</codenote> 640<codenote>This adds mailman alias file support to postfix</codenote>
629 <codenote>You may of course use the mysql tables for this,</codenote> 641<codenote>You may of course use the mysql tables for this,</codenote>
630 <codenote>but I hate doing that by hand.</codenote> 642<codenote>but I hate doing that by hand. Also, if you are not</codenote>
643<codenote>using virtual domains, adding the virtual alias maps</codenote>
644<codenote>to postfix may cause problems, be warned.</codenote>
631</pre> 645</pre>
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> 646<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>
633</body> 647</body>
634</chapter> 648</chapter>
635<chapter> 649<chapter>
639<chapter> 653<chapter>
640<title>Wrap Up</title> 654<title>Wrap Up</title>
641<body> 655<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> 656<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>
643<pre caption="Wrap up" > 657<pre caption="Wrap up" >
644 # <i>postfix reload</i> 658# <i>postfix reload</i>
645 # <i>rc-update add $service default</i> 659# <i>rc-update add $service default</i>
646</pre> 660</pre>
647<p> 661<p>
648<e>Have fun!</e> 662<e>Have fun!</e>
649</p> 663</p>
650</body> 664</body>
660<section> 674<section>
661<title>Step 1: Check your config files.</title> 675<title>Step 1: Check your config files.</title>
662<body> 676<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> 677<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>
664<pre> 678<pre>
665 # <i>/etc/init.d/service restart</i> 679# <i>/etc/init.d/service restart</i>
666</pre> 680</pre>
667</body> 681</body>
668</section> 682</section>
669<section> 683<section>
670<title>Step 2: Are all the necessary services actually running?</title> 684<title>Step 2: Are all the necessary services actually running?</title>
671<body> 685<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> 686<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>
673<pre> 687<pre>
674 # <i>/etc/init.d/$service status</i> 688# <i>/etc/init.d/$service status</i>
675 # <i>netstat -a | grep $service (or $port)</i> 689# <i>netstat -a | grep $service (or $port)</i>
676</pre> 690</pre>
677</body> 691</body>
678</section> 692</section>
679<section> 693<section>
680<title>Step 3: Are all the service using the current config's?</title> 694<title>Step 3: Are all the service using the current config's?</title>
681<body> 695<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> 696<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>
683<pre> 697<pre>
684 # <i>apachectl fullstatus</i> (needs lynx installed) 698# <i>apachectl fullstatus</i> (needs lynx installed)
685 # <i>apachectl configtest</i> (checks config sanity) 699# <i>apachectl configtest</i> (checks config sanity)
686 # <i>postconf -n</i> (will tell you exactly what param's postfix is using) 700# <i>postconf -n</i> (will tell you exactly what param's postfix is using)
687 # <i>/etc/init.d/$service restart</i> 701# <i>/etc/init.d/$service restart</i>
688</pre> 702</pre>
689</body> 703</body>
690</section> 704</section>
691<section> 705<section>
692<title>Step 4: Check the logs.</title> 706<title>Step 4: Check the logs.</title>
693<body> 707<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> 708<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>
695<pre> 709<pre>
696 # <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering) 710# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)
697 # <i>nano -w /var/log/mail/current</i> 711# <i>nano -w /var/log/mail/current</i>
698 # <i>cat /var/log/mysql/mysql.log</i> 712# <i>cat /var/log/mysql/mysql.log</i>
699 # <i>tail /var/log/apache/error_log</i> 713# <i>tail /var/log/apache/error_log</i>
700</pre> 714</pre>
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> 715<p>You may also find the debug_peer parameters in main.cf helpful. Setting these will increase log output over just verbose mode.</p>
702<pre caption="adding debug_peer support"> 716<pre caption="adding debug_peer support">
703 # <i>nano -w /etc/postfix/main.cf</i> 717# <i>nano -w /etc/postfix/main.cf</i>
704 debug_peer_level = 5 718debug_peer_level = 5
705 debug_peer_list = $host.domain.name 719debug_peer_list = $host.domain.name
706 <codenote>Uncomment one of the suggested debugger</codenote> 720<codenote>Uncomment one of the suggested debugger</codenote>
707 <codenote>commands as well.</codenote> 721<codenote>commands as well.</codenote>
708</pre> 722</pre>
709</body> 723</body>
710</section> 724</section>
711<section> 725<section>
712<title>Step 5: Talk to the service itself.</title> 726<title>Step 5: Talk to the service itself.</title>
713<body> 727<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> 728<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>
715<pre> 729<pre>
716 # <i>telnet localhost $port</i> 730# <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> 731<codenote>SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,</codenote>
718<codenote>letting you know that the service is running and ready to respond to requests.</codenote> 732<codenote>letting you know that the service is running and ready to respond to requests.</codenote>
719 733
720 Trying 127.0.0.1... 734Trying 127.0.0.1...
721 Connected to localhost. 735Connected to localhost.
722 Escape character is '^]'. 736Escape character is '^]'.
723 * OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. See COPYING for distribution information. 737* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.
724 </pre> 738</pre>
725</body> 739</body>
726</section> 740</section>
727<section> 741<section>
728<title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title> 742<title>Step 6: Sometimes only the big guns will give you the information you need: strace.</title>
729<body> 743<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> 744<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>
731<pre> 745<pre>
732 # <i>emerge strace</i> 746# <i>emerge strace</i>
733 # <i>strace $command</i> 747# <i>strace $command</i>
734 # <i>strace -p `ps -C $service -o pid=`</i> 748# <i>strace -p `ps -C $service -o pid=`</i>
735</pre> 749</pre>
736</body> 750</body>
737</section> 751</section>
738<section> 752<section>
739<title>Step 7: Research</title> 753<title>Step 7: Research</title>

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

  ViewVC Help
Powered by ViewVC 1.1.20