Closed celesteking closed 8 years ago
Actually, able to reproduce when cipher doesn't match.
openssl s_client -connect $HOST:25 -starttls smtp -cipher DH-DSS-SEED-SHA
SSL Alert 42: bad certificate
There is a problem with the certificate, for example, a certificate is corrupt, or a certificate contains signatures that cannot be verified
Von meinem iPhone gesendet
Am 08.03.2016 um 20:16 schrieb celesteking notifications@github.com:
Essentially, see below. No idea why it didn't accept the cert.
[core] S: 250-xxx Hello m68-175.mailgun.net [166.78.68.175], Haraka is at your service. [core] S: 250-PIPELINING [core] S: 250-8BITMIME [core] S: 250-SIZE 50000000 [core] S: 250-AUTH PLAIN LOGIN [core] S: 250 STARTTLS [core] C: STARTTLS state=1
[core] running unrecognized_command hook in tls plugin [core] S: 220 Go ahead. [core] Upgrading to TLS [core] client [xxx] connection error: Error: 140597631096608:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:../deps/openssl/ openssl/ssl/s3_pkt.c:1300:SSL alert number 42 [core] running disconnect hooks .. 13:16:09 [core] disconnect ip=166.78.68.175 rdns="m68-175.mailgun.net" helo="m68-175.mailgun.net" relay=N early=N esmtp=Y tls=N pipe=N errors=0 txns=0 rcpts=0/0/0 msgs=0/0/0 bytes=0 lr="" time=1.445 13:16:21 [core] Plugin tls timed out on hook unrecognized_command - make sure it calls the callback tls.timeout is 12
— Reply to this email directly or view it on GitHub.
so?
Can we close this?
Closing unless this is still an issue. Re-open if necessary.
Essentially, see below. No idea why it didn't accept the cert.
tls.timeout is 12