Hopefully I’m right so far in narrowing this down… I can’t seem to figure out why, but Postfix and Dovecot appear to be killed repeatedly by watchdog-mailcow (except that i’ve also tried disabling that, and it still happens). At least the issue seems repetitive, so i should be able to keep the logs short. Help towards just trying to troubleshoot this would be extremely appreciated.
Server was running 2025-07 before postfix and dovecot started having issues, then was upgraded to 2026-03 during the process of troubleshooting it. Certs are pulled in from another server that runs certbot with Let’s Encrypt (I could not get that working either). Logs included below, can provide more if needed. I’ve been working on this all day now, hopefully I’m not missing something obvious. Also, is there a way to get more detail than this? I feel like I’m missing what is giving the containers a SIGTERM.
Postfix Log
postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus!
postfix-mailcow-1 | Using the open Spamhaus blocklists.
postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory
postfix-mailcow-1 | 2026-03-11 20:49:48,169 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | 2026-03-11 20:49:48,169 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | Mar 11 20:49:50 cf75ffbf4713 postfix/postfix-script[355]: starting the Postfix mail system
postfix-mailcow-1 | Mar 11 20:49:50 cf75ffbf4713 postfix/master[357]: daemon started -- version 3.7.11, configuration /opt/postfix/conf
postfix-mailcow-1 | 2026-03-11 20:49:52,099 WARN received SIGTERM indicating exit request
postfix-mailcow-1 | 2026-03-11 20:49:52,099 INFO waiting for processes, postfix, syslog-ng to die
postfix-mailcow-1 | Mar 11 20:49:52 cf75ffbf4713 syslog-ng[10]: syslog-ng shutting down; version='3.38.1'
postfix-mailcow-1 | 2026-03-11 20:49:52,205 INFO stopped: syslog-ng (exit status 0)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 WARN stopped: postfix (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 INFO reaped unknown pid 357 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 INFO reaped unknown pid 358 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 INFO reaped unknown pid 359 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 INFO reaped unknown pid 361 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,208 INFO reaped unknown pid 362 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:53,210 WARN stopped: processes (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:49:54,533 INFO Set uid to user 0 succeeded
postfix-mailcow-1 | 2026-03-11 20:49:54,537 INFO supervisord started with pid 1
postfix-mailcow-1 | 2026-03-11 20:49:55,542 INFO spawned: 'processes' with pid 8
postfix-mailcow-1 | 2026-03-11 20:49:55,547 INFO spawned: 'postfix' with pid 9
postfix-mailcow-1 | 2026-03-11 20:49:55,553 INFO spawned: 'syslog-ng' with pid 10
postfix-mailcow-1 | Uptime: 1889 Threads: 9 Questions: 7326 Slow queries: 0 Opens: 70 Open tables: 63 Queries per second avg: 3.878
postfix-mailcow-1 | Mar 11 20:49:55 cf75ffbf4713 syslog-ng[10]: syslog-ng starting up; version='3.38.1'
postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
postfix-mailcow-1 | The AS of your IP is NOT listed as a banned AS from Spamhaus!
postfix-mailcow-1 | Using the open Spamhaus blocklists.
postfix-mailcow-1 | chown: cannot access '/usr/share/man/man1/mailq.1.gz': No such file or directory
postfix-mailcow-1 | 2026-03-11 20:49:56,954 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | 2026-03-11 20:49:56,954 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix-mailcow-1 | Mar 11 20:49:59 cf75ffbf4713 postfix/postfix-script[355]: starting the Postfix mail system
postfix-mailcow-1 | Mar 11 20:49:59 cf75ffbf4713 postfix/master[357]: daemon started -- version 3.7.11, configuration /opt/postfix/conf
postfix-mailcow-1 | 2026-03-11 20:50:00,173 WARN received SIGTERM indicating exit request
postfix-mailcow-1 | 2026-03-11 20:50:00,174 INFO waiting for processes, postfix, syslog-ng to die
postfix-mailcow-1 | Mar 11 20:50:00 cf75ffbf4713 syslog-ng[10]: syslog-ng shutting down; version='3.38.1'
postfix-mailcow-1 | 2026-03-11 20:50:00,287 INFO stopped: syslog-ng (exit status 0)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 WARN stopped: postfix (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 INFO reaped unknown pid 357 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 INFO reaped unknown pid 358 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 INFO reaped unknown pid 359 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 INFO reaped unknown pid 360 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,290 INFO reaped unknown pid 362 (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:01,292 WARN stopped: processes (terminated by SIGTERM)
postfix-mailcow-1 | 2026-03-11 20:50:02,512 INFO Set uid to user 0 succeeded
postfix-mailcow-1 | 2026-03-11 20:50:02,515 INFO supervisord started with pid 1
postfix-mailcow-1 | 2026-03-11 20:50:03,519 INFO spawned: 'processes' with pid 9
postfix-mailcow-1 | 2026-03-11 20:50:03,524 INFO spawned: 'postfix' with pid 10
postfix-mailcow-1 | 2026-03-11 20:50:03,529 INFO spawned: 'syslog-ng' with pid 11
postfix-mailcow-1 | Uptime: 1897 Threads: 9 Questions: 7365 Slow queries: 0 Opens: 70 Open tables: 63 Queries per second avg: 3.882
postfix-mailcow-1 | Mar 11 20:50:03 cf75ffbf4713 syslog-ng[11]: syslog-ng starting up; version='3.38.1'
Dovecot Log
dovecot-mailcow-1 | Uptime: 1883 Threads: 9 Questions: 7312 Slow queries: 0 Opens: 70 Open tables: 63 Queries per second avg: 3.883
dovecot-mailcow-1 | Detecting SKIP_FTS=y... not enabling Flatcurve (FTS) then...
dovecot-mailcow-1 | grep: /etc/dovecot/extra.conf: No such file or directory
dovecot-mailcow-1 | % Total % Received % Xferd Average Speed Time Time Time Current
dovecot-mailcow-1 | Dload Upload Total Spent Left Speed
100 129k 100 129k 0 0 128k 0 0:00:01 0:00:01 --:--:-- 128k
dovecot-mailcow-1 | 20_blatspammer.cf
dovecot-mailcow-1 | 70_HS_body.cf
dovecot-mailcow-1 | 70_HS_header.cf
dovecot-mailcow-1 | 2026-03-11 20:49:51,973 INFO Set uid to user 0 succeeded
dovecot-mailcow-1 | 2026-03-11 20:49:51,977 INFO supervisord started with pid 1
dovecot-mailcow-1 | 2026-03-11 20:49:52,983 INFO spawned: 'processes' with pid 110
dovecot-mailcow-1 | 2026-03-11 20:49:52,988 INFO spawned: 'dovecot' with pid 111
dovecot-mailcow-1 | 2026-03-11 20:49:52,992 INFO spawned: 'syslog-ng' with pid 112
dovecot-mailcow-1 | Mar 11 20:49:53 3758fdcc60af syslog-ng[112]: syslog-ng starting up; version='4.8.3'
dovecot-mailcow-1 | Mar 11 20:49:53 3758fdcc60af dovecot: master: Dovecot v2.3.21.1 (d492236fa0) starting up for imap, sieve, lmtp, pop3
dovecot-mailcow-1 | Mar 11 20:49:53 3758fdcc60af dovecot: auth-worker(130): conn unix:auth-worker (pid=129,uid=401): auth-worker<7>: sql(9rgxxuu2tisqtmcs@mailcow.local): unknown user
dovecot-mailcow-1 | Mar 11 20:49:53 3758fdcc60af dovecot: doveadm(9rgxxuu2tisqtmcs@mailcow.local): Error: User doesn't exist
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: lmtp(133): Connect from 172.22.1.13
dovecot-mailcow-1 | 2026-03-11 20:49:54,274 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | 2026-03-11 20:49:54,275 INFO success: dovecot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | 2026-03-11 20:49:54,275 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: auth-worker(130): conn unix:auth-worker (pid=129,uid=401): auth-worker<8>: sql(watchdog@invalid,172.22.1.13): unknown user
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: lmtp(133): Disconnect from 172.22.1.13: Logged out (state=MAIL FROM)
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=172.22.1.13, lip=172.22.1.250, TLS, TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=172.22.1.13, lip=172.22.1.250
dovecot-mailcow-1 | Mar 11 20:49:54 3758fdcc60af dovecot: managesieve-login: Disconnected: Connection closed (no auth attempts in 0 secs): user=<>, rip=172.22.1.13, lip=172.22.1.250
dovecot-mailcow-1 | 2026-03-11 20:49:55,369 WARN received SIGTERM indicating exit request
dovecot-mailcow-1 | 2026-03-11 20:49:55,370 INFO waiting for processes, dovecot, syslog-ng to die
dovecot-mailcow-1 | Mar 11 20:49:55 3758fdcc60af syslog-ng[112]: syslog-ng shutting down; version='4.8.3'
dovecot-mailcow-1 | 2026-03-11 20:49:55,481 INFO stopped: syslog-ng (exit status 0)
dovecot-mailcow-1 | 2026-03-11 20:49:56,593 INFO stopped: dovecot (exit status 0)
dovecot-mailcow-1 | 2026-03-11 20:49:56,594 WARN received SIGQUIT indicating exit request
dovecot-mailcow-1 | 2026-03-11 20:49:56,595 WARN stopped: processes (terminated by SIGTERM)
dovecot-mailcow-1 | Uptime: 1891 Threads: 9 Questions: 7331 Slow queries: 0 Opens: 70 Open tables: 63 Queries per second avg: 3.876
dovecot-mailcow-1 | Detecting SKIP_FTS=y... not enabling Flatcurve (FTS) then...
dovecot-mailcow-1 | grep: /etc/dovecot/extra.conf: No such file or directory
dovecot-mailcow-1 | % Total % Received % Xferd Average Speed Time Time Time Current
dovecot-mailcow-1 | Dload Upload Total Spent Left Speed
100 129k 100 129k 0 0 106k 0 0:00:01 0:00:01 --:--:-- 106k
dovecot-mailcow-1 | 20_blatspammer.cf
dovecot-mailcow-1 | 70_HS_body.cf
dovecot-mailcow-1 | 70_HS_header.cf
dovecot-mailcow-1 | 2026-03-11 20:50:00,847 INFO Set uid to user 0 succeeded
dovecot-mailcow-1 | 2026-03-11 20:50:00,850 INFO supervisord started with pid 1
dovecot-mailcow-1 | 2026-03-11 20:50:01,858 INFO spawned: 'processes' with pid 155
dovecot-mailcow-1 | 2026-03-11 20:50:01,864 INFO spawned: 'dovecot' with pid 156
dovecot-mailcow-1 | 2026-03-11 20:50:01,872 INFO spawned: 'syslog-ng' with pid 157
dovecot-mailcow-1 | Mar 11 20:50:01 3758fdcc60af syslog-ng[157]: syslog-ng starting up; version='4.8.3'
dovecot-mailcow-1 | Mar 11 20:50:02 3758fdcc60af dovecot: master: Dovecot v2.3.21.1 (d492236fa0) starting up for imap, sieve, lmtp, pop3
dovecot-mailcow-1 | Mar 11 20:50:02 3758fdcc60af dovecot: auth-worker(176): conn unix:auth-worker (pid=175,uid=401): auth-worker<7>: sql(3podcu81yditzbqu@mailcow.local): unknown user
dovecot-mailcow-1 | Mar 11 20:50:02 3758fdcc60af dovecot: doveadm(3podcu81yditzbqu@mailcow.local): Error: User doesn't exist
dovecot-mailcow-1 | 2026-03-11 20:50:03,374 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | 2026-03-11 20:50:03,374 INFO success: dovecot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | 2026-03-11 20:50:03,374 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
dovecot-mailcow-1 | 2026-03-11 20:50:03,375 WARN received SIGTERM indicating exit request
dovecot-mailcow-1 | 2026-03-11 20:50:03,375 INFO waiting for processes, dovecot, syslog-ng to die
dovecot-mailcow-1 | Mar 11 20:50:03 3758fdcc60af syslog-ng[157]: syslog-ng shutting down; version='4.8.3'
dovecot-mailcow-1 | 2026-03-11 20:50:03,486 INFO stopped: syslog-ng (exit status 0)
dovecot-mailcow-1 | 2026-03-11 20:50:04,594 INFO stopped: dovecot (exit status 0)
dovecot-mailcow-1 | 2026-03-11 20:50:04,594 INFO reaped unknown pid 169 (exit status 0)
dovecot-mailcow-1 | 2026-03-11 20:50:04,594 WARN received SIGQUIT indicating exit request
dovecot-mailcow-1 | 2026-03-11 20:50:04,595 WARN stopped: processes (terminated by SIGTERM)
Watchdog Log
watchdog-mailcow-1 | Wed Mar 11 20:49:19 EDT 2026 Container is running for less than 360 seconds, skipping action...
watchdog-mailcow-1 | Wed Mar 11 20:49:19 EDT 2026 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:19 EDT 2026 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:19 EDT 2026 Dovecot health level: 17% (2/12), health trend: -10
watchdog-mailcow-1 | Wed Mar 11 20:49:28 EDT 2026 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:28 EDT 2026 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:30 EDT 2026 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:38 EDT 2026 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:40 EDT 2026 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:40 EDT 2026 Postfix TLS Policy companion health level: 100% (8/8), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:41 EDT 2026 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:44 EDT 2026 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:54 EDT 2026 Dovecot health level: 25% (3/12), health trend: 1
watchdog-mailcow-1 | Wed Mar 11 20:49:55 EDT 2026 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:56 EDT 2026 MySQL/MariaDB health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:49:59 EDT 2026 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:03 EDT 2026 Clamd health level: 100% (15/15), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:08 EDT 2026 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:11 EDT 2026 Postfix health level: 13% (1/8), health trend: -4
watchdog-mailcow-1 | Wed Mar 11 20:50:18 EDT 2026 SOGo health level: 100% (3/3), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:20 EDT 2026 Rspamd health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:21 EDT 2026 Redis health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:28 EDT 2026 Dovecot health level: 33% (4/12), health trend: 1
watchdog-mailcow-1 | Wed Mar 11 20:50:29 EDT 2026 Mail queue health level: 100% (20/20), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:29 EDT 2026 Dovecot replication health level: 100% (20/20), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:29 EDT 2026 PHP-FPM health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:31 EDT 2026 Ratelimit health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:33 EDT 2026 Unbound health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:42 EDT 2026 Postfix TLS Policy companion health level: 100% (8/8), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:45 EDT 2026 Nginx health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:46 EDT 2026 ACME health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:48 EDT 2026 Fail2ban health level: 100% (1/1), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:52 EDT 2026 Clamd health level: 100% (15/15), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:50:52 EDT 2026 Dovecot health level: 42% (5/12), health trend: 1
watchdog-mailcow-1 | Wed Mar 11 20:51:01 EDT 2026 Olefy health level: 100% (5/5), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:51:05 EDT 2026 Postfix health level: 0% (0/8), health trend: -4
watchdog-mailcow-1 | Wed Mar 11 20:51:05 EDT 2026 Postfix TLS Policy companion health level: 100% (8/8), health trend: 0
watchdog-mailcow-1 | Wed Mar 11 20:51:06 EDT 2026 Postfix hit error limit
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000284s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000205s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000348s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000177s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000373s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000225s;;;0.000000
watchdog-mailcow-1 | Connection closed by server before sending QUIT command
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000208s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000249s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000213s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000322s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000188s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000385s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000227s;;;0.000000
watchdog-mailcow-1 | SMTP OK - 0.150 sec. response time|time=0.150227s;;;0.000000
watchdog-mailcow-1 | SMTP OK - 0.022 sec. response time|time=0.021609s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000470s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000193s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000374s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000197s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000417s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000178s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000412s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000180s;;;0.000000
watchdog-mailcow-1 | SMTP OK - 0.156 sec. response time|time=0.156171s;;;0.000000
watchdog-mailcow-1 | SMTP UNKNOWN - Cannot read EHLO response via TLS.
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000336s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000168s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000344s;;;0.000000
watchdog-mailcow-1 | connect to address 172.22.1.253 and port 589: Connection refused
watchdog-mailcow-1 | SMTP CRITICAL - 0.000 sec. response time|time=0.000219s;;;0.000000