A mail setup checker for self-hosters
Sojourner can send emails and check if SPF, DKIM and DMARC are correctly configured.
How does this work? Another email hoster is used that is known to check SPF/DKIM/DMARC and puts the results in the Authentication-Result headers. Sojourner checks these headers to see if our self-hosted email server is configured correctly.
An email is sent to another email hoster, using our self-hosted email server. The destination email address should be configured to forward an email to our self-hosted email server (probably a different address). The email is sent back to our self-hosted email server (if everything goes well!), but with the additional mail headers that give the result of the SPF/DKIM/DMARC checks.
Say we have a forward setup from [email protected]
to [email protected]. Then an email is sent:
,-----------.
| Sojourner |
`-----------'
| 1) send email from [email protected]
v to [email protected]
,---------------------.
| self-hosted SMTP |
`---------------------'
| 2) send email ^
v | 3) forward email to:
,---------------------. [email protected]
| other email hoster |
`---------------------'
After a delay (some hosters take some minutes to receive/forward emails), the INBOX of the special account is checked:
,-----------.
| Sojourner |
`-----------'
| 1) get emails for [email protected]
v
,---------------------.
| self-hosted IMAP |
`---------------------'
All emails to this address are checked for a special header that Sojourner added and only emails that were sent within a certain time (can be configured) are considered.
If no email was received for a certain sender, then an error message is shown. If the email headers show that one of the checks did not pass, an error message is shown.
There is a docker image that packages this application: https://hub.docker.com/r/mjholtkamp/sojourner
To configure Sojourner, a settings.py file is mounted in the docker image. For information on how and what to configure, see settings.example.py
Then run the following docker command (substituting the path to the settings file of course):
docker run \
-v /path/to/your/settings.py:/app/conf/settings.py \
mjholtkamp/sojourner \
send
After a delay, check emails:
docker run \
-v /path/to/your/settings.py:/app/conf/settings.py \
mjholtkamp/sojourner \
check
I personally have setup two cronjobs to do run these two commands with 10 minutes in between.
- Sojourner assumes SMTP/IMAP are both accessed over SSL/TLS, so unencrypted access will not work
- Sojourner only complains if something is not right, you still have to figure out what went wrong in that case
- Sojourner will not work without a second email hoster, or at least another email server that checks SPF/DKIM/DMARC. Usually that is not checked by the MSA, but by the MTA or MDA.
- Potentially others that I'm not aware of. Feel free to create an issue if you think it is a bug.
Sojourner is named after Sojourner Truth. I was looking for a famous nurse (since this application is checking the health 😄) and when I saw her name, I liked it since it reminded me of the Sojourner Mars Rover. I like the name because a sojourner is a traveller and the emails that Sojourner sends are travelling to and back. Yes, I know the reasons are shallow, but I made this, so I get to pick the name 😉.