Miscellaneous first checks

• I checked that all ports are open and not blocked by my ISP / hosting provider.
• I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

Affected Component(s)

Spamassassin KAM

What happened and when does this occur?

The daily cronjob of Spamassassin KAM has failed and mailed this message:

Cron root@mail test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/spamassassin_kam:
Reloading SpamAssassin Mail Filter Daemon: No spamd found running; none killed.
run-parts: /etc/cron.daily/spamassassin_kam exited with return code 1

What did you expect to happen?

No report from cronjob.

How do we replicate the issue?

I've set those environment variables in the compose file:

    environment:
      - SSL_TYPE=letsencrypt
      - SSL_DOMAIN=mail.domain.tld
      - ENABLE_CLAMAV=1
      - ENABLE_DNSBL=1
      - ENABLE_FAIL2BAN=1
      - ENABLE_SPAMASSASSIN=1
      - ENABLE_SPAMASSASSIN_KAM=1
      - ENABLE_POSTGREY=1
      - ENABLE_QUOTAS=1
      - POSTFIX_MESSAGE_SIZE_LIMIT=10240000 # Set the message size limit for all users. ~10 MB

DMS version

v10.5.0

What operating system is DMS running on?

Linux

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Docker Compose

docker-compose.yml

No response

Relevant log output

No response

Other relevant information

Issue #2414 is reporting spamd not running in certain configurations.

What level of experience do you have with Docker and mail servers?

• I am inexperienced with docker
• I am inexperienced with mail servers
• I am uncomfortable with the CLI

Code of conduct

• I have read this project's Code of Conduct and I agree
• I have read the README and the documentation and I searched the issue tracker but could not find a solution

Improvements to this form?

No response