On Tue, May 06, 2014 at 10:49:20PM -0400, Sahil Tandon wrote: > We are experiencing a problem that seems to manifest *only* when > delivering to MXs that exhibit the SSL problem described by Viktor[1] > AND connection caching is enabled on demand.
That is when TLS handshakes fail and cleartext connections are made to deliver the mail. Such connections may be cached. Have you tried disabling TLS, but not the demand caching? Does the problem *only* lead to erroneous connection re-use via relays that are the result of a cleartext fallback? > [...] > This is 2.12-20140109. On what platform (FreeBSD per chance)? > I am still reviewing the > logs to understand this, but at first glance, it appears that we try to > deliver mail to MXs that (in DNS) are not associated with the > destination domain, e.g.: > > May 6 12:00:04 mx2 postfix/smtp[26171]: SSL_connect error to > iron1-mx.tops.gwu.edu[128.164.127.227]:25: -1 > May 6 12:00:04 mx2 postfix/smtp[26171]: warning: TLS library problem: > error:1407741A:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert decode > error:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c:762: > May 6 12:00:04 mx2 postfix/smtp[26171]: 4416951CD: Cannot start TLS: > handshake failure > ... Where are the rest of the logs for smtpd[26171] that show the retried cleartext delivery? > May 6 12:00:05 mx2 postfix/smtp[26118]: 751AE5215: > to=<[email protected]>, > relay=iron1-mx.tops.gwu.edu[128.164.127.227]:25, > conn_use=2, delay=3.3, delays=0.02/3.1/0.08/0.15, dsn=5.0.0, > status=bounced > (host iron1-mx.tops.gwu.edu[128.164.127.227] said: > 550 #5.1.0 Address rejected. (in reply to RCPT TO command)) > May 6 12:00:07 mx2 postfix/smtp[26240]: 3C02D52D2: > to=<[email protected]>, > relay=iron1-mx.tops.gwu.edu[128.164.127.227]:25, > conn_use=3, delay=3.9, delays=0.1/3.5/0.07/0.15, dsn=5.0.0, > status=bounced > (host iron1-mx.tops.gwu.edu[128.164.127.227] said: > 550 #5.1.0 Address rejected. (in reply to RCPT TO command)) > May 6 12:00:07 mx2 postfix/smtp[25609]: A9657525C: > to=<[email protected]>, > relay=iron1-mx.tops.gwu.edu[128.164.127.227]:25, > conn_use=4, delay=4.7, delays=0.01/4.5/0.07/0.15, dsn=5.0.0, > status=bounced > (host iron1-mx.tops.gwu.edu[128.164.127.227] said: > 550 #5.1.0 Address rejected. (in reply to RCPT TO command)) The metadata for the cached connection from scache(8) indeed seems inconsistent with the expected request. You may need to enable "-v" in scache, to observe requests and responses. > May 6 10:31:44 mx2 postfix/smtp[6133]: SSL_connect error to > smtp.citrix.com[66.165.176.89]:25: -1 > May 6 10:31:44 mx2 postfix/smtp[6133]: warning: TLS library problem: > error:1407741A:SSL > routines:SSL23_GET_SERVER_HELLO:tlsv1 alert decode > error:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c:762: > May 6 10:31:44 mx2 postfix/smtp[6133]: 59013110C: Cannot start TLS: > handshake failure > ... Once again, where is the rest of the that delivery? > May 6 10:31:47 mx2 postfix/smtp[5241]: 9AC2B1145: > to=<[email protected]>, relay=smtp.citrix.com[66.165.176.89]:25, > conn_use=2, delay=63, delays=0.11/62/0.2/0.39, dsn=5.0.0, > status=bounced (host smtp.citrix.com[66.165.176.89] said: 550 #5.1.0 > Address rejected. (in reply to RCPT TO command)) > May 6 10:31:48 mx2 postfix/smtp[5918]: A9BD01152: > to=<[email protected]>, relay=smtp.citrix.com[66.165.176.89]:25, > conn_use=3, delay=64, delays=0.11/63/0.21/0.46, dsn=5.0.0, > status=bounced (host smtp.citrix.com[66.165.176.89] said: 550 #5.1.0 > Address rejected. (in reply to RCPT TO command)) > May 6 10:31:49 mx2 postfix/smtp[6082]: EDFBF1181: > to=<[email protected]>, relay=smtp.citrix.com[66.165.176.89]:25, > conn_use=4, delay=64, delays=0.16/64/0.21/0.39, dsn=5.0.0, > status=bounced (host smtp.citrix.com[66.165.176.89] said: 550 #5.1.0 > Address rejected. (in reply to RCPT TO command)) There seems to be corruption in the scache client or server. -- Viktor.
