Re: IETF mail server and SSLv3

ned+ietf@mauve.mrochek.com Fri, 05 February 2016 16:18 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 764131B3B09 for <ietf@ietfa.amsl.com>; Fri, 5 Feb 2016 08:18:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UopoLKlTOPr for <ietf@ietfa.amsl.com>; Fri, 5 Feb 2016 08:18:04 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) by ietfa.amsl.com (Postfix) with ESMTP id D22FE1B3B08 for <ietf@ietf.org>; Fri, 5 Feb 2016 08:18:03 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PWBHCQH2J40010OL@mauve.mrochek.com> for ietf@ietf.org; Fri, 5 Feb 2016 08:13:01 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PW7P38X61C00008P@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 05 Feb 2016 08:12:57 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01PWBHCOQZTW00008P@mauve.mrochek.com>
Date: Fri, 05 Feb 2016 08:04:10 -0800
Subject: Re: IETF mail server and SSLv3
In-reply-to: "Your message dated Fri, 05 Feb 2016 15:44:35 +0000" <20160205154435.GT19242@mournblade.imrryr.org>
References: <F38A9FEF-7DBB-4F40-860E-6CB425E5EEE3@ietf.org> <sjmvb66r1st.fsf@securerf.ihtfp.org> <20160204024001.GM19242@mournblade.imrryr.org> <C9624BB55C713BCF83E4A552@7AD4D3FB4841A5E367CCF211> <08CEE02F-74DF-4C5E-A116-AB66FD8516FA@dukhovni.org> <01PWAPWAKLJI00008P@mauve.mrochek.com> <20160205041346.GS19242@mournblade.imrryr.org> <01PWBEB7DVJY00008P@mauve.mrochek.com> <20160205154435.GT19242@mournblade.imrryr.org>
To: Viktor Dukhovni <ietf-dane@dukhovni.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KvmHX7LR4aathjYUKxbxR0ogBSc>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 16:18:05 -0000

> On Fri, Feb 05, 2016 at 06:42:34AM -0800, Ned Freed wrote:

> > > The implementation and documentation of this was joint work with
> > > Wietse back in early 2006.  These days, when STARTTLS fails, Postfix
> > > tries other MX hosts first and if they all fail, defers the mail
> > > initially. Cleartext fallback kicks in on the second delivery
> > > attempt if STARTTLS fails again.
> >
> > Actually, I consider this approach as unacceptable unless the second delivery
> > attempt occurs within a minute or two. (Which, incidentally, is a much shorter
> > retry period after deferral than the standards recommend.)

> The default is 5 minutes, with doubling exponential backoff up to
> a cutoff of somewhat over an hour:

That's borderline IMO.

> ...

> As for "unacceptable", you might find the below fall into that
> category:

>   * IIRC Sendmail never falls back to cleartext if STARTTLS is
>     advertised.

A fix has been available for a while; the apparent plan is to integrate 
it into sendmail 8.16. See:

http://www.sendmail.org/%7Eca/email/patches/tls_failures.p1#sthash.iwHHaXb0.dpuf

for details. However, since the fix doesn't allow for immediate fallback, it
leaves a lot to be desired.

> ...

> As for a delay of < 5 minutes delivering email to such broken sites
> it is, for most users, a reasonable trade-off to reduce needless
> TLS fallback in the face of routine transmission glitches.

That's a consequence of piggybacking cleartext fallback on the deferral
mechanism you use for transmission failures. It doesn't have to  be done this
way.

				Ned