Re: [dmarc-ietf] hints for receivers

Scott Kitterman <sklist@kitterman.com> Sat, 20 April 2013 17:21 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3769D21F8F5D for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 10:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=2.300, BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y+V6z1YCjrYb for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 10:21:44 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 6221D21F8F4A for <dmarc@ietf.org>; Sat, 20 Apr 2013 10:21:44 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id DE4D120E40D2; Sat, 20 Apr 2013 13:21:43 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1366478503; bh=miz3Jq8Ki6VmYf9CLoJ8I2lGjanGsvUkGmVQ5NKtio0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bpPzGB5Pd924/1pM8gR2RZf9xbIIFdK8xf/DQnNNRnCV/FC16XgO85PRb3ZxionHh IsdHeZp3CfHLjUW09A5bM5VbtQFZL5zZvYCAbmipLnqT5vaihFFlOUrI/1G4ztJwN8 b2g5AuQ8qllXH1lfO3rh7Jq+ltFGwBeXJhoWJlBg=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id C1AC220E409E; Sat, 20 Apr 2013 13:21:43 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 20 Apr 2013 13:21:42 -0400
Message-ID: <1581179.AB75fythCq@scott-latitude-e6320>
User-Agent: KMail/4.9.5 (Linux/3.5.0-27-generic; KDE/4.9.5; i686; ; )
In-Reply-To: <CAL0qLwZSNF7KP0nk8HFp6d9rcJx_gG7-CSWNMXks47i=jrqD6Q@mail.gmail.com>
References: <8598319F-D23B-4A5D-9896-0D2CF5D27F94@eudaemon.net> <CAL0qLwZSNF7KP0nk8HFp6d9rcJx_gG7-CSWNMXks47i=jrqD6Q@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Subject: Re: [dmarc-ietf] hints for receivers
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmarc>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Apr 2013 17:21:45 -0000

Most of the current deployment is at large providers that can do significant 
data analysis to effectively identify lists.  As a small domain, there's no way 
I can do the same.

If there were a protocol method to share this information, either among 
trusted receivers or via 'hints', it could be useful to smaller providers that 
don't have the scale to mine the data themselves.

Scott K

On Saturday, April 20, 2013 10:08:17 AM Murray S. Kucherawy wrote:
> This is reminiscent of VBR (RFC5518).  It would be interesting to find out
> how much uptake of that there's been.
> 
> Either way, I don't see this as something that could go in the base spec.
> However, DMARC was made extensible, so if there can be shown a demand for
> this among both senders and receivers, which is to say (as you asked) if
> there are receivers willing to make use of it, then it could be developed
> as an extension.
> 
> I imagine, though, that if such receivers existed, we'd have heard from
> them by now.  The preferred practice appears to be for receivers to
> identify lists using their own methods.
> 
> -MSK
> 
> On Sat, Apr 20, 2013 at 5:57 AM, Tim Draegen <tim@eudaemon.net> wrote:
> > I like the spirit J. Gomez's "l={yes,no,dunno}" proposal, but have been
> > struggling 'cause I don't think it would be effective in the wild.
> > 
> > While grinding up a batch of coffee beans, it struck me that
> > "l={yes,no,dunno}" is part of a larger category of "hints for receivers".
> > 
> >  As such, would receivers make use of high-level sender-provided
> > 
> > descriptors of email category?
> > 
> > For example, "l={yes,no,dunno}" could be realized with a
> > "category={transactional,newsletter,organization/corporate}" type of tag.
> > 
> >  In this way, receivers would use the hint "category=transactional", see
> > 
> > that the message came over a mailing list (transactional email shouldn't
> > come through a mailing list, right?), and act appropriately.
> > 
> > =- Tim
> > 
> > PS.  The "l={yes,no,dunno}" tag attempts to prescribe whether or not a
> > domain is excepted to arrive through a "list".  From the receiver PoV, is
> > a
> > description of the content of the email more generally useful?
> > 
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dmarc