Virtual Users And Domains With Postfix, Courier, MySQL And SquirrelMail (Ubuntu 12.10)

Version 1.0
Author: Falko Timme
Follow me on Twitter
Last edited 11/04/2012

This tutorial is Copyright (c) 2012 by Falko Timme. It is derived from a tutorial from Christoph Haas which you can find at You are free to use this tutorial under the Creative Commons license 2.5 or any later version.

This document describes how to install a Postfix mail server that is based on virtual users and domains, i.e. users and domains that are in a MySQL database. I'll also demonstrate the installation and configuration of Courier (Courier-POP3, Courier-IMAP), so that Courier can authenticate against the same MySQL database Postfix uses.

The resulting Postfix server is capable of SMTP-AUTH and TLS and quota (quota is not built into Postfix by default, I'll show how to patch your Postfix appropriately). Passwords are stored in encrypted form in the database (most documents I found were dealing with plain text passwords which is a security risk). In addition to that, this tutorial covers the installation of Amavisd, SpamAssassin and ClamAV so that emails will be scanned for spam and viruses. I will also show how to install SquirrelMail as a webmail interface so that users can read and send emails and change their passwords.

The advantage of such a "virtual" setup (virtual users and domains in a MySQL database) is that it is far more performant than a setup that is based on "real" system users. With this virtual setup your mail server can handle thousands of domains and users. Besides, it is easier to administrate because you only have to deal with the MySQL database when you add new users/domains or edit existing ones. No more postmap commands to create db files, no more reloading of Postfix, etc. For the administration of the MySQL database you can use web based tools like phpMyAdmin which will also be installed in this howto. The third advantage is that users have an email address as user name (instead of a user name + an email address) which is easier to understand and keep in mind.

This howto is meant as a practical guide; it does not cover the theoretical backgrounds. They are treated in a lot of other documents in the web.

This document comes without warranty of any kind! I want to say that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!


1 Preliminary Note

This tutorial is based on Ubuntu 12.10 Server (Quantal Quetzal), so you should set up a basic Ubuntu 12.10 server installation before you continue with this tutorial. The system should have a static IP address. I use as my IP address in this tutorial and as the hostname.

Make sure that you are logged in as root (type in

sudo su

to become root), because we must run all the steps from this tutorial as root user.

It is very important that you make /bin/sh a symlink to /bin/bash...

dpkg-reconfigure dash

Use dash as the default system shell (/bin/sh)? <-- No

... and that you disable AppArmor:

/etc/init.d/apparmor stop
update-rc.d -f apparmor remove
apt-get remove apparmor apparmor-utils


2 Install Postfix, Courier, Saslauthd, MySQL, phpMyAdmin

To install Postfix, Courier, Saslauthd, MySQL, and phpMyAdmin, we simply run

apt-get install postfix postfix-mysql postfix-doc mysql-client mysql-server courier-authdaemon courier-authlib-mysql courier-pop courier-pop-ssl courier-imap courier-imap-ssl libsasl2-2 libsasl2-modules libsasl2-modules-sql sasl2-bin libpam-mysql openssl phpmyadmin apache2 libapache2-mod-php5 php5 php5-mysql libpam-smbpass

You will be asked a few questions:

New password for the MySQL "root" user: <-- yourrootsqlpassword
Repeat password for the MySQL "root" user: <-- yourrootsqlpassword
Create directories for web-based administration? <-- No
General type of mail configuration: <-- Internet Site
System mail name: <--
SSL certificate required <-- Ok
Web server to reconfigure automatically: <-- apache2
Configure database for phpmyadmin with dbconfig-common? <-- No


3 Apply The Quota Patch To Postfix

We have to get the Postfix sources, patch it with the quota patch, build new Postfix .deb packages and install those .deb packages:

apt-get build-dep postfix

cd /usr/src
apt-get source postfix

(Make sure you use the correct Postfix version in the following commands. I have Postfix 2.9.3 installed. You can find out your Postfix version by running

postconf -d | grep mail_version

The output should look like this:

root@server1:/usr/src# postconf -d | grep mail_version
mail_version = 2.9.3
milter_macro_v = $mail_name $mail_version


cd postfix-2.9.3
patch -p1 < ../postfix-vda-v11-2.9.1.patch

Next open debian/rules and change DEB_BUILD_HARDENING from 1 to 0:

vi debian/rules


If you don't do this, your build will fail with the following error messages:

maildir.c: In function âdeliver_maildirâ:
maildir.c:974:17: error: format not a string literal and no format arguments [-Werror=format-security]
maildir.c:977:17: error: format not a string literal and no format arguments [-Werror=format-security]
maildir.c:983:17: error: format not a string literal and no format arguments [-Werror=format-security]
maildir.c:986:17: error: format not a string literal and no format arguments [-Werror=format-security]
maildir.c: In function âsql2fileâ:
maildir.c:404:25: warning: ignoring return value of âreadâ, declared with attribute warn_unused_result [-Wunused-result]
maildir.c:417:26: warning: ignoring return value of âwriteâ, declared with attribute warn_unused_result [-Wunused-result]
cc1: some warnings being treated as errors
make: *** [maildir.o] Error 1
make: Leaving directory `/usr/src/postfix-2.9.3/src/virtual'
make[1]: *** [update] Error 1
make[1]: Leaving directory `/usr/src/postfix-2.9.3'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Now we can build the new Postfix .deb packages:


Now we go one directory up, that's where the new .deb packages have been created:

cd ..

The command

ls -l

shows you the available packages:

root@server1:/usr/src# ls -l
total 6928
drwxr-xr-x 24 root root    4096 Oct 19 12:56 linux-headers-3.5.0-17
drwxr-xr-x  7 root root    4096 Oct 19 12:56 linux-headers-3.5.0-17-generic
drwxr-xr-x 18 root root    4096 Nov  4 14:11 postfix-2.9.3
-rw-r--r--  1 root root    3809 Nov  4 14:11 postfix_2.9.3-2ubuntu2_amd64.changes
-rw-r--r--  1 root root 1510254 Nov  4 14:11 postfix_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root  249645 Nov  4 14:10 postfix_2.9.3-2ubuntu2.diff.gz
-rw-r--r--  1 root root    1599 Nov  4 14:10 postfix_2.9.3-2ubuntu2.dsc
-rw-r--r--  1 root root 3760555 May 30 18:04 postfix_2.9.3.orig.tar.gz
-rw-r--r--  1 root root   47064 Nov  4 14:11 postfix-cdb_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root  159634 Nov  4 14:11 postfix-dev_2.9.3-2ubuntu2_all.deb
-rw-r--r--  1 root root 1077006 Nov  4 14:11 postfix-doc_2.9.3-2ubuntu2_all.deb
-rw-r--r--  1 root root   55430 Nov  4 14:11 postfix-ldap_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root   48796 Nov  4 14:11 postfix-mysql_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root   48964 Nov  4 14:11 postfix-pcre_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root   48978 Nov  4 14:11 postfix-pgsql_2.9.3-2ubuntu2_amd64.deb
-rw-r--r--  1 root root   55009 Apr 11  2012 postfix-vda-v11-2.9.1.patch

Pick the postfix and postfix-mysql packages and install them like this:

dpkg -i postfix_2.9.3-2ubuntu2_amd64.deb postfix-mysql_2.9.3-2ubuntu2_amd64.deb


4 Create The MySQL Database For Postfix/Courier

Now we create a database called mail:

mysqladmin -u root -p create mail

Next, we go to the MySQL shell:

mysql -u root -p

On the MySQL shell, we create the user mail_admin with the passwort mail_admin_password (replace it with your own password) who has SELECT,INSERT,UPDATE,DELETE privileges on the mail database. This user will be used by Postfix and Courier to connect to the mail database:

GRANT SELECT, INSERT, UPDATE, DELETE ON mail.* TO 'mail_admin'@'localhost' IDENTIFIED BY 'mail_admin_password';
GRANT SELECT, INSERT, UPDATE, DELETE ON mail.* TO 'mail_admin'@'localhost.localdomain' IDENTIFIED BY 'mail_admin_password';

Still on the MySQL shell, we create the tables needed by Postfix and Courier:

USE mail;

CREATE TABLE domains (
domain varchar(50) NOT NULL,
PRIMARY KEY (domain) )

CREATE TABLE forwardings (
source varchar(80) NOT NULL,
destination TEXT NOT NULL,
PRIMARY KEY (source) )

email varchar(80) NOT NULL,
password varchar(20) NOT NULL,
quota INT(10) DEFAULT '10485760',

CREATE TABLE transport (
domain varchar(128) NOT NULL default '',
transport varchar(128) NOT NULL default '',
UNIQUE KEY domain (domain)


As you may have noticed, with the quit; command we have left the MySQL shell and are back on the Linux shell.

The domains table will store each virtual domain that Postfix should receive emails for (e.g.


The forwardings table is for aliasing one email address to another, e.g. forward emails for to

source destination

The users table stores all virtual users (i.e. email addresses, because the email address and user name is the same) and passwords (in encrypted form!) and a quota value for each mail box (in this example the default value is 10485760 bytes which means 10MB).

email password quota No9.E4skNvGa. ("secret" in encrypted form) 10485760

The transport table is optional, it is for advanced users. It allows to forward mails for single users, whole domains or all mails to another server. For example,

domain transport smtp:[]

would forward all emails for via the smtp protocol to the server with the IP address (the square brackets [] mean "do not make a lookup of the MX DNS record" (which makes sense for IP addresses...). If you use a fully qualified domain name (FQDN) instead you would not use the square brackets.).

BTW, (I'm assuming that the IP address of your mail server system is you can access phpMyAdmin over in a browser and log in as mail_admin. Then you can have a look at the database. Later on you can use phpMyAdmin to administrate your mail server.

Share this page:

8 Comment(s)

Add comment


From: Maqsood at: 2013-01-23 12:02:45

Dear Recipient,

I am facing problem while configuring Postfix, I am performing same steps as given in this article. But I am receiving error message while run this commend “dpkg -i postfix_2.9.3-2ubuntu2_amd64.deb postfix-mysql_2.9.3-2ubuntu2_amd64.deb”. I am using Ubuntu 12.10 server edition. Waiting for your nice guidance

From: Anonymous at: 2013-03-01 14:51:16

Nice guidance - why don't you tell us what the error message is so we can see it? :)

From: Rinti at: 2013-08-07 10:52:15

Its a nice post. I have done accurately and its running fine. But I got another problem. that is about vacation responder / auto reply. I got few ways in internet. but none works for me. As I followed your tutorial, I request you to give a tutorial for auto response working with this configuration.

From: at: 2013-05-17 16:44:07

I had to edit /etc/courier/imapd-ssl and set TLS_CIPHER_LIST="HIGH:MEDIUM:LOW" (it defaults to "HIGH:MEDIUM"). Before I did this STARTTLS logins worked (ports 25, 110) but users could not login using SSL over imap (port 993) or pop3 (port 995) and I kept getting the following in the mail log:

couriertls: read: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate

I spent days googling this and couldn't find anything, so adding it here in case anyone else encounters the same issue.

From: Anonymous at: 2013-09-04 11:50:44

If you're using logcheck, remove the spaces either side of the equals sign on the sql_select line of /etc/postfix/sasl/smtpd.conf otherwise it won't match the logcheck ignore rule.

From: shai at: 2013-08-03 15:45:11

adduser clamav amavis
/etc/init.d/amavis restart
/etc/init.d/clamav-freshclam restart


/etc/init.d/clamav-daemon restart

From: Didier Misson at: 2013-03-03 03:40:36

Don't forget that mailbox need to be initialize with the "maildirmake" command !

For :


cd /home/vmail



maildirmake sales

chown -R vmail:vmail sales


Thanks for this great HowTo.


From: Michael at: 2013-12-04 09:50:20

Maybe someone else did the same mistake as me. I had pointed for my domain to my own server and got the error message in /var/log/

(mail for <fqdn of mailserver> loops back to myself)... 

I had just deleted the transport entry and the email-server worked fine.