Health check of postfix without the logging noise

Currently, every time haproxy checks if postfix is still alive, e.g. on port 587, I see this in my logging: Jan 28 13:13:20 albus submission/smtpd[97331]: warning: haproxy read: EOF Jan 28 13:13:20 albus submission/smtpd[97331]: connect from unknown[unknown] Jan 28 13:13:20 albus submission/smtpd

Re: Health check of postfix without the logging noise

Gerben Wierda: > Currently, every time haproxy checks if postfix is still alive, > e.g. on port 587, I see this in my logging: > > Jan 28 13:13:20 albus submission/smtpd[97331]: warning: haproxy read: EOF > Jan 28 13:13:20 albus submission/smtpd[97331]: connect from unknown[unknown] > Jan 28 13:13

Bounces from gmail

Amateur mail-admin here (I know, don't do that) . I have a redirect to gmail set up for two users, and at times this happens: 1) The relayhost ("smarthost") I use, my internet provider, will accept the mail for gmail. 2) Gmail rejects the mail as spam. 3) Relayhost bounces mail back at me.

Re: Health check of postfix without the logging noise

> On 28 Jan 2023, at 13:40, Wietse Venema wrote: > > Gerben Wierda: >> Currently, every time haproxy checks if postfix is still alive, >> e.g. on port 587, I see this in my logging: >> >> Jan 28 13:13:20 albus submission/smtpd[97331]: warning: haproxy read: EOF >> Jan 28 13:13:20 albus submissi

Re: Health check of postfix without the logging noise

Gerben Wierda: > > A proper health check verifies that a service actually responds. > > True. > > > You can find more with "haproxy health check script". For example, > > Postfix should reply with a "220" status within 5 seconds. > > Thanks, I have been looking at how to set this up, but so far

Re: Health check of postfix without the logging noise

> On 28 Jan 2023, at 14:53, Wietse Venema wrote: > > Gerben Wierda: >>> A proper health check verifies that a service actually responds. >> >> True. >> >>> You can find more with "haproxy health check script". For example, >>> Postfix should reply with a "220" status within 5 seconds. >> >> T

Re: Health check of postfix without the logging noise

Currently, every time haproxy checks if postfix is still alive, e.g. on port 587, I see this in my logging: Jan 28 13:13:20 albus submission/smtpd[97331]: warning: haproxy read: EOF Jan 28 13:13:20 albus submission/smtpd[97331]: connect from unknown[unknown] Jan 28 13:13:20 albus submission/smtp

Re: Health check of postfix without the logging noise

> On 28 Jan 2023, at 17:26, post...@ptld.com wrote: > >> Currently, every time haproxy checks if postfix is still alive, e.g. on port >> 587, I see this in my logging: >> Jan 28 13:13:20 albus submission/smtpd[97331]: warning: haproxy read: EOF >> Jan 28 13:13:20 albus submission/smtpd[97331]:

Re: Health check of postfix without the logging noise

On 2023-01-28 at 11:32:11 UTC-0500 (Sat, 28 Jan 2023 17:32:11 +0100) Gerben Wierda is rumored to have said: On 28 Jan 2023, at 17:26, post...@ptld.com wrote: Currently, every time haproxy checks if postfix is still alive, e.g. on port 587, I see this in my logging: Jan 28 13:13:20 albus submi

append_dot_mydomain, how to make it work

I've tried just about every combination of these configs from the docs: append_dot_mydomain (default: Postfix ≥ 3.0: no, Postfix < 3.0: yes) With locally submitted mail, append the string ".$mydomain" to addresses that have no ".domain" informati