After a short night I thing I found 1-2 hints in the postfix log.
When trying to send a Mail with SoGo, there are this log entries I get when executing
sudo docker-compose logs -f –tail=200 postfix-mailcow
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: connect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: warning: host or service rspamd:9900 not found: Name or service not known
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: warning: connect to Milter service inet:rspamd:9900: Cannot assign requested address
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: NOQUEUE: milter-reject: CONNECT from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: NOQUEUE: milter-reject: EHLO from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]: 451 4.7.1 Service unavailable - try again later; proto=SMTP helo=<baec04defb79>
mailcowdockerized-postfix-mailcow-1 | Jun 26 08:00:32 e12f9bbc03ae postfix/sogo/smtpd[3303]: disconnect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248] ehlo=1 auth=0/1 quit=1 commands=2/3
The first hint indicates that rspamd is not available.
warning: host or service rspamd:9900 not found: Name or service not known
The second hint seems to confirm this as if I google for that the error code 451 indicates that a spam mail is rejected to accept.
NOQUEUE: milter-reject: EHLO from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
As a result, it looks like rspamd has a problem.
So I tried to run
sudo docker-compose logs -f –tail=200 rspam-mailcow
but without any output. Should this command work similar to the postfix command?
I also checked the UI logs page but this is also empty.
![](https://community.mailcow.email/assets/files/2023-06-26/1687760001-274285-image.png)
Looks for me like rspam is not running correct. The container itself is running and also restarting the container via GUI didn’t help.
How can I dive deeper into the rspam container for troubleshooting? How can I check if the container is reachable via network? Maybe it as a problem with the uplink mapping or the DNS name after the “new” network adapter for the VM?
PS:
Accessing the rspam UI doesn’t work: https://my.domain/rspamd/ after some seconds it shows![](https://community.mailcow.email/assets/files/2023-06-26/1687760704-904872-image.png)
The steps in this image seems to be more general not related to rspam. Anyway I see no errors in the stated logs.
One addition I have to correct “I see no errors” in the log-command of error message of rspam UI.
I see this HTTP 502:
mailcowdockerized-nginx-mailcow-1 | 5.1.87.87 - - [26/Jun/2023:08:24:02 +0200] “GET /rspamd/ HTTP/1.0” 502 2038 “-” “GuzzleHttp/7”