Re: [dmarc-ietf] not ADSP, was is DMARC informational?

Michael Thomas <> Mon, 07 December 2020 05:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9CDF53A1015 for <>; Sun, 6 Dec 2020 21:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KSb5qeYXSQMI for <>; Sun, 6 Dec 2020 21:31:09 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0AFE23A1013 for <>; Sun, 6 Dec 2020 21:31:08 -0800 (PST)
Received: by with SMTP id e23so7928837pgk.12 for <>; Sun, 06 Dec 2020 21:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=y578QlIZ4NWaOT6xjBDyWUhSeQe7ppz131l66z6AHUI=; b=DlceJTAsjsABqQRILuqbmkQjjC7xcPTau4pGUExz5AhJ5V4dinRqqla2klumPxfutL swMKTSG5hEVUJFDjHlEFx6L4q58wswLhUQwirASpYCfpNCQkoUsA/jsYOumZSbkSIFvS 2IkBM2bQRTTaEiYPw7ds32QlKfBoEyDWqbYmZcIklCr3Sx4cm/jJhHvrTRPcXMZwNJ1/ VqBxplLfJODgZ8h0cYg5Ky/Qb/2K2Kq1q8iFK0zDm5Q0HKPWxNebFEY9bMH+aOeNYnz9 Gb+MZOqqk8AEhFjPIwICpHz2Fi1y1hE0WWCa9H00FrofNtnMnP7a9by0WO9fiOxDD2DV k1eQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=y578QlIZ4NWaOT6xjBDyWUhSeQe7ppz131l66z6AHUI=; b=DOzr0wIz6C6Bjk6fy9Qkk4W+3m3ytpM6IGJXGnIZwuWfVpyRY0x7Y4osJh025aC3qQ E06DS2Ht8oGSYLza7X19pEhUM695iMIcIUZkn4PUa8UxzdpOLm/zNiidHIHZUxn891sQ w8AK1lNc78+pb+8Ny3WIpmiD4ACOB3hYFq805QViUcMl8jxONfLmU7Rsed96hsLjBrBw z5icb8XEwApsCy2xcAXyJGLVXFsy4v/CIzUPJ6sk2ubqeo6c0t6SSWUmXF7T7xm16dNf n8giFjrYuMGl1OLRl24YqXCcY5NT8geME/0O5i0zk58kKQ06fBSh979n29bfd+D38QD1 89jA==
X-Gm-Message-State: AOAM530GGRFPA70zofvZs3RI97m+xDVC53MDjySAWn+CxVPdwkErPhDf tf2cHyolMI0TamMaDukQwZ2oszlCOzd72g==
X-Google-Smtp-Source: ABdhPJz/FSSTtN6wsgxUTtFpI0aSac9U3CJEEdVoSdrSgTl1MK67X8AJk//froRweQWnZQMeoTZwJw==
X-Received: by 2002:a63:5b23:: with SMTP id p35mr17006888pgb.143.1607319068011; Sun, 06 Dec 2020 21:31:08 -0800 (PST)
Received: from mike-mac.lan ( []) by with ESMTPSA id o189sm6815739pfd.73.2020. for <> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 06 Dec 2020 21:31:07 -0800 (PST)
References: <20201207051846.CBEEE291CC3F@ary.qy>
From: Michael Thomas <>
Message-ID: <>
Date: Sun, 6 Dec 2020 21:31:05 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <20201207051846.CBEEE291CC3F@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [dmarc-ietf] not ADSP, was is DMARC informational?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 Dec 2020 05:31:12 -0000

On 12/6/20 9:18 PM, John Levine wrote:
> In article <> you write:
>> As I recall, people took a run at trying ADSP and it was largely
>> unsuccessful.  I recall at least Yahoo, PayPal, and Google trying it but
>> finding that it interfered with their employees' participation in lists, so
>> they each invented new domains for their employees to use as separate from
>> their operational public services.  This basically led to its demise.
> Among ADSP's shortcomings was that there was no way to test it other
> than to turn it on and see how much damage it caused.  The answer was
> frequently a lot, so they turned it back off and that was that.
> DMARC certainly has its problems but the reporting is great. It makes
> the surprises when you turn DMARC on a lot less, at least if your name
> is not AOL or Yahoo.

but apparently y! is doing DMARC in the face of its inadequacies anyway. 
i really like the reporting capabilities as an auditing tool as well, 
but it doesn't change much on the ground with the basic problems. it 
just confirms that it's a bad idea to use p=reject in many cases. there 
are clearly many use cases where that isn't a problem -- like bank 
transactional mail -- and ADSP was just fine for that. nothing much has 
changed on that front in 15 years. I find it amusing to be talking about 
this all these years later, with all kinds of companies trying to 
capitalize on the new and mostly unimproved dmarc.