Re: Change the mailing list protocol, not DMARC.

Ted Lemon <ted.lemon@nominum.com> Fri, 13 June 2014 13:51 UTC

Return-Path: <Ted.Lemon@nominum.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 9DB9D1B2919 for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 afAAX17MZb1v for <ietf@ietfa.amsl.com>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E11A01B2917 for <ietf@ietf.org>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C7F641B81FD for <ietf@ietf.org>; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B73A019005C; Fri, 13 Jun 2014 06:51:05 -0700 (PDT)
Received: from [10.0.10.40] (174.62.147.182) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Jun 2014 06:51:05 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Change the mailing list protocol, not DMARC.
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk>
Date: Fri, 13 Jun 2014 09:51:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <61CB97DA-A3C8-4B48-B014-399F42DFDA25@nominum.com>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <C2850EE4-00FB-451E-A829-00B562B108E2@nominum.com> <alpine.LSU.2.00.1406131425200.3035@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [174.62.147.182]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BYjavd3AtCo4CGsW7GEhIMuTrbo
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, IETF <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: <http://www.ietf.org/mail-archive/web/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, 13 Jun 2014 13:51:07 -0000

On Jun 13, 2014, at 9:41 AM, Tony Finch <dot@dotat.at> wrote:
> BUT! These systems do not use the MIME external body mechanism, because it
> is common for mail servers to reject these messages on the grounds that
> they are too difficult to properly scan for viruses.
> 
> The end result is something pretty simiilar to MIME external bodies, but
> a complete mess from the protocol architecture point of view.

Ouch.   Yet another reason why a flag day may be necessary to improve the situation.