Maybe someone can tell me how to avoid delivery problems from mimecst.com.
Here's what I noticed so far:
If my server offers STARTTLS mimecast aborts the handshake with a protocol error
Info about cipher and cert offered by mimecast as client:
cipher=ECDHE-RSA-AES256-GCM-SHA384,
cert_subject=/C=GB/L=London/O=Mimecast+20Services+20Limited/OU=Technical+20Operations/CN=*.mimecast.com,
cert_issuer=/C=US/O=DigiCert+20Inc/CN=DigiCert+20Global+20CA+20G2,
and then:
description=error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate
unknown, file=s3_pkt.c, line=1498, text=SSL alert number 46
seemingly because it does not like my (self-signed) cert.
If I turn off STARTTLS, mail delivery used to be ok, e.g.:
Received: from us-smtp-delivery-171.mimecast.com
(us-smtp-delivery-171.mimecast.com. [216.205.24.171])
by kiel.esmtp.org (MeTA1-1.1.Alpha13.1) with ESMTP
id S000000000000419800; Thu, 7 Nov 2019 20:22:07 +0100
Received: from NAM05-CO1-obe.outbound.protection.outlook.com
(mail-co1nam05lp2052.outbound.protection.outlook.com [104.47.48.52]) (Using
TLS) by relay.mimecast.com with ESMTP id
us-mta-191-n-oFfjTNO3eIMfTTPpry7g-1; Thu, 07 Nov 2019 14:22:02 -0500
but almost immediately thereafter all sessions failed: mimecast did
not start any transaction and I do not know why -- maybe they require
STARTTLS now?
Unfortunately it isn't easy for me to get an "official" cert, and
that should not be a requirement anyway.
So how do I get mails from mimecast?
TIA,
Claus Assmann
_______________________________________________
mailop mailing list
[email protected]
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
