IETF Logo Mail Archive

Re: [dmarc-ietf] DMARC forensic reports (ruf=) and privacy

"John Levine" <johnl@taugh.com> Mon, 28 January 2019 19:22 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 27E7F13118E for <dmarc@ietfa.amsl.com>; Mon, 28 Jan 2019 11:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=LnspRAr7; dkim=pass (1536-bit key) header.d=taugh.com header.b=RNTSYUpy
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 NscGCwjel3wY for <dmarc@ietfa.amsl.com>; Mon, 28 Jan 2019 11:22:00 -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 1DCB9130EAE for <dmarc@ietf.org>; Mon, 28 Jan 2019 11:22:00 -0800 (PST)
Received: (qmail 55664 invoked from network); 28 Jan 2019 19:21:59 -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; s=d96c.5c4f5657.k1901; bh=Y8EHwpXcx70kBTqoR1JTUoIX2Q++dGyexrgXQ+Ugnm8=; b=LnspRAr7n5xjKfy5AG8PO2MXyRnrjUN9U5uNr45ltIRPGGRCAOEuw4F3HPSfE8T7kKK6JT1/pEVEX5ZH0+Qr35FKXHJbj+TRbuxTMjV2k73HzS7/jvEce8/MHNJ8wR9absO8bkXOP1t7MP1M/zW7mgjLRNmLmvlv7e7cCMnpuFkw6WeICAmE8TqkuF+Ji2SeKPqo0hAwZT2vsW6T/DncidQhRi3dSu92nqQ3EG/dxVr7S8LR3P+9Kz4QyHRcSVf5
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; s=d96c.5c4f5657.k1901; bh=Y8EHwpXcx70kBTqoR1JTUoIX2Q++dGyexrgXQ+Ugnm8=; b=RNTSYUpygJXejWxBE3D0G7aaIrsAPJJ9uAzB/iJMwR+tCxykm5drYgaKHdLi2II70rnapg9PWvsM+zwWu7Z6R8h5fgAenb8jNAd+InX5Fgq2N2X9pvVfrCIvmZ8DDi34zzPKiCCchN27CYyFd7W35PGhFUs7zGcgU1l6U4ETu54maWGUXhyULJmp1pC7TCoge68u02vDuD/SbeJYrBEvl0uadYjod+R526hr8j/kc/bY/dNnakSodtLX5zHjM3GG
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 ESMTP via TCP6; 28 Jan 2019 19:21:58 -0000
Received: by ary.qy (Postfix, from userid 501) id D02A2200D64851; Mon, 28 Jan 2019 14:21:58 -0500 (EST)
Date: Mon, 28 Jan 2019 14:21:58 -0500
Message-Id: <20190128192158.D02A2200D64851@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dilyan.palauzov@aegee.org
In-Reply-To: <ccec6257175e633174ed792d41f2065cdae6b3e6.camel@aegee.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/MV2J6JRlAX5Qwei6ogyp-fSfNCI>
Subject: Re: [dmarc-ietf] DMARC forensic reports (ruf=) and privacy
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, 28 Jan 2019 19:22:02 -0000

In article <ccec6257175e633174ed792d41f2065cdae6b3e6.camel@aegee.org> you write:
>sending a notification, when DMARC does not match is comparable to sending a notification/feedback loop, when a user
>clicks a message as spam.

No, it isn't.  When the user clicks the spam button, she has taken a
specific step to notify someone about the message.  DMARC forensic
reports are entirely automated.

But once again, I am pretty sure the people who you would need to
persuade are not on this mailing list, or any IETF mailing list.

R's,
John

v2.23.0 | Report a Bug | By Email