com postfix_container: Aug 23 00: 02: 06 example postfix/ smtpd: connect from unknownĪug 23 00: 02: 07 example. com postfix_container: Aug 23 00: 02: 04 example postfix/ smtpd: disconnect from unknown ehlo= 1 auth= 0/ 1 quit= 1 commands= 2/ 3Īug 23 00: 02: 06 example. com postfix_container: Aug 23 00: 02: 04 example postfix/ smtpd: warning: unknown: SASL LOGIN authentication failed: authentication fai>Īug 23 00: 02: 04 example. com postfix_container: Aug 23 00: 02: 02 example postfix/ smtpd: disconnect from unknown commands= 0/ 0Īug 23 00: 02: 04 example. com postfix_container: Aug 23 00: 02: 02 example postfix/ smtpd: lost connection after CONNECT from unknownĪug 23 00: 02: 02 example. com postfix_container: Aug 23 00: 02: 02 example postfix/ smtpd: connect from unknownĪug 23 00: 02: 02 example. There are more steps to have postfix log to stdout.Īug 23 00: 02: 02 example. com postfix/ anvil: statistics: max connection count 1 for ( smtp: xxx. com postfix/ anvil: statistics: max connection rate 4/ 60 s for ( smtp: xxx. com postfix/ smtpd: disconnect from unknown ehlo= 1 auth= 0/ 1 quit= 1 commands= 2/ 3Īug 23 00: 05: 32 example. com postfix/ smtpd: warning: unknown: SASL LOGIN authentication failed: authentication fai>Īug 23 00: 02: 11 example. com postfix/ smtpd: connect from unknownĪug 23 00: 02: 10 example. com postfix/ smtpd: disconnect from unknown ehlo= 1 auth= 0/ 1 quit= 1 commands= 2/ 3Īug 23 00: 02: 09 example. com postfix/ smtpd: warning: unknown: SASL LOGIN authentication failed: authentication fai>Īug 23 00: 02: 07 example. com postfix/ smtpd: connect from unknownĪug 23 00: 02: 07 example. com postfix/ smtpd: disconnect from unknown ehlo= 1 auth= 0/ 1 quit= 1 commands= 2/ 3Īug 23 00: 02: 06 example. com postfix/ smtpd: warning: unknown: SASL LOGIN authentication failed: authentication fai>Īug 23 00: 02: 04 example.

com postfix/ smtpd: disconnect from unknown commands= 0/ 0Īug 23 00: 02: 04 example. com postfix/ smtpd: lost connection after CONNECT from unknownĪug 23 00: 02: 02 example. com postfix/ smtpd: connect from unknownĪug 23 00: 02: 02 example. Following will make all docker logs, including container stdout, go into journald.Īug 23 00: 02: 02 example. Docker Logĭocker support multiple ways of logging. With only a single Tiny VPS, I decided to stick with logwatch and make it work with postfix again. However those type of setup are for multiple servers, and most importantly, by no means tiny! It is common for containerized environment shipping logs to centralize server and processed by analytic tools like Elastic Stack. Part 5 - Docker, Postfix, Journald & Logwatch Part 2 - Non-Linux Outgoing SMTP Account.Setting $all to Required-Start for postfix SysV did not fix my issue. # Short-Description: start and stop service my-serviceĪnd there is an $all keyboard, which according to documentation, should mark this service as being started after everything else, but is this 'everything else' all the systemd services or services that only have sysV scripts? # Required-Stop: $local_fs $network $remote_fs # Required-Start: $local_fs $network $remote_fs I did see the couple of 'keywords' I can use in the SysV script: # BEGIN INIT INFO Question is, how can I make postfix depend on docker being started? Or to put it more generically, how can i make a service which does not have a native systemd service unit file depend on a service that does have one. If postfix had a native systemd service unit file, I would just make it require rvice, but postfix has SysV script, which systemd translates into service unit during boot. Problem is that postfix starts before docker and throws an error about the network not being there, which is true because rvice did not start yet, and therefore ignores it. In order for this to work, I have to add the docker network to postfix's main.cf file. I have configured that a docker container sends email using the host's smtp (postfix).

Postfix docker syslog