atom feed10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Calling a Mail Se...
FromSent OnAttachments
Jacob S. BarrettJul 31, 2003 7:35 am 
Jeff PotterJul 31, 2003 9:13 am 
Juri HaberlandJul 31, 2003 11:34 am 
Jacob S. BarrettJul 31, 2003 12:02 pm 
Anand BuddhdevJul 31, 2003 12:08 pm 
Juri HaberlandJul 31, 2003 12:10 pm 
Juri HaberlandJul 31, 2003 12:24 pm 
Gordon MessmerAug 3, 2003 6:45 pm 
Mitch (WebCob)Aug 4, 2003 12:34 am 
Gordon MessmerAug 4, 2003 11:18 am 
Subject:Re: [courier-users] Calling a Mail Server's TLS Bluff
From:Juri Haberland (ju@koschikode.com)
Date:Jul 31, 2003 12:24:39 pm
List:net.sourceforge.lists.courier-users

Anand Buddhdev wrote:

On Thu, 31 Jul 2003 20:34:15 +0200 Juri Haberland wrote:

Postfix-tls has the same "problems" but provides a file called 'tls_per_site', where you can disable TLS for a particular site - obviously similar to 'esmtproutes'. IMHO, what you are asking for is a workaround for bugs in other MTA software. One can argue about that...

It's all very well to argue about correct behaviour in other MTAs. But the problem remains, that mail remains undelivered. And sometimes, email *is* important.

As I wrote in another mail, if you don't check your logs, you're to blame - not the software.

We're talking here about a feature in courier which allows for it to fall back to an unencrypted connection if STARTTLS negotiation fails. Exim is a great example reasonable behaviour. If it tries STARTTLS, and that fails, it falls back to an unencrypted connection, logging this fact; email gets delivered. However, exim can be told to specifically insist on STARTTLS with certain sites, in which case, a failure to negotiate a secure connection will cause the message to bounce. We might want this kind of behaviour with certain sites.

Yes, it's a 'nice-to-have', but IMO not critical.

Cheers, Juri