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

Want to support HowtoForge? Become a subscriber!
 
Submitted by falko (Contact Author) (Forums) on Tue, 2014-05-06 12:16. :: Linux | Ubuntu | Email | MySQL | Postfix

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

Version 1.0
Author: Falko Timme, updated by Srijan Kishore
Last edited 30/Apr/2014

This tutorial is Copyright (c) 2014 by Falko Timme & Srijan Kishore. It is derived from a tutorial from Christoph Haas which you can find at http://workaround.org. 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 14.04 Server (Trusty Tahr), so you should set up a basic Ubuntu 14.04 server installation before you continue with this tutorial. The system should have a static IP address. I use 192.168.0.100 as my IP address in this tutorial and server1.example.com 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, if you are getting  apparmor: unrecognized service then remove it from update-rc.d

service 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: <-- server1.example.com
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

Some time you can get an error as follows:-

root@server1:~# apt-get build-dep postfix
Reading package lists... Done
Building dependency tree      
Reading state information... Done
E: You must put some 'source' URIs in your sources.list
root@server1:~#

You can correct it as follows, by adding the source repositories:

vi /etc/apt/sources.list

Make the entry as in my case is

deb http://archive.ubuntu.com/ubuntu trusty main restricted universe
deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe
deb http://security.ubuntu.com/ubuntu trusty-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu trusty partner


deb-src http://archive.ubuntu.com/ubuntu trusty main restricted universe
deb-src http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe
deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted universe multiverse
deb-src http://archive.canonical.com/ubuntu trusty partner

Next

apt-get update
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.11.0 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.11.0
milter_macro_v = $mail_name $mail_version
root@server1:/usr/src#


wget http://vda.sourceforge.net/VDA/postfix-vda-v13-2.10.0.patch
cd postfix-2.11.0
patch -p1 < ../postfix-vda-v13-2.10.0.patch

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

vi debian/rules

[...]
export DEB_BUILD_HARDENING=0
[...]

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.11.0/src/virtual'
make[1]: *** [update] Error 1
make[1]: Leaving directory `/usr/src/postfix-2.11.0'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
root@server1:/usr/src/postfix-2.11.0#

Now we can build the new Postfix .deb packages:

dpkg-buildpackage

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 6824
drwxr-xr-x 18 root root    4096 Apr 30 04:28 postfix-2.11.0
-rw-r--r--  1 root root   46756 Apr 30 04:28 postfix-cdb_2.11.0-1_amd64.deb
-rw-r--r--  1 root root  142842 Apr 30 04:28 postfix-dev_2.11.0-1_all.deb
-rw-r--r--  1 root root  851842 Apr 30 04:28 postfix-doc_2.11.0-1_all.deb
-rw-r--r--  1 root root   53898 Apr 30 04:28 postfix-ldap_2.11.0-1_amd64.deb
-rw-r--r--  1 root root   48500 Apr 30 04:28 postfix-mysql_2.11.0-1_amd64.deb
-rw-r--r--  1 root root   48610 Apr 30 04:28 postfix-pcre_2.11.0-1_amd64.deb
-rw-r--r--  1 root root   48324 Apr 30 04:28 postfix-pgsql_2.11.0-1_amd64.deb
-rw-r--r--  1 root root   55701 Jun  7  2013 postfix-vda-v13-2.10.0.patch
-rw-r--r--  1 root root  267855 Apr 30 04:27 postfix_2.11.0-1.diff.gz
-rw-r--r--  1 root root    1522 Apr 30 04:27 postfix_2.11.0-1.dsc
-rw-r--r--  1 root root    3885 Apr 30 04:28 postfix_2.11.0-1_amd64.changes
-rw-r--r--  1 root root 1329238 Apr 30 04:28 postfix_2.11.0-1_amd64.deb
-rw-r--r--  1 root root 4034741 Feb 12 01:38 postfix_2.11.0.orig.tar.gz
root@server1:/usr/src# 

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

dpkg -i postfix_2.11.0-1_amd64.deb postfix-mysql_2.11.0-1_amd64.deb

 

4 Create The MySQL Database For Postfix/Courier

Now we create a database called mail:

mysqladmin -u root -p create mail

You will be asked for this question:

Enter Password: <-- yourrootsqlpassword

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';
FLUSH PRIVILEGES;

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) )
ENGINE=MyISAM;

CREATE TABLE forwardings (
source varchar(80) NOT NULL,
destination TEXT NOT NULL,
PRIMARY KEY (source) )
ENGINE=MyISAM;

CREATE TABLE users (
email varchar(80) NOT NULL,
password varchar(20) NOT NULL,
quota INT(10) DEFAULT '10485760',
PRIMARY KEY (email)
) ENGINE=MyISAM;

CREATE TABLE transport (
domain varchar(128) NOT NULL default '',
transport varchar(128) NOT NULL default '',
UNIQUE KEY domain (domain)
) ENGINE=MyISAM;

quit;

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. example.com).

domain
example.com

The forwardings table is for aliasing one email address to another, e.g. forward emails for info@example.com to sales@example.com.

source destination
info@example.com sales@example.com

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
sales@example.com 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
example.com smtp:[1.2.3.4]

would forward all emails for example.com via the smtp protocol to the server with the IP address 1.2.3.4 (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 192.168.0.100) you can access phpMyAdmin over http://192.168.0.100/phpmyadmin/ 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.

 


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by Milaensis (not registered) on Thu, 2014-07-17 10:35.
By following this guide to the letter SSL / TLS does not work! No answers on any port. Do you have a solution?
Submitted by admin (registered user) on Thu, 2014-07-17 10:38.
Check postfix master.cf file to ensure that there is no # in front of the smtps and Submission lines.
Submitted by Anonymous (not registered) on Mon, 2014-07-07 16:50.

First of all, thank you!   Thank you for providing the only bl**dy "how to" for SSL-enabled imap/smtp/postfix on the web that actually works!! :D   I owe you a pint!

I have two questions/suggestions for a possible update:

  1. How to tweak the configuration to force the use of SSL for imap/smtp.
  2. Why is samba (smb) needed? Seems like an odd dependency which I'd like to remove.

Since installing the dependences for that libpam-smbpass package, I get the following error every time I use 'sudo' :

no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
Submitted by cowbjim74 (registered user) on Fri, 2014-06-06 01:56.

I am having serious issues. I have installed 3 times, followed to the letter your guide.

First AWEESOME guide. I am scratching my head on this one. I am trying to set up an email server and know Exchange very very well. BUT do not want to give MS any of my hard earned money. I also have quite extensive background (not used for a while) in Linux and Ubuntu

I am using 14.04

whenever an IMAP client whether it be MS Live Mail, other IMAP, or Squirrelmail, I am not making a connection

 

I have sent numerous test messages to the users that were created. These were sent from mailx, Gmail, and Yahoo.

 

I don't even see where the others hit the system from GMail, or Yahoo.

 

But on the one sent from mailx, it appears that it was delivered, but then dropped ?????

log entries:

Jun  5 19:30:42 DS-JMW-UMail postfix/pickup[30580]: 24394E349E: uid=1000 from=<wjw003@DS-JMW-UMail.jmwent.com>
Jun  5 19:30:42 DS-JMW-UMail postfix/cleanup[607]: 24394E349E: message-id=<20140606003042.24394E349E@mail.jmwent.com>
Jun  5 19:30:42 DS-JMW-UMail postfix/qmgr[30581]: 24394E349E: from=<wjw003@DS-JMW-UMail.jmwent.com>, size=358, nrcpt=1 (queue active)
Jun  5 19:30:48 DS-JMW-UMail postfix/smtpd[616]: connect from localhost[127.0.0.1]
Jun  5 19:30:48 DS-JMW-UMail postfix/smtpd[616]: A9FCCE34A1: client=localhost[127.0.0.1]
Jun  5 19:30:48 DS-JMW-UMail postfix/cleanup[607]: A9FCCE34A1: message-id=<20140606003042.24394E349E@mail.jmwent.com>
Jun  5 19:30:48 DS-JMW-UMail postfix/qmgr[30581]: A9FCCE34A1: from=<wjw003@DS-JMW-UMail.jmwent.com>, size=802, nrcpt=1 (queue active)
Jun  5 19:30:48 DS-JMW-UMail amavis[557]: (00557-01) Passed CLEAN {RelayedOpenRelay}, <wjw003@DS-JMW-UMail.jmwent.com> -> <wjw003@localhost>, Message-ID: <20140606003042.24394E349E@mail.jmwent.com>, mail_id: ifjtmyWInhAp, Hits: 2.425, size: 358, queued_as: A9FCCE34A1, 6495 ms
Jun  5 19:30:48 DS-JMW-UMail postfix/smtp[611]: 24394E349E: to=<wjw003@localhost>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.8, delays=0.3/0.03/0.07/6.5, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as A9FCCE34A1)
Jun  5 19:30:48 DS-JMW-UMail postfix/qmgr[30581]: 24394E349E: removed
Jun  5 19:30:48 DS-JMW-UMail postfix/local[619]: A9FCCE34A1: to=<wjw003@mail.jmwent.com>, orig_to=<wjw003@localhost>, relay=local, delay=0.19, delays=0.08/0.04/0/0.07, dsn=2.0.0, status=sent (delivered to mailbox)
Jun  5 19:30:48 DS-JMW-UMail postfix/qmgr[30581]: A9FCCE34A1: removed

 

Now, when I use the clients to access IMAP, I get the following errors:

Jun  5 19:30:49 DS-JMW-UMail imapd: Connection, ip=[::1]
Jun  5 19:30:49 DS-JMW-UMail imapd: chdir wjw003/wjw003/: No such file or directory
Jun  5 19:30:49 DS-JMW-UMail imapd: wjw003: No such file or directory

 

Please help me for I have not much hair left to lose...

 

Thank you in advance!

 

 

Submitted by Anonymous (not registered) on Sat, 2014-06-07 19:31.

I have seen this too!

Apparently the directories, in /home/vmail/domain.tld aren't created when the mail arrives.

The reason might be an permission issue, not sure though, since I don't have any hair to lose any-more. I gave up on it.

I could use a sponge though, to polish the great planes.

Every time there is a DNS or mail or kernel update with Ubuntu, it breaks my system in bits and pieces. Sick of running around and fixing it!

Although, using the tut here to the letter too (several times), on a fresh install, it didn't work. It goes from authentication failure, to directory not found. Others, claim that saslauth doesn't know how to handle 64 bit OS's. Dunno!


Submitted by HogensHero (not registered) on Wed, 2014-07-02 04:35.

I know this is a stupid question but are you using a fully qualified domain name or are you using domain.tld?

Apparently the directories, in /home/vmail/domain.tld aren't created when the mail arrives.

If you are using domain.tld you need to use your actual domain name.  I was able to get this up and running on 14.04 in 20 minutes using this tutorial and my domain name.

Submitted by HogensHero (registered user) on Sat, 2014-05-17 04:51.

It would be helpful if you added in how to enable phpmyadmin so that you can access it in a web browser as you have shown.

BTW, (I'm assuming that the IP address of your mail server system is 192.168.0.100) you can access phpMyAdmin over http://192.168.0.100/phpmyadmin/ 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. 

 Maybe add these lines somewhere.

ln -s /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf

a2enconf phpmyadmin
service apache2 reload

Thank for the tutorial.