On Thu, Nov 21, 2019, Steven Champeon via mailop wrote: > We recently ran into this as well, via a longtime list member whose > company decided to switch to mimecast. I just grudgingly disabled TLS > altogether until I can investigate what ridiculous hoops I need to jump
Well, that doesn't work anymore for this particular sender :-( According to someone from mimecast (who tried to reply to the list but the mail didn't go through), it's up to the customer (?) to specify what requirement they want. > As for free CAs, they suffer from the same problem as self-signed, maybe > because that's what all certs are at the bottom. I'm not sure if there > are any who would actually work with mimecast, or how a mail server is I wasted several hours to set up one host to get a Let's Encrypt cert, configured my server to use that for connections from mimecast, and ... still get the same error. It's really frustrating what some people do with their configurations -- they shouldn't have so many knobs to break mail :-( _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
