Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

Laura Atkins <laura@wordtothewise.com> Mon, 17 August 2020 14:00 UTC

Return-Path: <laura@wordtothewise.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 4B9CB3A0C4E for <dmarc@ietfa.amsl.com>; Mon, 17 Aug 2020 07:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 8-8mCKSNmwCG for <dmarc@ietfa.amsl.com>; Mon, 17 Aug 2020 07:00:46 -0700 (PDT)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id CA8CD3A0C4D for <dmarc@ietf.org>; Mon, 17 Aug 2020 07:00:45 -0700 (PDT)
Received: from [192.168.0.227] (unknown [37.228.245.144]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 9F6889F1F7 for <dmarc@ietf.org>; Mon, 17 Aug 2020 07:00:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1597672845; bh=Jhvk7nM/r8SMWu8qg1fG4PJgIHsu9ke6tx56CBji+yw=; h=From:Subject:Date:References:To:In-Reply-To:From; b=cBIQ65kegzJ4fSXBcbKK5Q7uD4kWnvrKa0r5COBWPvjThPvY8wwqd8oyyiX3HKTKF z5Yh+QoATClSgHPHH/3RQqpkpLUmtkEBjv5A1lYT/leLVT0ugebkt8ZSFShSS6KRdl fj6uUzBviRi557QRlcAbLtihxKNvaZuKrXJJNkSY=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E76CEDB-B27D-43BE-8887-382079BF8849"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 17 Aug 2020 15:00:42 +0100
References: <CAJ4XoYcFbh8-nAxjxzzRgUahFfhcgcZQ2yMF2ewv_-DgUmhL=g@mail.gmail.com> <20200814164237.313071E971DB@ary.local> <CAJ4XoYeqj_5mpZu1PZP4rNfrWRyC5gC-2dfK7oX9xQHiR24QeA@mail.gmail.com> <085c6a5f-5451-ae8c-4873-133673ba1754@tana.it> <CAL0qLwaVUi9QtV4zcCwncuy4N3YPwsGZPzFfd1q19io79UG2VQ@mail.gmail.com> <c1844590-4b12-9763-21c5-6ac5b730321b@tana.it> <6358f3da-806b-f4eb-b9a0-8ee8ce4121d7@dcrocker.net> <4e549ca6-6047-6ff2-325c-fe8d7247e157@tana.it> <c972e0af-b589-1780-47b3-8cb2a2024ec2@dcrocker.net> <13a0ed72-2c5a-8ba6-84ab-b857e29403f1@tana.it> <b5935bde-e8-78ef-ed17-90a1d730aa9d@taugh.com> <8CCCBF0C-8651-4298-BB29-457381655D1D@wordtothewise.com> <beba49bc-e599-4f5b-72ad-2328938af9da@tana.it> <7FC8E909-1A13-4682-B3D8-EAD76F2B02BB@wordtothewise.com> <CAJ4XoYcx=doEfrN2M=X8OZQF0Nq+AFRLYqTgrsr1zMFSJVwziw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <CAJ4XoYcx=doEfrN2M=X8OZQF0Nq+AFRLYqTgrsr1zMFSJVwziw@mail.gmail.com>
Message-Id: <7C25FA42-6C6B-45B9-8476-B74F2455EDDC@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ukJ_PxHy4h0T7eXsKIhMxCFSdDI>
Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 17 Aug 2020 14:00:48 -0000


> On 17 Aug 2020, at 14:18, Dotzero <dotzero@gmail.com> wrote:
> 
> And, 17 years on, we know that domain level authentication doesn’t actually help filter spam nor does it provide law enforcement with a potent tool for locating and identifying spammers. It was promising, it didn’t live up to the promise. 
> 
> There were a lot of thrown at the wall during those 3 days of talks. One of them was domain level opt-out. Another was a global opt-out list similar to the postal opt-outs run by the DMA. Another was a technology called TEOS. HashCash. The list of things we discussed as promising solutions was extensive. Just because we discussed a particular kind of solution does not mean that anything was decided. It also doesn’t mean that any particular solution mentioned was workable. 
> 
>>> https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day1.pdf <https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day1.pdf>
>>> https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day2.pdf <https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day2..pdf>
>>> https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day3.pdf <https://www.ftc.gov/sites/default/files/documents/public_events/ftc-spam-forum/transcript_day3.pdf>
>> 
>> 
>> Thanks.  Let me quote a paragraph by Paul Q. Judge, from the 3rd pdf:
>> 
>>    It doesn't require that one day everyone turns it on and we begin
>>    to drop the rest of the e-mail and break e-mail.  If a domain
>>    decides to turn it on, then they've prevented forgery for their
>>    domain and they're protected.  For persons that have not turned it
>>    on, then their e-mail still flows but they are not able to
>>    stop people from forging messages from their domain.  So, I think
>>    it's something useful and can be deployed incrementally.
> 
> We know, now, that turning on domain level protection does not stop phishing attacks against that company. It stops direct spoofing of the domain, but the phishers simply use a completely different domain. Just this weekend I got a PayPal phish. PayPal who helped invent DMARC are still getting spoofed and phished. Sure, the phishers aren’t using the paypal.com <http://paypal.com/> domain, but that doesn’t seem to have any effect on their success at stealing money from people. 
> 
> You raise an interesting point, Laura. Whatever "solutions" we put in place, the abusers/bad guys will evolve. One of the problems for the good guys (for some definition of good) is that standards work takes years (decades?)  while the bad  guys change their tactics at will. Crime existed before the Internet and will continue long after we are all dead and buried.

Totally agreed. The issue here is that DMARC is a fundamentally flawed model for preventing phishing. Phishers were adapting to mailbox provider filters even before DMARC and there was a lot of cousin and non-look-alike domain phishing even during the initial discussions. I know these issues were brought up during discussion of the protocol. Unfortunately, they weren’t sufficiently addressed and now we’re at a point where, to my mind, DMARC doesn’t fix anything while also breaking a lot of ways folks use mail.

It’s a little late now to go back. I think this is an opportunity to think about the underlying technical problems as well as a chance to revisit the assumptions about how email is used. Discussing things like Dave’s drafts will give us a chance to talk about how people actually use email to communicate with one another. And how we can allow brands what they want without breaking email too much for the rest of us. 

>> It seems we're still stuck midstream...
> 
> Stuck at what? Many of the people who were at that conference are still working in the field and understand both the purpose and what came out of the forum. I’d also say that most of what happened there is a nice bit of history but is also irrelevant to addressing the spam problem as it is now. Email has evolved significantly in the last 5 years, much less the last 15. We can use the discussion as history to say “we looked at this and it didn’t work” but I don’t really see a lot of value in saying “let’s retread things from a decade and a half ago that didn’t work.”
> 
> I think the most 
>  useful thing we can say about the FTC workshops is that they were a forcing mechanism that instigated a lot of effort and innovation in the space. Some of those efforts fell by the wayside and some still persist.

You think? I’m not sure I’d agree. I saw the workshop as mostly a political (and educating the politicians) exercise. The effort and innovation were already there and being done by a lot of people who weren’t there. I’m kinda bemused by the importance folks have assigned to it in relation to the vastly different email ecosystem we have today.

laura 
-- 
Having an Email Crisis?  We can help! 800 823-9674 

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741		

Email Delivery Blog: https://wordtothewise.com/blog