Re: Enough DMARC whinging

Dave Crocker <dhc@dcrocker.net> Thu, 01 May 2014 15:18 UTC

Return-Path: <dhc@dcrocker.net>
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 490F41A08E9 for <ietf@ietfa.amsl.com>; Thu, 1 May 2014 08:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 TK7yhU8iSuGG for <ietf@ietfa.amsl.com>; Thu, 1 May 2014 08:18:51 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 579811A07B3 for <ietf@ietf.org>; Thu, 1 May 2014 08:18:51 -0700 (PDT)
Received: from [10.168.69.12] (pool-71-164-185-121.dllstx.fios.verizon.net [71.164.185.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s41FIhD5009190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 1 May 2014 08:18:47 -0700
Message-ID: <536265CE.6090508@dcrocker.net>
Date: Thu, 01 May 2014 10:18:38 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Enough DMARC whinging
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com> <536113B1.5070309@bbiw.net> <CAMm+LwiXoW3p5uCmML4kAWXnbrrAnSCK9x5U2qeHJdVgR2r_Gg@mail.gmail.com>
In-Reply-To: <CAMm+LwiXoW3p5uCmML4kAWXnbrrAnSCK9x5U2qeHJdVgR2r_Gg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 01 May 2014 08:18:47 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BLEDu9KV5ocI9Ks_TgeT3-UcozM
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 01 May 2014 15:18:52 -0000

On 5/1/2014 8:22 AM, Phillip Hallam-Baker wrote:
> Spam filters should know about things as important as mailing list
> subscriptions.

We have about 20 years of spam filtering experience in the industry.
The quality of modern filters is astonishingly good; it's the only
reason email remains viable for users, in spite of open-Internet spam
traffic being far above 90%.

I believe that little or none of that filtering includes awareness of
mailing list subscriptions.  So while the above is an interesting and
possibly useful line of pursuit, it's not clear how it can be elevated
to the status of 'should'.

Note that historically, mailing list operators have been resistant to
the imposition of technical or operational changes.


> It the mailing list has appropriate spam ingress controls, is
> authenticated using DKIM and there is evidence that the user has
> subscribed then the spam filter can whitelist all the messages from
> that list.

Nope.  Mailing lists can be sources of spam, too.  Even good lists.  So
blanket whitelisting would not be advisable.

However modern filtering engines are complex enough for nuance.  So they
can ratchet up or down just how stringent the criteria are. The above
scenario well might warrant less stringent criteria.


> And to the other conversations, we are talking about draft- here. And
> that isn't the same as standard. In fact one of the requirements for
> being granted standard would be to come up with answers to these
> issues.

Standards status matters, but not as an absolute.  The fact that the
text exists as an I-D also does not automatically impart importance or
utility, in terms of industry adopters.

Often it does, of course, but this doesn't seem to be one of those
cases, does it?


Sometimes we forget that the IETF is in the service of adopters, not
vice versa.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net