Full Mail Server Solution w/ Virtual Domains & Users (Debian Etch, Postfix, Mysql, Dovecot, DSpam, ClamAV, Postgrey, RBL) - Page 14

VIII. Final Words and Sources

So, assuming you've followed this guide through to its entirety, you should have one fully functional email solution. You've got a primary and secondary MX, a mail delivery server, a secure mail server, and a healthy dose of spam and anti-virus protection.

Does that mean you can just push the 'GO' button and walk away? Absolutely not. First off, you're going to want to run the system through a number of tests... test everything. Try sending mail using your primary & secondary MX's as your SMTP server (it shouldn't work), try sending mail using your secure mail server, but without security settings enabled in your client (It also shouldn't work). Try everything, and then when it's all working, try it again. You don't want to go rolling this setup into production without having tested it thoroughly first.

In addition, it's entirely possible that something (or some things) are incorrect in this guide. A large portion of it was written from memory, and that always opens you up to a hole or two. If you find a glaring error, feel free to drop me a line, and I'll get it fixed. This is a long guide, I wouldn't be surprised if there were a few glitches in it.

Finally, I'd like to send out a 'Thank you' to the various people who helped me write this guide. There's more than one source that I 'borrowed' from verbatim, and I couldn't have written this without them. In no particular order:

HOWTO - Postfix and Dovecot with MySQL and TLS/SSL, Postgrey and DSPAM

Virtual Users and Domains with Postfix, Courier, and MySQL (Debian Etch)

Network File System (NFS) Server and Client Configuration in Debian


DSPAM With Embedded ClamAV Integrated Into Postfix With Virtual Users And Domains

Share this page:

Sub pages

5 Comment(s)

Add comment


From: at: 2008-03-27 06:06:28

Hi Vector,

I would just like to know how the mail gets transferred from the MX's to the delivery server (postman). I'm trying to understand how this full mail server setup works because I would like to implement something similar to this but using centos and ldap users.  

From: Stefan at: 2008-11-01 18:07:49

There is no explanation on how the mail is actually transfered from the MX server to the Mail Delivery Server. Using the steps in the guide will make the MX server try to deliver the mail directory into the NFS shared vmail folder, which isn't the desired behaviour.

From: Matt at: 2009-06-15 13:16:16

"NOTE: This is a temporary setup, just because we hadn't finished the DSPAM virtual user install prior to writing this guide. Ideally, you'd want DSPAM looking at the same virtual user table as Postfix in order to get all the token information stored correctly. I'll update the guide as soon as we've completed that change-over."

 Has this been updated anywhere? can anyone shed some light on what changes should be made?


From: mbsouth at: 2009-09-10 10:02:01

Would be nice to have an updated howto (based an this one) with Debian Lenny, Postfix 2.5(6), Dovecot 1.1(2) on three nodes (2xSMTP Postfix, 1x Dovecot IMAP/POP3)


From: at: 2007-11-15 20:55:15

Heads up when using the configuration examples for the mailbox path. Since maildir:/vmail/%d/%u is used in dovecot.conf, you should do the same in dovecot-sql.conf.

Such as:

# Get the mailbox
user_query = SELECT '/vmail/%d/%u' AS home, 'maildir:/vmail/%d/%u' AS mail, 150 AS uid, 8 AS gid, CONCAT('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1'
# Get the password
password_query = SELECT username AS user, password, '/vmail/%d/%u' AS userdb_home, 'maildir:/vmail/%d/%u' AS userdb_mail, 150 AS userdb_uid, 8 AS userdb_gid FROM mailbox WHERE username = '%u' AND active = '1'

Otherwise mail is delivered to /vmail/domain/user@domain and then IMAP checks /vmail/domain/user

Or change dovecot.conf to maildir:/vmail/%d/%n if you prefer the latter.