Viktor Dukhovni <postfix-us...@dukhovni.org> wrote:
> On Wed, Apr 20, 2022 at 08:26:16PM -0400, Viktor Dukhovni wrote:
>>> this is postfix 3.8-20220325 (FreeBSD port postfix-current) on FreeBSD
>>> 13.1-STABLE.
>>
>> You could install the "postfix" rather than "postfix-current" port.
>> I have:
>>
>> -rw-r--r-- 1 root wheel 13544 Mar 17 17:23
>> /usr/ports/mail/postfix/Makefile
>> -rw-r--r-- 1 root wheel 13809 Mar 17 17:23
>> /usr/ports/mail/postfix-current/Makefile
>
> Which are:
>
> /usr/ports/mail/postfix-current/Makefile:DISTVERSION= 3.8-20220325
> /usr/ports/mail/postfix/Makefile:DISTVERSION= 3.7.0
I had had 3.7.0 running until recently and upgraded to 3.8-20220325 because of
those 'signal 11' messages.
I did some investigation of my log files with the result that the first 'signal
11' messages were reported the day after I upgraded from 3.6.3 to 3.7.0:
2022-03-17 changes in jail mail:
-openssl-1.1.1m_2,1 TLSv1.3 capable SSL and crypto library
+openssl-1.1.1n,1 TLSv1.3 capable SSL and crypto library
+pcre2-10.39 Perl Compatible Regular Expressions
library, version 2
-postfix-3.6.3,1 Secure alternative to widely-used
Sendmail
+postfix-3.7.0_1,1 Secure alternative to widely-used
Sendmail
2022-03-18 first entry:
process /usr/local/libexec/postfix/postscreen pid xxxxx killed by
signal 11
FYI: Both service jails of mine running postfix are of identical setup, but run
on different cloud instances at different locations. These postfix instances
are dealing with very low traffic, namely 40-1000 connects each day. Both
instances started throwing 'signal 11' messages the day after my upgrades from
3.6 to 3.7/3.8.
HTH and regards,
Michael
