Virtual Users And Domains With Postfix, Courier, MySQL And SquirrelMail (Ubuntu 9.04) - Page 4
12 Test Postfix
To see if Postfix is ready for SMTP-AUTH and TLS, run
telnet localhost 25
After you have established the connection to your Postfix mail server type
If you see the lines
250-AUTH LOGIN PLAIN
everything is fine:
root@server1:/usr/local/sbin# telnet localhost 25
Connected to localhost.
Escape character is '^]'.
220 server1.example.com ESMTP Postfix (Ubuntu)
250-AUTH LOGIN PLAIN
221 2.0.0 Bye
Connection closed by foreign host.
to return to the system shell.
13 Populate The Database And Test
To populate the database you can use the MySQL shell:
mysql -u root -p
At least you have to create entries in the tables domains and users:
INSERT INTO `domains` (`domain`) VALUES ('example.com');
INSERT INTO `users` (`email`, `password`, `quota`) VALUES ('firstname.lastname@example.org', ENCRYPT('secret'), 10485760);
(Please take care that you use the ENCRYPT syntax in the second INSERT statement in order to encrypt the password!)
If you want to make entries in the other two tables, that would look like this:
INSERT INTO `forwardings` (`source`, `destination`) VALUES ('email@example.com', 'firstname.lastname@example.org');
INSERT INTO `transport` (`domain`, `transport`) VALUES ('example.com', 'smtp:mail.example.com');
To leave the MySQL shell, type
For most people it is easier if they have a graphical front-end to MySQL; therefore you can also use phpMyAdmin (in this example under http://192.168.0.100/phpmyadmin/ or http://server1.example.com/phpmyadmin/) to administrate the mail database. Again, when you create a user, go sure that you use the ENCRYPT function to encrypt the password:
I do not think I have to explain the domains and users table further.
The forwardings table can have entries like the following:
|email@example.comfirstname.lastname@example.org||Redirects emails for email@example.com to firstname.lastname@example.org|
|@email@example.com||Creates a Catch-All account for firstname.lastname@example.org. All emails to example.com will arrive at email@example.com, except those that exist in the users table (i.e., if firstname.lastname@example.org exists in the users table, mails to email@example.com will still arrive at firstname.lastname@example.org).|
|@email@example.com||This redirects all emails to example.com to the same user at anotherdomain.tld. E.g., emails to firstname.lastname@example.org will be forwarded to email@example.com.|
|firstname.lastname@example.orgemail@example.com, firstname.lastname@example.org||Forward emails for email@example.com to two or more email addresses. All listed email addresses under destination receive a copy of the email.|
The transport table can have entries like these:
|example.com||:||Delivers emails for example.com locally. This is as if this record would not exist in this table at all.|
|example.com||smtp:mail.anotherdomain.tld||Delivers all emails for example.com via smtp to the server mail.anotherdomain.com.|
|example.com||smtp:mail.anotherdomain.tld:2025||Delivers all emails for example.com via smtp to the server mail.anotherdomain.com, but on port 2025, not 25 which is the default port for smtp.|
|The square brackets prevent Postfix from doing lookups of the MX DNS record for the address in square brackets. Makes sense for IP addresses.|
|.example.com||smtp:mail.anotherdomain.tld||Mail for any subdomain of example.com is delivered to mail.anotherdomain.tld.|
|*||smtp:mail.anotherdomain.tld||All emails are delivered to mail.anotherdomain.tld.|
|firstname.lastname@example.org||smtp:mail.anotherdomain.tld||Emails for email@example.com are delivered to mail.anotherdomain.tld.|
for more details.
Please keep in mind that the order of entries in the transport table is important! The entries will be followed from the top to the bottom.
Important: Postfix uses a caching mechanism for the transports, therefore it might take a while until you changes in the transport table take effect. If you want them to take effect immediately, run
after you have made your changes in the transport table.
14 Send A Welcome Email For Creating Maildir
When you create a new email account and try to fetch emails from it (with POP3/IMAP) you will probably get error messages saying that the Maildir doesn't exist. The Maildir is created automatically when the first email arrives for the new account. Therefore it's a good idea to send a welcome email to a new account.
First, we install the mailx package:
aptitude install mailx
To send a welcome email to firstname.lastname@example.org, we do this:
You will be prompted for the subject. Type in the subject (e.g. Welcome), then press ENTER, and in the next line type your message. When the message is finished, press ENTER again so that you are in a new line, then press CTRL+D; if you don't want to cc the mail, press ENTER again:
root@server1:/usr/local/sbin# mailx email@example.com
Subject: Welcome <-- ENTER
Welcome! Have fun with your new mail account. <-- ENTER
Cc: <-- ENTER