Hello, On Wednesday 14 May 2008 19:35:04 Dino Ciuffetti wrote: > Hi. Thanks everybody for yesterday replay that solved my problem!! > > 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)"? > > I googled for it but I found only an old mail of this list saying this is > not possible with courier.
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. I know it's a common problem, and there are a lot of broken servers out there. But it's not up to the sending side to fix the problems of the receiving end... You could try to make the admin of the the receiving server aware of the problem and have him fix it, but that's about it. Sometimes it works, most of the time it doesn't. At least that's my experience. 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. HTH, -- Regards, Arno. ------------------------------------------------------------------------- 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
