docker-postfix-forwarder

This is the start of a Docker container that will forward mail using postfix.

The container supports acting as an MTA for outgoing mail from that forwarded address.

DNS records

For each domain you want to forward, set something like this:

name	type	value
mail.example.com	A	x.x.x.x
example.com	MX	1 mail.example.com.
example.com	TXT	"v=spf1 mx ~all"

For the one domain that you'll use for SRS, do this:

name	type	value
srs.example.com	MX	1 mail.example.com.
srs.example.com	TXT	"v=spf1 mx ~all"

Config file

Copy config.example.yaml to config.yaml and edit as appropriate. There are comments on each value.

SRS

SPF is a way for mail senders to publish in DNS a list of address that are allowed to send mail for that domain. The policy can either soft-fail or hard-fail. See RFC7208 for details.

Support for SRS is optional but enabled in the example config. You should think carefully about leaving it enabled.

If you enable it you will be forwarding some SPAM on and it is possible that you'll classified as a SPAM relay/sender. That isn't good. Hopefully we'll be able to screen enough incoming SPAM that this won't be a problem.

On the other hand, if the mail you are forwarding fails the SPF check, it is likely that legitimate mail will be marked as SPAM. There are some large companies that have hard-fail SPF policies (I've seen Apple, Evite and RedFin, for example) that are classified as SPAM by GMail without SRS.

Note that GMail advises not doing envelope sender rewriting when forwarding mail. Even so, I'm currently running with SRS enabled when forwarding to GMail.

Postscreen

Postscreen is included with Postfix and provides some simple ways to reject mail as likely SPAM. You can read the full details here.

Basically, there are two types of checks:

Pre-220 checks: These checks are performed during the initial negotation of the connection with the sending agent. If these pass, then postscreen can hand off the TCP connection to postfix with little delay in service. This first making sure that the sending agent waits appropriately before speaking. The second test is against DNS black lists. We rely most heavily on spamhaus here but I'm open to suggestions.

Post-220 checks: There are further checks that look for deeper protocol violations. The problem here is that postscreen isn't a proxy. So if it determines that a sending agent is legit, it can't hand off to postfix at this point. Instead, it tells the sending agent to retry later. On the next try, the connection will be handed off to postfix immediately. However, well behaved agents may wait minutes before retrying.

Build/upload

If you are using the Google Cloud Registry, simply run make upload-gcr. This will build and upload the Docker image to a private registry.

DO NOT push this image to a public registry and it has sensitive information (passwords).

Run

To run the image, do something like this:

sudo mkdir /opt/postfix-forwarder
GCEPROJECT=$(gcloud config -q --format text list project | cut -d ' ' -f 2 | tr - _)
gcloud docker pull gcr.io/$GCEPROJECT/postfix-forwarder
docker run --name postfix \
  -v /opt/postfix-forwarder:/var/spool/postfix \
  -p 587:587 -p 25:25 \
  -d gcr.io/$GCEPROJECT/postfix-forwarder

As all of the important data is stored in a host volume, you kill/delete/restart the container as necessary to change configuration. Note that the account IDs used in the container (for the postfix user, and postfix and postdrop groups) won't line up with your host system so if you back up this directory (using tar or whatever) use numeric IDs.

Configuring GMail

If you are using GMail, you can configure it to send mail through this account. To do that:

Go to "Settings" and then "Accounts and Import"
Click on "Add another email address you own"
Enter the full email address: user@example.com and click "Next Step"
Set up the SMTP server:
Set the SMTP server to mail.example.com and the port to 587.
Set the username to the full email address (not just the user part): user@example.com
Enter your password for this account
Select "Secure connection using TLS"
Click "Add Account"
Click on the verify link as it is sent. This might get directed to spam.

Gotcha: Logging

Everything from the postfix install will be output to stdout and logged with Docker. This means that docker logs postfix will give you some good info. But, unfortunately, those logs are never truncated or rotated. Eventually they will fill up your disk and bad stuff will happen.

If you are running logrotate on the host system, you truncate/rotate logs by dropping this file in /etc/logrotate.d/docker:

/var/lib/docker/containers/*/*-json.log {
    rotate 5
    copytruncate
    missingok
    notifempty
    compress
    maxsize 10M
    daily
    create 0644 root root
}

No guarantees here as this is a bit of a hack. This is a big hole in Docker right now. If things are logging fast, the copytruncate directive may miss some log lines.

TODOs

Integrate SpamAssasin
Support multiple email forward targets
Figure out DKIM
More flexibilty in rewriting/aliases

References

A lot of Google-ing was done to get to this point. However, this seemed to be the most relevant article: http://seasonofcode.com/posts/setting-up-dkim-and-srs-in-postfix.html

jbeda/docker-postfix-forwarder