Hello,
ofc NOT. But that then works.
Danke Ömer!
Am 19.04.2025 um 17:18 schrieb Ömer Güven:
mx2.neumuenster.de may
Have you tried:
neumuenster.de may
Best,
Ömer
Am 19.04.2025 um 17:15 schrieb Florian Piekert via Postfix-users
<postfix-users@postfix.org>:
Dear Postfixians,
I have noticed the following.
In main.cf I had
#smtp_tls_security_level = may
smtp_tls_security_level = encrypt
for a while, until just now. When I noticed that some target mx destination had
delivery issues with this, I put the exception in my smtp_tls_policy_maps file,
prior postfix-tlspol.
However, even with the exception
mx2.neumuenster.de may
in the tls_policy... file, I received
Apr 19 16:57:39 theater postfix/smtp[103385]: A2235122AC02: enabling PIX
workarounds: disable_esmtp for mx2.neumuenster.de[212.7.145.246]:25
Apr 19 16:57:39 theater postfix/smtp[103385]: A2235122AC02:
to=<testu...@neumuenster.de>, relay=mx2.neumuenster.de[212.7.145.246]:25,
delay=1.7, delays=1.7/0.01/0.07/0, dsn=5.7.4, status=bounced (TLS is required, but
was not offered by host mx2.neumuenster.de[212.7.145.246])
Meaning, the exception did not seem to get used.
Is this, possibly, depending on the PIC workaround that pf enabled for whatever
reason?
IF I switch
smtp_tls_security_level = may
#smtp_tls_security_level = encrypt
in main.cf
it delivers just fine to that server.
Viktor/Wietse? My mistake or combination thing with the PIX workaround?
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
