Bug Report

I believe this is the same as #1687. I do not want SASL.

Using ENABLE_SASLAUTHD=0 and SMTP_ONLY=1 results in the following log error (and could not connect to this SMTP server error in Apple Mail).

This is the relevant log error:

Feb  7 14:15:31 mailer-ams postfix/submission/smtpd[892]: warning: SASL: Connect to private/auth failed: Connection refused
Feb  7 14:15:31 mailer-ams postfix/submission/smtpd[892]: fatal: no SASL authentication mechanisms

Context

Fresh installation.

What is affected by this bug?

Using SMTP.

When does this occur?

Every time.

How do we replicate the issue?

I follow the default installation instructions.

Besides adding domain and hostname to .env, this is what I edit in mailserver.env:

SMTP_ONLY=1
ONE_DIR=1
PERMIT_DOCKER=host
SSL_TYPE=manual
SSL_CERT_PATH=/path/to/fullchain.cer
SSL_KEY_PATH=/path/to/cert.key

I keep ENABLE_SASLAUTHD=0 with its default value.

docker-compose.yml only mounts /path/to/. https://www.checktls.com is happy with the settings, gives 100% and valid certificate.

Workaround

Setting SMTP_ONLY= (to empty) fixes the issue.

Your Environment

• version: docker.io/mailserver/docker-mailserver:latest
• available RAM: 8GB
• Docker version: Docker version 20.10.3, build 48d30b5