>> Is it possible to make courier automagically failing back to plain text >> for broken smtp hosts that advertise STARTTLS but are broken on STARTTLS >> command returning something like: "454 TLS not available: missing RSA >> private key (#4.3.0)"?
> AFAIK it isn't possible in general. But think about it: why should it? If > you announce being able do TLS and actually you aren't why > should you announce it in the first place? > It's up to the receiving server to get it right. > Either I do "speak" TLS and announce it, or I can't. > In the latter case I can't announce it. Yes, that'ok. I agree with you!! > There's a workaround, though, but it's ugly: > put something like > > receiving-domain.example: mx.for.receiving.domain.example /SECURITY=NONE > > in your esmtproutes. That fixes the problem for receiving-domain.example, > but > not in general. As I said, it's an ugly workaround. This temporarily solved the problem... I home mx/cname record for that domain does not change too quickly :-) Thank you so much!!! Dino. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
