> On 31 May 2024, at 14:53, Wietse Venema <wie...@porcupine.org> wrote:
>
> Gerben Wierda via Postfix-users:
>>
>>> On 31 May 2024, at 13:20, pat...@patpro.net wrote:
>>>
>>> Hello,
>>>
>>> Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
>>> errors/abuse/half-baked connections?
>>
>> Not blacklisting as I understand it, but as HAproxy makes a connection to
>> test if the service is up and then breaks the connection I always see this
>> on both systems:
>>
>> On the postfix 3.9 instance
>> May 26 05:31:33 hermione submission_haproxy/smtpd[21485]: connect from
>> router.rna.nl[192.168.2.2]
>> May 26 05:31:33 hermione submission_haproxy/smtpd[21485]: improper command
>> pipelining after CONNECT from router.rna.nl[192.168.2.2]: QUIT\r\n
>> May 26 05:31:33 hermione submission_haproxy/smtpd[21485]: disconnect from
>> router.rna.nl[192.168.2.2] commands=0/0
>
> Yep, turn off smtpd_forbid_unauth_pipelining and try again..
>
> Wietse
Actually, changing the health check on submission to
"PROXY TCP4 192.168.2.2 192.168.2.2 65535 587\r\n"
(without the added "QUIT\r\n") did the trick as well. It might have been that
in a previous situation HAproxy would 'never' finish the health check, I don't
recall why I added "QUIT\r\n". Maybe it is needed for postscreen or dovecot and
I just copied it to all and now it stopped working for submission.
G
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
