Christophe Kalt via Postfix-users:
> Hi,
>
> I'm seeing regular postscreen segfaults on a test server with minimal
> traffic. The patterns I noticed from the logs is that it seems to happen
> when the server gets 2 ~simultaneous connections from the same host:
>
> 2024-02-04T14:33:31.876390 info postfix starting the Postfix mail system
> 2024-02-04T14:33:31.882441 info postfix daemon started -- version 3.8.4,
> configuration /etc/postfix
> 2024-02-04T14:34:02.888310 info postfix cache
> lmdb:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0
> entries
> 2024-02-04T14:34:02.890666 info postfix CONNECT from [91.239.130.97]:42190
> to [172.16.X.Y]:25
> 2024-02-04T14:34:02.890879 info postfix CONNECT from [91.239.130.97]:42196
> to [172.16.X.Y]:25
> 2024-02-04T14:34:02.890966 info postfix HANGUP after 0 from
> [91.239.130.97]:42190 in tests before SMTP handshake
> 2024-02-04T14:34:02.890989 info postfix DISCONNECT [91.239.130.97]:42190
> 2024-02-04T14:34:02.928708 warning postfix warning: process
> /usr/libexec/postfix/postscreen pid 93 killed by signal 11
postcreen source code has not changed since postfix-3.8.0:
$ diff -ur postfix-3.8.0/src/postscreen postfix-3.8.5/src/postscreen
[no output]
The SMTP smuggling changes are in code that is not used in postscreen.
postscreen has a different SMTP engine implementation.
I therefore suspect a bad build, or bad library dependency.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
