[pfx] Re: Inconsistent failure pattern with smtp_tls_wrappermode

On Fri, Apr 11, 2025 at 05:08:39PM +, Jeff Kletsky via Postfix-users wrote: > 2025 Apr 11 00:27:36.696 -07:00 mx1 warning: postfix/relay/smtp[69584]:  > warning: smtp_tls_wrappermode requires "smtp_tls_security_level = encrypt" > (or stronger) The warning is clear enough, to use "wrapper mode

[pfx] Re: pipe service program failing (signal handler?)

berg...@panix.com: > => Postfix does nothing to prevent a child process from making a system > => call. For blocked calls, you may find more useful info in SeLinux > => or AppArmor event logs. > > SELinux is disabled and AppArmor is not installed on this system. > > There's no problem running gm

[pfx] Re: pipe service program failing (signal handler?)

bergman--- via Postfix-users: > I'm trying to use gmi (https://github.com/gauteh/lieer#gmailieer) as a > pipe service under Postfix 3.9.0. > > The gmi part itself works correctly via the shell, and postfix works > correctly to transport mail to other services defined in master.cf as > SMTP sites.

[pfx] Re: insert multi-line values into header

So... shifting the conversation away from "how to insert multi-line values" to "how did this happen"? We have a web app that uses a wildcard redirect. Some subdomains may be legit i.e.. saturday.domain.com, this would go to a specific site for the saturday.domain.com site, but the redirect also

[pfx] pipe service program failing (signal handler?)

I'm trying to use gmi (https://github.com/gauteh/lieer#gmailieer) as a pipe service under Postfix 3.9.0. The gmi part itself works correctly via the shell, and postfix works correctly to transport mail to other services defined in master.cf as SMTP sites. The entry in master.cf is: gmail

[pfx] Re: Inconsistent failure pattern with smtp_tls_wrappermode

On 2025-04-11 at 13:08:39 UTC-0400 (Fri, 11 Apr 2025 17:08:39 +) Jeff Kletsky via Postfix-users is rumored to have said: > We recently changed hosting for our perimeter MTAs and also switched to > SMTPS, based recent standards-track RFCs. The only Standards Track RFC that recommends SMTPS i

[pfx] Inconsistent failure pattern with smtp_tls_wrappermode

We recently changed hosting for our perimeter MTAs and also switched to SMTPS, based recent standards-track RFCs. As I can "solve the problem" by going with STARTTLS, this is more of a bug report than a request to solve the problem. (I'm now aware that the opinions on wrapper vs. STARTTLS vary.