/[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.50 Revision 1.51
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.50 2006/04/09 07:42:45 fox2mike Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/virt-mail-howto.xml,v 1.51 2006/06/18 22:09:40 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/virt-mail-howto.xml"> 5<guide link="/doc/en/virt-mail-howto.xml">
6<title>Virtual Mailhosting System with Postfix Guide</title> 6<title>Virtual Mailhosting System with Postfix Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="antifa@gentoo.org">Ken Nowack</mail> 9 <mail link="antifa@gentoo.org">Ken Nowack</mail>
10</author> 10</author>
11<author title="Author"> 11<author title="Author">
12 <mail link="ezra@revoltltd.org">Ezra Gorman</mail> 12 <mail link="ezra@revoltltd.org">Ezra Gorman</mail>
13</author> 13</author>
14<author title="Editor"> 14<author title="Editor">
15 <mail link="klasikahl@gentoo.org">Zack Gilburd</mail> 15 <mail link="klasikahl@gentoo.org">Zack Gilburd</mail>
16</author> 16</author>
17<author title="Editor"> 17<author title="Editor">
18 <mail link="seather@scygro.za.net">Scygro</mail> 18 <mail link="seather@scygro.za.net">Scygro</mail>
19</author> 19</author>
20 20
21<abstract> 21<abstract>
22This document details how to create a virtual mailhosting system based upon 22This document details how to create a virtual mailhosting system based upon
23postfix, mysql, courier-imap, and cyrus-sasl. 23postfix, mysql, courier-imap, and cyrus-sasl.
24</abstract> 24</abstract>
25 25
26<version>1.0.27</version> 26<version>1.0.28</version>
27<date>2006-04-09</date> 27<date>2006-06-18</date>
28 28
29<!-- 29<!--
30Contents 30Contents
31 31
32I. Introduction 32I. Introduction
33II. Postfix Basics 33II. Postfix Basics
34III. Courier-imap 34III. Courier-imap
35IV. Cyrus-sasl 35IV. Cyrus-sasl
36V. SSL Certificates for Postfix and Apache 36V. SSL Certificates for Postfix and Apache
37VI. Adding SSL and SASL support to Postfix 37VI. Adding SSL and SASL support to Postfix
38VII. MySQL 38VII. MySQL
39VIII. Apache and phpMyAdmin 39VIII. Apache and phpMyAdmin
40IX. The vmail user 40IX. The vmail user
41X. Configuring MySQL Authentication and vhosts 41X. Configuring MySQL Authentication and vhosts
42XI. Squirrelmail 42XI. Squirrelmail
43XII. Mailman 43XII. Mailman
44XIII. Content Filtering and Anti-Virus 44XIII. Content Filtering and Anti-Virus
45XIV. Wrap Up 45XIV. Wrap Up
46XV. Troubleshooting 46XV. Troubleshooting
47--> 47-->
48 48
49<chapter> 49<chapter>
50<title>Introduction</title> 50<title>Introduction</title>
51<section> 51<section>
52<body> 52<body>
53 53
54<p> 54<p>
55For most gentoo users, a simple mail client and fetchmail will do. However, if 55For most Gentoo users, a simple mail client and fetchmail will do. However, if
56you're hosting a domain with your system, you'll need a full blown MTA (Mail 56you're hosting a domain with your system, you'll need a full blown MTA (Mail
57Transfer Agent). And if you're hosting multiple domains, then you'll definitely 57Transfer Agent). And if you're hosting multiple domains, then you'll definitely
58need something more robust to handle all of the email for your users. This 58need something more robust to handle all of the email for your users. This
59system was designed to be an elegant solution to that problem. 59system was designed to be an elegant solution to that problem.
60</p> 60</p>
61 61
62<p> 62<p>
63A virtual mail system needs to be able to handle email for numerous domains 63A virtual mail system needs to be able to handle email for numerous domains
64with multiple users over a variety of interfaces. This presents some issues 64with multiple users over a variety of interfaces. This presents some issues
65that must be dealt with. For instance, what if you have two users on different 65that must be dealt with. For instance, what if you have two users on different
66domains that want the same user name? If you are providing imap access and 66domains that want the same user name? If you are providing imap access and
67smtp-auth, how do combine the various authentication daemons into a single 67smtp-auth, how do combine the various authentication daemons into a single
68system? How do you provide security for the numerous components that comprise 68system? How do you provide security for the numerous components that comprise
69the system? How do you manage it all? 69the system? How do you manage it all?
70</p> 70</p>
110 110
111<impo> 111<impo>
112This document uses apache-1.3.x. Apache-2 has been marked stable in portage. 112This document uses apache-1.3.x. Apache-2 has been marked stable in portage.
113However there are still a number of issues with php integration. Until php 113However there are still a number of issues with php integration. Until php
114support in apache-2.0.x is marked stable, this guide will continue to use the 114support in apache-2.0.x is marked stable, this guide will continue to use the
1151.3.x version. 1151.3.x version.
116</impo> 116</impo>
117 117
118<impo> 118<impo>
119You need a domain name to run a public mail server, or at least an MX record 119You need a domain name to run a public mail server, or at least an MX record
120for a domain. Ideally you would have control of at least two domains to take 120for a domain. Ideally you would have control of at least two domains to take
121advantage of your new virtual domain functionality. 121advantage of your new virtual domain functionality.
122</impo> 122</impo>
123 123
124<impo> 124<impo>
125Make sure <path>/etc/hostname</path> is set to the right hostname for your mail 125Make sure <path>/etc/conf.d/hostname</path> is set to the right hostname for
126server. Verify your hostname is set correctly with <c>hostname</c>. Also 126your mail server. You can apply any changes you make to this file by running
127verify that there are no conflicting entries in <path>/etc/hosts</path>. 127<c>/etc/init.d/hostname restart</c>. Verify your hostname is set correctly with
128<c>hostname</c>. Also verify that there are no conflicting entries in
129<path>/etc/hosts</path>.
128</impo> 130</impo>
129 131
130<note> 132<note>
131It is recommended that you read this entire document and familiarize yourself 133It is recommended that you read this entire document and familiarize yourself
132with all the steps before attempting the install. If you run into problems with 134with all the steps before attempting the install. If you run into problems with
133any of the steps, check the troubleshooting guide at the end of this document. 135any of the steps, check the troubleshooting guide at the end of this document.
134Also, not all the referenced packages are necessary, this set up is very 136Also, not all the referenced packages are necessary, this set up is very
135flexible. For instance, if you do not desire a web interface, feel free to skip 137flexible. For instance, if you do not desire a web interface, feel free to skip
136the squirrelmail section. 138the squirrelmail section.
137</note> 139</note>
138 140
139</body> 141</body>
140</section> 142</section>
141</chapter> 143</chapter>
142 144

Legend:
Removed from v.1.50  
changed lines
  Added in v.1.51

  ViewVC Help
Powered by ViewVC 1.1.20