Re: DMARC and yahoo

"Rolf E. Sonneveld" <> Mon, 21 April 2014 21:07 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 595501A0296 for <>; Mon, 21 Apr 2014 14:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Sju0RbNKI90T for <>; Mon, 21 Apr 2014 14:07:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6694B1A028E for <>; Mon, 21 Apr 2014 14:07:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3gCL8V48jQz5Mh9k; Mon, 21 Apr 2014 23:07:38 +0200 (CEST)
Received: from ( []) by (Postfix) with ESMTP id 3gCL8V2k4Hz1L8cK; Mon, 21 Apr 2014 23:07:38 +0200 (CEST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id F1CCC12316E; Mon, 21 Apr 2014 23:07:37 +0200 (CEST)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10026) with ESMTP id 42KjBsLBRdQC; Mon, 21 Apr 2014 23:07:31 +0200 (CEST)
Received: from [] (unknown []) by (Postfix) with ESMTPSA id C7DA2122EB0; Mon, 21 Apr 2014 23:07:30 +0200 (CEST)
Message-ID: <>
Date: Mon, 21 Apr 2014 23:07:29 +0200
From: "Rolf E. Sonneveld" <>
Organization: Sonnection B.V.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Douglas Otis <>
Subject: Re: DMARC and yahoo
References: <20140421163621.29166.qmail@joyce.lan> <> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------030000040900080902030108"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=2009; t=1398114458; bh=Xazu/kPp0qe3lw6/n5pd1BMKV2FPkD8MFtMXWhKZu/4=; h=Message-ID:Date:From:To:Subject:From; b=ghI76bvT0Zf8S8L4/9IRpzMLOckvFMA38YZyOhch+Lu0wMqcWBe30zCFyGolGsaCQ A87MlZAjr8DfOfrghyXAdYv5LPuK/OEuUnWEK91TBP9jWRHGTiCNsS7IbRIUi7zM1Y NsHSHHyb0/4rXBI61YY9qU+ANko8r9kXLhJIP/xU=
DKIM-Filter: OpenDKIM Filter v2.8.2 3gCL8V48jQz5Mh9k
Cc: John Levine <>,,
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Apr 2014 21:07:49 -0000

Hi, Doug,

On 04/21/2014 09:20 PM, Douglas Otis wrote:
> On Apr 21, 2014, at 9:42 AM, Dave Crocker < 
> <>> wrote:
>> On 4/21/2014 9:36 AM, John Levine wrote:
>>> They could fix it if they
>>> wanted, e.g., by arranging to whitelist mail sources that don't match
>>> DMARC's authentication model but send mail people want.  This is not
>>> just mailing lists, of course.
>> Sorry, but I'm not quite understanding what additional mechanism you 
>> have in mind.
>> Exactly who does exactly what?
>> Who has to adopt it?
>> How will it scale?
> Dear Dave,
> Each domain can simply point to their desired white-list. This can be 
> one published directly or simply referenced as described in:
> This has elements from the moribund ADSP.  The sender wishing to 
> protect a domain while also applying policy like that of ADSP or DMARC 
> can offer receivers a rapid and scalable method to check third-party 
> domain authorizations.  This means senders are always able to defend 
> recipients who trust messages from their domain.  Please note, 
> authorizations can also require presence of a List-ID.

This doesn't answer Dave's questions: who has to adopt it and how will 
it scale.

Adoption: of course the owner of the sending domain has to adopt it, but 
is there also a role for the owners of mailing lists, invite services 
etc.? How will the sending domain ever know whether a mailing list is 
open or closed for example? How will it know which invite services will 
need a TPA exemption?

Scaling: how does the owner of the sending domain (potentially very 
large numbers of users) know to what mailing lists its users are 
subscribed, what invite services will potentially need this TPA 
authorization etc.? Furthermore, will it scale if mailing lists can be 
members of mailing lists and how will the sending domain know about this 
hierarchy or chain of mailing lists? So the technical howto might be the 
easy part of the solution, while the organizational howto will 
definitely be the difficult part...