bluelotussoftware/spamassassin repository overview

⁠Apache SpamAssassin

This project is based on the excellent work done by Christian Luginbühl dinkel/spamassassin⁠ to run Apache SpamAssassin as a Docker image.

There are two versions: Alpine Linux, and Debian Buster (slim). The Alpine Linux version is about 34% smaller than the Debian image.

It runs spamd on exposed port 783 and constantly updates its ruleset.

⁠Usage

docker run -d -p 783:783 bluelotussoftware/spamassassin

or linked (this is how I use it)

docker run -d --name spamassassin bluelotussoftware/spamassassin
docker run -d --link spamassassin:spamassassin application-with-spamc-or-something

⁠Configuration (environment variables)

None at the moment.

⁠Data Persistence

It has been a design decision to discard exporting the ruleset to a data volume as it will be always be brought up-to-date (quite quickly) upon starting a new container. Also currently there is no intention to have a custom config.

⁠Explaining run.sh

This is a poor man's supervisord. It is my strong (but not so much challenged) belief, that there shouldn't be yet another process manager (Docker has one, CoreOS has one (with fleet and systemd).

The only thing this script does is watching its forked (background) processes and as soon as one dies, it terminates all the others and exits with the code of the first dying process.

⁠TODO

• There is an open issue on the script for /run.sh: set: line 2: can't access tty; job control turned off which seems to be related to the tty versus console on Alpine Linux.