IETF Logo Mail Archive

Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports

John Levine <johnl@taugh.com> Thu, 31 December 2020 16:00 UTC

Return-Path: <johnl@iecc.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 10BFF3A0D70 for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 08:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=vVDPy/0i; dkim=pass (2048-bit key) header.d=taugh.com header.b=eEzLFj7w
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 Yws0AThsjK6y for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 08:00:32 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5228D3A0D6F for <dmarc@ietf.org>; Thu, 31 Dec 2020 08:00:31 -0800 (PST)
Received: (qmail 11249 invoked from network); 31 Dec 2020 16:00:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2bee.5fedf59f.k2012; bh=3ZFC39tmg3tyh6mf+o1OJO9cJRwL2HQ+cYUAZix0mwk=; b=vVDPy/0iPZMR+/jt39Fhv1jTd+9Fjo82w4fegveEJMSzZsIizWNWH9MWDgIQZRDZ+x9D+lwBlz0VIvluC/n1GO3/HIl/8u3zZAR8V6mmquagkv81mEb4Nh6SPkaL473sVUen9rE0k0mz97IeVQNVAKvb11YscqOmkwFU37+g/QGCBKpUX2bMd61jc0n3ejWoAhkjuU6fuuYZtFzbznj8BXf27w4g40Sh2Q4QVx5aOaD8eoLIlOcRRmRbQAPJCZGSEjCe+X1/ke153QUik/smsVRvyqaIP0dmFqTeRrxyLUXvHDTa6Px/+Xh3fqT1jiA7I26QNIbqVKrBwr1GBGBpBg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2bee.5fedf59f.k2012; bh=3ZFC39tmg3tyh6mf+o1OJO9cJRwL2HQ+cYUAZix0mwk=; b=eEzLFj7wBzTlikrAPK+U3CbAZTDN8QDXDK4iwcFYmaUMoXq7Pj48C2MCIDnTf7egvrrpwI8nvqW84idv4A590qfXmN38PmAPe7EdM+1TO2SMXIEM4klMDuj9c6PkDMq6YK8EJjVQHswImMHi2BUTlGCPTjZ7IBBd3szrLfdue3YaGYtOVeGpgWEIOEjpIXYQVcPmOj+tMgxJubcvkct8oEB8dk7KqC8WJZC5mmv9ADk7t0+0kDHxyTpz128rMTp4vAbU9boVxk87pS6a/JUnHwrfq+JAxCuPq7Gl5c0yiJQhhZPtM/eNbVTqxS3NtCjNxjGozgQGfYYPqukNcHSumQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 31 Dec 2020 16:00:30 -0000
Received: by ary.qy (Postfix, from userid 501) id 20AFB3EE7AD7; Thu, 31 Dec 2020 11:00:29 -0500 (EST)
Date: Thu, 31 Dec 2020 11:00:29 -0500
Message-Id: <20201231160030.20AFB3EE7AD7@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <7dc4203e-1140-8808-776c-e80e5b5f6565@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LFTxHg38E5mK8DprqtMl04hAVGs>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Thu, 31 Dec 2020 16:00:34 -0000

In article <7dc4203e-1140-8808-776c-e80e5b5f6565@tana.it> you write:
>> Many Girl Scout troops were affected when Yahoo published p=reject. Which is 
>> probably why John brought it up. This isn’t a hypothetical, this is things that 
>> we know actually happened and real world effects of DMARC.
>
>I'd guess the problem they experienced have been mailing list and submissions 
>using ISP's bundled services or similar unauthorized MSAs.  The former is fixed 
>by From: rewriting, the latter has no possible fix.

Not a good guess.  Please review previous messages in this thread for clues.

>Are there other unwanted effects?

The main effect is that the mail they'd been sending from their ESP
with their Yahoo address on the From: line used to work, and now falls
on the floor or worse.

R's,
John

v2.23.0 | Report a Bug | By Email