E-mail server section: Difference between revisions
(Started MySQL config) |
m (yes) |
||
Line 7: | Line 7: | ||
* can have multiple aliases per mailbox | * can have multiple aliases per mailbox | ||
* can forward mail for certain aliases to multiple mailboxes | * can forward mail for certain aliases to multiple mailboxes | ||
For this type of mail server setup, we owe a great thankyou to [http://workaround.org/articles/ispmail-etch/ Christoph Haas] | For this type of mail server setup, we owe a great thankyou to [http://workaround.org/articles/ispmail-etch/ Christoph Haas], whose advise has helped us create flexible and reliable mail servers since 2003. | ||
==Preparation== | ==Preparation== | ||
Line 50: | Line 50: | ||
mysql -u root -p < create.vmail.sql | mysql -u root -p < create.vmail.sql | ||
(This of course assumes you have ''create.vmail.sql'' in your current working directory; if not you can include the path to the file.) Simply give the MySQL root user password, and the script creates the database, the user, and the necessary tables. | (This of course assumes you have ''create.vmail.sql'' in your current working directory; if not you can include the path to the file.) Simply give the MySQL root user password, and the script creates the database, the user, and the necessary tables. | ||
We're not going to fill the database tables just yet, but we ''are'' going to tell Postfix to use the ''vmail'' database, and also ''how'' to read the database. To this end, we're going to create | |||
==Postfix configuration== | ==Postfix configuration== |
Revision as of 02:15, 31 October 2008
E-mail server setup
What we want to accomplish here is the setup of a mail server with the following properties:
- can serve multiple mail domains
- can relay mail for other domains to other mail servers
- can have one or more mailboxes per domain
- users of these mailboxes can be virtual (do not need to have a Linux user account)
- can have multiple aliases per mailbox
- can forward mail for certain aliases to multiple mailboxes
For this type of mail server setup, we owe a great thankyou to Christoph Haas, whose advise has helped us create flexible and reliable mail servers since 2003.
Preparation
We'll assume that the server currently has no mailserver installed, at least no other than the default exim mailserver. Furthermore, the server is already fitted with MySQL, and this database is running without problems.
The hostname of the server must be set correctly, so that hostname -f returns a valid DNS name, like lighthouse.saruman.biz.. It might also be an internal name like lighthouse.saruman.lan. but that will require us to give extra attention to the name under which Postfix will contact its collegues on the Internet. Also, the server can correctly [Networking_section#DNS_resolution_under_Debian | resolve DNS names] like www.debian.org, preferably by running it's own caching DNS server.
The server is kept on the correct date and time using NTP, TCP port 25 is open on the server, the ISP will allow connections from Internet to this port, and if there's a firewall running on this server, then it has port 25 open so as to not block incoming e-mail.
Software installation
As a first step, we use apt or aptitude to make sure that our server is up-to-date. Then we can install the necessary software packages. Under Debian 5.0 "Lenny", the (single) packages is:
- postfix, the mail server itself - this includes the "virtual package" postfix-tls, that we want to use to secure connections to Postfix with the TLS protocol
At the same time we can - and must - purge the following packages:
- exim4
- exim4-base
- exim4-daemon-light
- exim4-config
In aptitude, only press "go" when you've marked all four of these packages "purge", or you cannot install postfix.
When installing the postfix package, the Debian installer script will ask you several questions, which you can answer like this:
- General type of mail configuration: Internet site
- System mail name: the FQDN of the mail server that you've verified in the previous section. Note that the script will try to guess the DNS name, but that might yield a DNS name with a trailing dot. That is technically correct, but the installation script will barf. Remove the trailing dot before hitting <enter>!
- Postmaster mail address: the address that all mail should go to that is addressed to "root" and "postmaster".
- Domain list: give the list of all domains that the machine can consider itself the FINAL destination for. This should at a minimum include an empty value, "localhost" and the FQDN of the machine itself (no trailing dots!); however, if you're running your own mail domain, you can also add that (e.g. "saruman.biz"). Thus, the list could look like this:
saruman.biz, lighthouse.saruman.lan, localhost.saruman.lan, , localhost
- Force synchronous updates? We think that's not necessary, but please read the question and decide for yourself
- Local networks: something like 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 192.168.67.0/24 (the default, augmented with your local IP range)
- Mailbox size limits: you can give postfix a limit in bytes, but we're going to use one single big mailbox for all users, so we cannot let Postfix guard it. Leave it at 0 (zero) so we don't have a size limit.
- Character for local address extension: we leave it at +
- Internet protocols to use: currently we don't have IPv6 support, so there's no sense in letting Postfix try to serve IPv6. We choose ipv4 only.
With the above data, the Debian install script for Postfix can do its job and configure Postfix with some basic settings.
Now that Postfix is installed, we can install some dependent packages (we could install them in the same run, but if anything goes amiss with the postfix installation, then these packages are going to remain unconfigured as well):
- postfix-doc, the accompanying documentation;
- postfix-mysql, necessary to have Postfix talk to our MySQL server;
- postfix-pcre to be able to parse regular expressions, which which we can combat spam;
- dovecot-imapd is a daemon that will provide your users with IMAP access to their mail;
- dovecot-pop3d is another daemon, but for the POP3 protocol.
MySQL configuration
We will use the MySQL database to record data on our mail system, and then give our Postfix access to this database so that it can read its configuration from there. For starters, we'll create a MySQL database named "vmail", and a MySQL user named "vmail_admin" that can read all necessary data from that "vmail" database. Then, we create the necessary tables. We do this with the MySQL client mysql. However, we're quite lazy, so we don't create this database by hand, but by use of a script create.vmail.sql. To this end, feed the create.vmail.sql script into the mysql client like this:
mysql -u root -p < create.vmail.sql
(This of course assumes you have create.vmail.sql in your current working directory; if not you can include the path to the file.) Simply give the MySQL root user password, and the script creates the database, the user, and the necessary tables.
We're not going to fill the database tables just yet, but we are going to tell Postfix to use the vmail database, and also how to read the database. To this end, we're going to create