On Sat, Jan 03, 2026 at 13:18:01 -0800, Fred Morris via Postfix-users wrote:
> I don't see how they can be more brain-damaged than they already are,
> they're already looping:
>
> 2026-01-02T17:36:15.671360-08:00 flame postfix/smtpd[4447]: connect from
> scan.cypex.ai[3.137.73.221]
> 2026-01-02T17:36:15.672050-08:00 flame postfix/smtpd[4447]: warning:
> non-SMTP command from scan.cypex.ai[3.137.73.221]: GET / HTTP/1.1
> 2026-01-02T17:36:15.672419-08:00 flame postfix/smtpd[4447]: disconnect
> from scan.cypex.ai[3.137.73.221] unknown=0/1 commands=0/1
> 2026-01-02T17:37:34.445451-08:00 flame postfix/smtpd[4447]: connect from
> scan.cypex.ai[3.137.73.221]
> 2026-01-02T17:37:34.446043-08:00 flame postfix/smtpd[4447]: warning:
> non-SMTP command from scan.cypex.ai[3.137.73.221]: GET / HTTP/1.1
> 2026-01-02T17:37:34.446334-08:00 flame postfix/smtpd[4447]: disconnect
> from scan.cypex.ai[3.137.73.221] unknown=0/1 commands=0/1
In this case the connection is already closed by
smtpd_forbid_unauth_pipelining=yes, regardless of
smtpd_delay_reject setting.
Geert
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
