Lindsay Haisley writes:
On Sat, 2008-12-06 at 20:27 -0500, Sam Varshavchik wrote:If you can isolate this to Exchange only, set the following in courierd, which may fix this:TLS_CIPHER_LIST="SSLv3:TLSv1:!SSLv2:HIGH:!LOW:!MEDIUM:!EXP:!DES-CBC3-SHA:[EMAIL PROTECTED]"Interesting. After putting this line in courierd, remote system sends back: 500 DEBUG: Unexpected SSL connection shutdown.
Well, the remote system is closing the SSL connection, and Courier turns that event into this error message.
The system is apparently running Exchange. It identifies itself with:
220 squid.humantech.com Microsoft ESMTP MAIL Service, Version:
6.0.3790.3959
Apparently I'm going to have to leave ESMTP_USE_STARTTLS off for the
benefit of my customers who need to be able to communicate with their
customers on Exchange servers more than they need the extra security of
TLS over the Internet.
Yes. Exchange's TLS implementation does seem to be buggy. You do have an option of individually disabling TLS for individual remote mail servers. There's a way to do that so you'll still talk to TLS to the non-buggy part of the world, but you'll have to manually maintain a list of broken mail servers, and you probably don't want to do that.
pgp7IUY3Rk2xR.pgp
Description: PGP signature
------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
