14 messages in net.sourceforge.lists.courier-usersRe: [courier-users] TLS errors after ...
FromSent OnAttachments
Jerry AmundsonJun 27, 2007 11:47 am 
Gaye Abdoulaye WalsimouJun 27, 2007 12:32 pm 
Sam VarshavchikJun 27, 2007 3:33 pm 
Jerry AmundsonJun 27, 2007 9:07 pm 
Jerry AmundsonJun 28, 2007 1:30 pm 
Gaye AbdoulayeJun 28, 2007 1:59 pm 
Sam VarshavchikJun 28, 2007 3:23 pm 
Jerry AmundsonJun 29, 2007 7:26 am 
Alexander GrethaJun 29, 2007 1:51 pm 
Gaye Abdoulaye WalsimouJun 29, 2007 1:57 pm 
Alexander GrethaJun 29, 2007 2:04 pm 
Gordon MessmerJun 30, 2007 11:39 am 
Gaye AbdoulayeJun 30, 2007 12:36 pm 
Alexander GrethaJul 2, 2007 1:26 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] TLS errors after 0.56.0 upgradeActions...
From:Jerry Amundson (jamu@gmail.com)
Date:Jun 29, 2007 7:26:27 am
List:net.sourceforge.lists.courier-users

On 6/28/07, Sam Varshavchik <mrs@courier-mta.com> wrote:

The only related change in that area is that SSL2 is no longer accepted as a fallback for SSL3. If you want to use SSL2, you must explicitly set either TLS_PROTOCOL or SSL_PROTOCOL, accordingly.

Play with TLS_PROTOCOL (for STARTTLS), and SSL_PROTOCOL (for esmtp over SSL), and try different values for each.

Setting TLS_PROTOCOL=SSL2 (for STARTTLS) worked for me. From the Received line: (TLS: SSLv2,168bits,DES-CBC3-MD5)

jerry

-- "Oh joy! Rapture! I've got a brain" -Scarecrow