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

Viktor Dukhovni 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

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

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

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

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

SRS and sender_dependent_relayhost_maps

Hello, I'm trying to implement SRS using postsrsd. Since it always rewrites non-local sender (even for incoming mail) I'm trying to restrict it only for outgoing mail. I managed configuring local SMTP server (alternative port) that rewrites sender using canonical_maps, but: I would like on

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

Wietse Venema wrote: > 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 g

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

Would these commands make a difference (for Postfix 3.7 or 3.8): postconf -P smtp/inet/smtputf8_enable=no postfix reload There have been some invasive changes in postscreen 3.7 that imvolve the handling of SMTPUTF8 in SMTP commands. Postfix 3.6 did not care. Wietse

Workaround for sender address rejected: domain not found

I've seen this a few times with some companies. I'm expecting an email from, say, example.com They say it's bouncing. I check the logs and there's a RCPT 450 Sender address rejected: domain not found. The email is being sent from email.example.com, but that subdomain doesn't exist, can't be pinged

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

Michael Grimm: > > You have already mentined that the problem started after you > > updated from 3.6 to 3.7. > > Yes, postfix 3.6 didn't trigger my problem. > > But I wonder, if that the simultaneous upgrade of the openssl > package might be the cause of postscreen's dying after that "TLS > rand

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

Wietse Venema wrote > Would these commands make a difference (for Postfix 3.7 or 3.8): > > postconf -P smtp/inet/smtputf8_enable=no > postfix reload Done. Please give me 24/48 hours to respond, because these events are not that often ... Thanks and with kind regards, Michael

Re: Workaround for sender address rejected: domain not found

On 2022-04-21 at 16:34:38 UTC-0400 (Thu, 21 Apr 2022 16:34:38 -0400) Ian Evans is rumored to have said: I've seen this a few times with some companies. I'm expecting an email from, say, example.com They say it's bouncing. I check the logs and there's a RCPT 450 Sender address rejected: domain

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

Michael Grimm: > Wietse Venema wrote > > > Would these commands make a difference (for Postfix 3.7 or 3.8): > > > > postconf -P smtp/inet/smtputf8_enable=no > > postfix reload > > Done. Please give me 24/48 hours to respond, because these events > are not that often ... When I delete the posts

Re: Workaround for sender address rejected: domain not found

On 4/21/2022 3:34 PM, Ian Evans wrote: I've seen this a few times with some companies. I'm expecting an email from, say, example.com They say it's bouncing. I check the logs and there's a RCPT 450 Sender address rejected: domain not found. The email is being sent from e

Re: Workaround for sender address rejected: domain not found

On Thu, Apr 21, 2022 at 5:19 PM Noel Jones wrote: > > On 4/21/2022 3:34 PM, Ian Evans wrote: > > I've seen this a few times with some companies. I'm expecting an > > email from, say, example.com > > > > They say it's bouncing. I check the logs and there's a RCPT 450 > > Sende

Re: Workaround for sender address rejected: domain not found

On 2022-04-21 at 18:31:56 UTC-0400 (Thu, 21 Apr 2022 18:31:56 -0400) Ian Evans is rumored to have said: [...] smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/valid_senders, reject_unknown_sender_domain So, you're already set up for exempting senders listed in /etc/post

Re: SRS and sender_dependent_relayhost_maps

On 2022-04-21 17:51, Matus UHLAR - fantomas wrote: I'm trying to keep configuration and mail flow as simple as possible. so dont use SRS ?