t-lo/mailserver

Dockerised mailserver

mailserver's Issues

Feature request: Automated Builds + Publishing of docker image and release tarball via Github Actions

This is a good issue to start with if you'd like to become a contributor to the mailserver project.

Goal of this feature request is to automate build and publishing of new Mailserver releases. There's a script that does most of this work already - the logic of that script would need to be converted into a Github Action.

todo list

• add documentation on client set-up
• add monitoring
• add sanity check after initialisation
  • check MX of DOMAIN and ADDITIONAL_DOMAINS
  • check SPF and DKIM TXT records
• add opendkim and opendmarc to set-up

Feature request: Pigeonhole sieve server

Feature Request: virus scanning / clamav

This is a good first issue to start with if you'd like to become a contributor to the mailserver project.

Add virus scanning to the mailserver, e.g via clamav or other virus scanners available on Alpine. The feature should be added directly to the mailserver image, i.e. no external container should be used.

The virus scanner should be integrated directly with postfix, e.g. via postfix' content_filter feature.

Create default admin email (e.g. for `abuse@...` to work)

Feature request: fail2ban

WIP, needs a number of privileges for the container. Also, depends on the host's iptables/nftabled kmods.

Feature request: spam scoring / spamassassin integration

This is a good first issue to start with if you'd like to become a contributor to the mailserver project.

Add spam scoring to the mailserver, e.g via spamassassin or other spam scanners available on Alpine. The feature should be added directly to the mailserver image, i.e. no external container should be used.

The spam scorer should be integrated directly with postfix, e.g. via postfix' content_filter feature. It should provide a spam rating in email headers so users can use it in their SIEVE scripts.

Release 1.0

Find a good release name, package

• LICENSE
• README.md
• dns_check.sh
• settings.env.empty
• start_mailserver.sh
• start_monitoring.sh
• user.sh

into a tarball, and call it a release!

Make LMTP accessible from the outside

Some applications like mailman use LMTP to interface with the SMTP server.
For this to work from/to the container host, LMTP access to the mailserver container is required.

Either

• switch to tcp LMTL and forward LMTP ports to the host (to 127.0.0.1)
• move LMTP sockets to /host