There was recently some discussion about this issue where some misconfigured mail servers announce STARTTLS support when in fact they really don't support it. There are two ways to fix that problem that I can see, but neither one is really practical. You can either disable TLS completely for outgoing connections or per domain vi esmtproutes with "/SECURITY=NONE". I really don't want to have to make an entry for every domain I discover is misconfigured because you have to specify a particular host to handle the request, which may change over time. That leaves me with disabling TLS altogether, which isn't very desirable as well.

Is there a flag, available today, that can be set that tells courier to _try_ TLS? In other words, if STARTTLS is announced and you call the bluff, rather than failing to deliver and deferring the message it would retry without calling STARTTLS. If there isn't a flag that does this, can it be added to a wish list? For karma sake, it would be nice if it would log the failed STARTTLS attempt so that one could contact the postmaster of that domain and notify him.

Thanks,
Jake

--
Jacob S. Barrett
[EMAIL PROTECTED]
www.amduat.net

"I don't suffer from insanity, I enjoy every minute of it."




------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to