On Fri, May 31, 2024 at 01:06:20PM +0200, Gerben Wierda via Postfix-users wrote:
> Hmm, I just noticed (all outgoing smtp was going to a backup server
> that works) that one of my postfix instances cannot send mail (smtp
> doesn't work, postscreen and smtpd work fine).
What *exactly* do you mean by "smtp" doesn't work? What concrete
evidence can you post to substantiate and detail this?
> # submission (587)
> submission inet n - n - - smtpd
> -o smtpd_tls_security_level=encrypt
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_tls_auth_only=yes
> -o syslog_name=submission
> 990 inet n - n - - smtpd
> -o smtpd_tls_security_level=encrypt
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_tls_auth_only=yes
> -o syslog_name=submission_haproxy
> -o smtpd_upstream_proxy_protocol=haproxy
>
> The one that haproxy sees as down has been recently updated to postfix 3.9
Often, Postfix updates are part of a broader update of other system
packages, perhaps the issue is with one of those.
> So, HAproxy sees smtpd as up on postfix 3.9 but it sees smtp as down.
> In reality, both are up.
How could "haproxy" "see" "smtp" as down, the smtp(8) delivery agent
is not a network listener and haproxy does not connect to it. If you
mean incoming SMTP on port 25 (the "smtp/inet" service in master.cf),
that's still "smtpd", so best to not call it "smtp".
Also why not post that master.cf entry? And some logging for
"postfix/smtpd" (assuming default syslog_name).
> What should I do? Revert to postfix 3.8? I rather not, I rather would
> upgrade the other to 3.9 (but if I do that, I probably lose all smtp
> behind HAproxy for now)
Reverting Postfix is unlikely to help, Postfix is very stable software,
and a configuration that isn't working with 3.9 likely won't work also
with 3.8.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
