On Sun, Nov 22, 2015 at 06:49:51PM -0800, Quanah Gibson-Mount wrote: > I'm currently testing out migrating to postfix 3.0.3. However, LMTP > delivery is failing due to:
Same OpenSSL library??? Seems implausible. > Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: SSL_connect error to > zre-ldap002.eng.zimbra.com[10.137.242.52]:7025: -1 > Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: warning: TLS library > problem: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert > handshake failure:s23_clnt.c:757: The server returns a fatal alert in response to the client's TLS HELLO. > Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: 7B8A411607DC: > to=<[email protected]>, > relay=zre-ldap002.eng.zimbra.com[10.137.242.52]:7025, delay=0.04, > delays=0.03/0.01/0.01/0, dsn=4.7.5, status=deferred (Cannot start TLS: > handshake failure) This is normal, with 3.0.0 cleartext fallback happens only after a message is retried, not on the initial connection. The real problem to fix here is the server's failure to interoperate. > lmtp_tls_security_level = may > > On my 2.11.4 postfix systems, with lmtp_tls_security_level set to may, > deliver works fine even though startTLS is not enabled. I.e., this seems > to be a regression since 2.11.4 This is not a regression. The 3.0 RELEASE-NOTES (which you undoubtedly read :-), say: [Feature 20140209] the Postfix SMTP client now also falls back to plaintext when TLS fails AFTER the TLS protocol handshake. [Feature 20140218] The Postfix SMTP client now requires that a queue file is older than $minimal_backoff_time, before falling back from failed TLS to plaintext (both during or after the TLS handshake). -- Viktor.
