Re: [dmarc-ietf] hints for receivers

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
>