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:Matus UHLAR - fantomas (uhl@fantomas.sk)
Date:Oct 27, 2011 4:45:19 am
List:net.sourceforge.lists.courier-users

returning to an old thread... (sorry for the quoted reply w/o comments)

Matus UHLAR - fantomas writes:

What error does courieresmtp generate now, when it envounters STARTTLR error with SMTP server? Can I turn on fallback to plaintext SMTP, when courier encounters such error?

While I would like to use TLS where possible, I'm ok without it - we currently send all mail without TLS now :)

On 15.08.11 15:02, Sam Varshavchik wrote:

There are several possibilities. If the STARTTLS command itself fails, it's an SMTP error no difference then any other SMTP error, and will be either permanent or transient depending on its numerical code. If the STARTTLS command succeeds, but TLS negotiation fails, its a permanent error. But in either case there is really no fallback path.

There would be a fallback path, if courier returned and reported tempfail in such case: we could set up esmtproutes for such host that would disable using starttls there, and the mail would get delivered.

Currently, when STARTTLS fails, courier issues permanent error which causes mail to be imediately lost, which is why we can not use starttls by default.

Can you please change the STARTTLS error to cause temporary failure? Thank you.

For practical purposes TLS for SMTP is fundamentally broken. Many TLS servers simply use self-signed certs, making TLS fundamentally useless as means for effective encryption.

Many does not mean all - those who use certificates signed by truaster authorities are safe. And we can still configure other certificates as trusted.

------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev