Re: smtpd_milter_maps and XFORWARD

2022-04-20 Thread Jesper Dybdal
On 2022-04-08 16:22, Wietse Venema wrote: Jesper Dybdal: I run Amavis as a before-queue filter, and opendmarc in the after-Amavis smtpd instance. Why not use Amavis as a before-queue MILTER? Then there is no need to propagate remote SMTP client info through non-Postfix programs. Thanks for the

Re: smtpd_milter_maps and XFORWARD

2022-04-20 Thread Wietse Venema
Jesper Dybdal: > On 2022-04-08 16:22, Wietse Venema wrote: > > Jesper Dybdal: > >> I run Amavis as a before-queue filter, and opendmarc in the after-Amavis > >> smtpd instance. > > Why not use Amavis as a before-queue MILTER? Then there is no need > > to propagate remote SMTP client info through no

warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Michael Grimm
Hi, this is postfix 3.8-20220325 (FreeBSD port postfix-current) on FreeBSD 13.1-STABLE. I do find comparable entries in my logfiles that I do not understand, honestly, like: Apr 20 06:36:23 mail.lan postfix/postscreen[74803]: CONNECT from [1.2.3.4]:45534 to [10.1.1.1]:25 Apr 20 06:36:23 mai

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Wietse Venema
Michael Grimm: > Hi, > > this is postfix 3.8-20220325 (FreeBSD port postfix-current) on FreeBSD > 13.1-STABLE. > > I do find comparable entries in my logfiles that I do not understand, > honestly, like: The text from the remote client is encoded in octal, the way that C programs used to do suc

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Michael Grimm
Wietse Venema wrote: > Michael Grimm: >> this is postfix 3.8-20220325 (FreeBSD port postfix-current) on FreeBSD >> 13.1-STABLE. >> >> I do find comparable entries in my logfiles that I do not understand, >> honestly, like: > > The text from the remote client is encoded in octal, the way that

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Viktor Dukhovni
> > On 20 Apr 2022, at 4:20 pm, Michael Grimm wrote: > > Apr 20 06:36:27 mail.lan postfix/postscreen[74803]: PREGREET 429 > after 0 from [1.2.3.4]:49074: > \026\003\003\001\250\001\000\001\244\003\003\327j\316\343\332\272\233\200\236\017\243`\342e\217\204\ That looks like a TLS client HELLO.

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Wietse Venema
Viktor Dukhovni: > > > On 20 Apr 2022, at 4:20 pm, Michael Grimm wrote: > > > > Apr 20 06:36:27 mail.lan postfix/postscreen[74803]: PREGREET > > 429 after 0 from [1.2.3.4]:49074: > > \026\003\003\001\250\001\000\001\244\003\003\327j\316\343\332\272\233\200\236\017\243`\342e\217\204\ > > That

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Michael Grimm
Wietse Venema wrote: > Viktor Dukhovni: >> That looks like a TLS client HELLO. Perhaps the client is misconfigured and >> using >> wrapper mode on port 25 instead of 465... > > It should not matter. postscreen is designed to handle random garbage. > > If you could test withg Postfix 3.6 then

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Viktor Dukhovni
On Wed, Apr 20, 2022 at 10:20:56PM +0200, Michael Grimm 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/p

Re: warning: process /usr/local/libexec/postfix/postscreen pid xxxxx killed by signal 11

2022-04-20 Thread Viktor Dukhovni
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 >