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)

supervisorctl restart postfix fails

What happened and when does this occur?

Running supervisorctl restart postfix inside the container, leads to the following endless looping error messages in mail.log:

2023-02-25 22:51:45,196 INFO waiting for postfix to stop
2023-02-25 22:51:45,197 INFO stopped: postfix (terminated by SIGTERM)
2023-02-25 22:51:45,199 INFO spawned: 'postfix' with pid 4682
2023-02-25 22:51:45,200 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Feb 25 22:51:45 mail postfix/postfix-script[4688]: fatal: the Postfix mail system is already running
2023-02-25 22:51:46,223 INFO exited: postfix (exit status 1; not expected)
2023-02-25 22:51:47,228 INFO spawned: 'postfix' with pid 4689
Feb 25 22:51:47 mail postfix/postfix-script[4695]: fatal: the Postfix mail system is already running
2023-02-25 22:51:47,256 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-02-25 22:51:48,257 INFO exited: postfix (exit status 1; not expected)
2023-02-25 22:51:49,262 INFO spawned: 'postfix' with pid 4696
Feb 25 22:51:49 mail postfix/postfix-script[4702]: fatal: the Postfix mail system is already running
2023-02-25 22:51:49,287 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-02-25 22:51:50,288 INFO exited: postfix (exit status 1; not expected)

What did you expect to happen?

Clean restart of postfix.

How do we replicate the issue?

1. Run supervisorctl restart postfix inside the container

...

DMS version

edge

What operating system is DMS running on?

Linux

Which operating system version?

Debian 11

What instruction set architecture is DMS running on?

AMD64 / x86_64

What container orchestration tool are you using?

Docker

docker-compose.yml

No response

Relevant log output

No response

Other relevant information

This is a regression introduced in #3033

Workaround:

supervisorctl stop postfix
service postfix stop
supervisorctl start postfix

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

• I am inexperienced with docker
• I am rather experienced with docker
• I am inexperienced with mail servers
• I am rather experienced with mail servers
• I am uncomfortable with the CLI
• I am rather comfortable 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