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)

error in server logs

What happened and when does this occur?

We have two problems.
1. Server deployed with ENABLE_AMAVIS=0. But /etc/cron.d/amavisd-new not disabled. Unnecessary work of processes every 3 hours
2. By default, no alias is created for the internal mail of the docker image.
For example: cron execute /etc/cron.d/amavisd-new . A line gets into stdout, which cron is obliged to send to the user as a result of work.

From: [email protected] (Cron Daemon)
To: [email protected]
Subject: Cron <amavis@imap>  test -e /usr/sbin/amavisd-new-cronjob && /usr/sbin/amavisd-new-cronjob sa-sync

Mail server received this mail. Since there is no alias for [email protected], the mail will be stored in /var/mail/amavis. it`s 'ok', but we do not see mail, and potentially problems.

What did you expect to happen?

1. /etc/cron.d/amavisd-new don`t work
2. description in the documentation about mandatory creation of an alias for internal users
For example `./setup.sh alias add @mail.example.com [email protected]`

How do we replicate the issue?

1. deploy container with ENABLE_AMAVIS=0
2. wait some time
3. check file /var/mail/amavis

DMS version

v11.1.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

No response

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