Re: [dmarc-ietf] Reports helping spammers? (#81)

Douglas Foster <dougfoster.emailstandards@gmail.com> Sat, 23 January 2021 14:14 UTC

Return-Path: <dougfoster.emailstandards@gmail.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 3D50D3A11E8 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 06:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 5gatjGK4PcSM for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6B43A11E7 for <dmarc@ietf.org>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id k47so2842485uad.1 for <dmarc@ietf.org>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1IWNeey2qnWyK+WqzHd9D+g6P9EVm3I+BIfeqXBOrR0=; b=UQXmuSKo16SlqikKO3u2A0adHZi10pakTQCwe8cu4zNRwJDPmU5pVQr5cwPQb8yueY ROnOWCBKEkxO3Ng8fwl7m4NDDOb86+83HF854oeQfcwqlWxFUExgT0DWcNVFao1sFH2K brzqyUlcjkQi239wtfVkcFofnGcxTWF7wLtV90k6955/tY0Iqg9CDivkiYSGS6oiItnt b4gQbeZzFLLes5fmLiknHQaqWYaSl0mWKzvKksGJRLRr07EoPiI7cfT1PwZBGMOE2EAh lyWn1FFAX0nv/0+WPQm837lAqduphBsJghp+ny/0vr2BO79P4LGs5pCw6VNeoxJqMo7q GvuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1IWNeey2qnWyK+WqzHd9D+g6P9EVm3I+BIfeqXBOrR0=; b=KZH7e65+WcXY64LuumFa8POJQraD6IV2xvWAGDHaQdH0Rtq76IJP72+qwZPCCfDUxd SP21PHMOI5bMsau8jTZBXOZlToNnMEPObv+rP1bmRpDQAurjMQ+6BAX0L75KF/oRPAZr BvEcNQhg6IS5LetGMzbLW5SOowU0Ewsp0uiifjxIYW52dgX5dKjfv89/wISS1SHr5W8d +UbSMQXEg+h0xznYFKGze1MHwr7bNsYNQw7tBaN5mFrfHB7Sp0sk+dNbyNOHgCo9ESMO lGEUSGpQJqrZIQjk0QPKdW1r5+KNKBQPeIzIpcDEzwDY8zgPjvwoEAc1f9cMesKjPsm3 QCKg==
X-Gm-Message-State: AOAM530kQPafcpVhK3/iUpAc+dGdC/FHLwHqejwulMHaqxD6h/19ugLn ggO4M05J1gN9S7noy1d9k+FzL4Z3sdSFE37RKOA=
X-Google-Smtp-Source: ABdhPJyEI3QpV+MFngQ9hamgF2eH2E4JlbQy/xPwQA2XXXvuvTtuZPlbkdCMd8sW90lesCDE+LNWDd4KNzpMXF5qBMo=
X-Received: by 2002:ab0:768:: with SMTP id h95mr347643uah.104.1611411243292; Sat, 23 Jan 2021 06:14:03 -0800 (PST)
MIME-Version: 1.0
References: <20210122224018.E63E06BF246B@ary.qy> <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
In-Reply-To: <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 23 Jan 2021 09:13:53 -0500
Message-ID: <CAH48ZfyvjDQoqQp29LG07tz4g_eRMRboJdQ=qK8kzhyyknbMCg@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: John Levine <johnl@taugh.com>, IETF DMARC WG <dmarc@ietf.org>, emgu@google.com
Content-Type: multipart/alternative; boundary="000000000000be5a6305b991ea54"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Kru-hg0e1-1ffJkYVxV3sl7c53M>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Sat, 23 Jan 2021 14:14:06 -0000

The zeal with which the status quo is being defended suggests that
disposition reporting is pretty valuable to legitimate sending domains.
However, this situation complicates any effort to argue that such
information is useless and harmless for malicious domains.   Such a fine
distinction has not yet been justified.

I can fully endorse Murray's position that alignment reporting is
beneficial, even when the sending domain is malicious.   However, it is
also off-topic.   My focus is on disposition reporting, not alignment
reporting.

Bottom line:  The perceived risk of disposition reporting will differ with
each person, and therefore with each reporting domain.    The specification
would be improved by providing a way for skeptical domain owners to redact
information that they do not wish to disclose.   Currently, the options are
to (a) not report at all, or (b) report ambiguous and slightly misleading
information such as "dispostion=quarantine, overridereason=other".   A
better option would be to have options to state
"dispositioin=not specified, overridereason=not specified".


On Sat, Jan 23, 2021 at 6:21 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Fri 22/Jan/2021 23:40:18 +0100 John Levine wrote:
> >
> > As someone said, the better the spammers align their stuff, the better
> > we can filter it.
>
>
> 100% agreed.
>
>
> > Close this, please.
>
>
> Please don't.  That such a doubt can cross the minds even of knowledgeable
> people is a real issue.  At a minimum, the paragraph I cited[*] should be
> restored.  A crispy further clarification is welcome.
>
> Best
> Ale
> --
>
> [*]
> https://mailarchive.ietf.org/arch/msg/dmarc/HRAR3hSdckw3mU_Gebh8vcYOjm4
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>