Full Mail Server Solution w/ Virtual Domains & Users - Page 11 (Secure Postfix+TLS)
B. Secure Postfix+TLS
To begin with, we're going to need to install postfix on secure-mail.example.com. This particular install doesn't need quota support (It doesn't handle local delivery), but just to keep things simple, we're going to install it the same way we did above:
# dpkg -i postfix_2.3.8-2_i386.deb
If/when the auto-configuration asks you questions about postfix during the installation, just select "No Configuration"
dpkg is going to install all of the configuration files for Postfix into /etc/postfix, so go there, and create the file main.cf:
# cd /etc/postfix
The main.cf file can be edited using two different methods. You can use your favorite text editor, or you can use the built-in postfix toolpostconf. We've already used postconf once to determine our version in subsection IV.A above.
The real benefit of the postconf tool is that it has some built in error checking, and it eliminates the possibility of 'weirdness' due to carriage returns, line feeds, odd quotes, etc. We'll be using it in this guide, but there really is no requirement.
Start by filling in the basic information:
# postconf -e 'myhostname = secure-mail.example.com'
You'll notice that this time we disabled local delivery.
Since this is basically just an outbound relay server, we
don't want it trying to 'deliver'
Now we'll want to fill in the information for SASL (SMTP Authentication). This does NOT encrypt the connection, it just requires the users to log in:
# postconf -e 'smtpd_sasl_auth_enable = yes'
So now your postfix install will query dovecot for all of it's authentication needs, but it's still not encrypted. Let's go ahead and change that...
# postconf -e 'smtpd_tls_cert_file =
Go ahead and reload postfix...
# postfix reload
And then let's get Dovecot up and running...