atom feed18 messages in net.sourceforge.lists.courier-usersRe: [courier-users] ESMTP_USE_STARTTL...
FromSent OnAttachments
Matus UHLAR - fantomasAug 15, 2011 7:38 am 
Sam VarshavchikAug 15, 2011 12:02 pm 
Matus UHLAR - fantomasAug 16, 2011 12:07 am 
Matus UHLAR - fantomasOct 27, 2011 4:33 am 
Matus UHLAR - fantomasOct 27, 2011 4:45 am 
Alessandro VeselyOct 30, 2011 7:50 am 
Ben KennedyOct 30, 2011 12:03 pm 
Alessandro VeselyOct 31, 2011 7:22 am 
Sam VarshavchikNov 3, 2011 5:47 pm 
Alessandro VeselyNov 4, 2011 3:53 am 
Matus UHLAR - fantomasNov 4, 2011 4:09 am 
Sam VarshavchikNov 4, 2011 5:25 am 
Sam VarshavchikNov 4, 2011 5:29 am 
Matus UHLAR - fantomasNov 4, 2011 5:45 am 
Sam VarshavchikNov 5, 2011 9:46 pm 
Alessandro VeselyNov 6, 2011 3:51 am 
Sam VarshavchikNov 6, 2011 4:16 am 
Matus UHLAR - fantomasNov 6, 2011 7:55 am 
Subject:Re: [courier-users] ESMTP_USE_STARTTLS error question
From:Alessandro Vesely (ves@tana.it)
Date:Nov 6, 2011 3:51:32 am
List:net.sourceforge.lists.courier-users

On 06/Nov/11 05:47, Sam Varshavchik wrote:

Matus UHLAR - fantomas writes:

If the error was temporary, I could disable TLS negotiation for remote server and ask them to fix the problem.

After some soul-searching, I've changed my mind. I'm going to change so that the default configuration ignores errors in response to a STARTTLS. This won't help if the other server accepted a STARTTLS, but the actual TLS negotiation failed, because of a cipher mismatch, or something of this sort. The TLS session is broken at this point, everyone's screwed, and you can't do anything there.

There will be a setting to treat all STARTTLS errors as soft errors, or revert to the current behavior of a hard error, if someone still wants this.

Would it make sense to invoke a user-provided script to sort this out?

A script could track server certificates, update esmtproutes, notify admins, report attacks, and whatever.

jm2c

------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1