Sam Varshavchik wrote: > > Probably won't ditch, but adjust the default settings, so everything > should work by default.
The point that I tried to illustrate, after doing the testing, was that there's no point to that setting. Nothing can be made better by changing it. If it's set to TLS1 or SSL3 under openssl, then only a client with an identical configuration will work. Even a client that uses the SSL23 setting can't connect to a server that uses TLS1 or SSL3 rather than SSL23. I can't conceive of any situation in real life where someone would want a system to do that. All that's accomplished by having that setting is creating the possibility for someone to break their system in ways that they won't notice for a while. http://phantom.dragonsdawn.net/~gordon/courier-tls.html I'm still irritated that you couldn't be bothered to save the mime part and look at the test results after I spent the time to do that work. Testing took hours; looking at the results would have taken you two minutes, tops. Some days you can be pretty uncooperative with people who put an honest effort into helping you improve your project. ------------------------------------------------------------------------- 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
