Re: [dmarc-ietf] DMARC and ARC

Douglas Foster <dougfoster.emailstandards@gmail.com> Mon, 07 December 2020 12:38 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 D6D313A1390 for <dmarc@ietfa.amsl.com>; Mon, 7 Dec 2020 04:38:11 -0800 (PST)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 O_dSoYiP3Roy for <dmarc@ietfa.amsl.com>; Mon, 7 Dec 2020 04:38:09 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (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 8E2FE3A1388 for <dmarc@ietf.org>; Mon, 7 Dec 2020 04:38:09 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id q68so4405718uaq.3 for <dmarc@ietf.org>; Mon, 07 Dec 2020 04:38:09 -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=v7swuOi8+y6oULK/f4w/XEJUZPYVU2NuqST/Og5OGwI=; b=JQlm7AKRK9Qrw5VnPH6DV8A3YNx+m7tKYmEZ1l5z53I5SW0nPm8Ygbjr17ZY8DzepF Y9jQdQnjjEOG/LCL+Wshheh3Xi35+vooTOldRitTV97akRn9a2rW9IlRCtD7f4qlJwzs glCB19mCr8KL9rqbrK1g6PAzyYvhCNRe9rstobVaGMaLvZFFcTrjsJDJX/+ljKFBDoSq 4KMbHsL29BAzz5+pxokeNfnaYZh5tftAtZFrwVbNBB4RXYtR7ln4cMU5UOKMWpRn2+Nu OwPNu/4XvncE0gD64ZKBNQDdJd7O72QnqNpEU+yV0aRoOYFL7sujtokjijdy2xcpPSXF g6ng==
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=v7swuOi8+y6oULK/f4w/XEJUZPYVU2NuqST/Og5OGwI=; b=Mm6/fz1o93fC++yC43i4Bb2AWxwBTWXvy62Egi+sDXXQySC/Z3E++Ku2qm9qmaa616 Q31KLc+i97yduFgIwtc+ut0Z4hlsSJg4ebbm+Iv8X2na2GbSiI14yr+U9Pr2xE4GdCJD uYpTVP1GL3HfyxLHs5RUJuiwYWhL94kkE/LEYMILAawLANZ9h8ZSRzhJUj+Gb+oxhcHn 2g7JbxFa77qgv/SKdz09g48MYVKUcBc/WUK07Y6fkowejIGz/GwYxkoGflBTMw8F2bD5 ERcveVzlUdbsoe2UrdNr6V6TVHlrJ+2DOvOCVnvxSCgDBk92h6NDTj1Qme+Zga31CNmW 3Qtg==
X-Gm-Message-State: AOAM530LEv31e5vtOaay+cAYreplwv2u+EsLJ8ghnw585P9FEh8q/Nv3 a6sE2q4L0A4Wuqm9/aqGLR3RsUA8WzSZMUsqr+E=
X-Google-Smtp-Source: ABdhPJzRvONps5DcSAQbpuvw9++oyuC8+6Mysp4cpjO8JXR7NqsPzYah6w1udLy3jfxUrTm8DM1Xx8xcakPwnhjOdLg=
X-Received: by 2002:ab0:2a4a:: with SMTP id p10mr11746036uar.95.1607344688302; Mon, 07 Dec 2020 04:38:08 -0800 (PST)
MIME-Version: 1.0
References: <CAH48Zfx1gL-rnqWWaJODi72Sgp6F70Bm_kAYL5rwSmVmopQ9qg@mail.gmail.com> <CAL0qLwbgGvwBiu=MBsbhQ_HRdSQ7jDABgicd1Od_wyLGttp6Ug@mail.gmail.com>
In-Reply-To: <CAL0qLwbgGvwBiu=MBsbhQ_HRdSQ7jDABgicd1Od_wyLGttp6Ug@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 7 Dec 2020 07:37:58 -0500
Message-ID: <CAH48Zfys470gb4MpSjdnfuAeir5JVZz-0PYswX6X75JTZxw8ag@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002d8f4105b5df19ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qyf_0q8P8v9KlmoXxSCBkHWkIUA>
Subject: Re: [dmarc-ietf] DMARC and ARC
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, 07 Dec 2020 12:38:12 -0000

Thanks for engaging Murray.

On the usefulness of source blacklisting:

I have been using the model I described for about a year.    I have two
categories of mailers that account for nearly all of my spam:
 spamer-owned infrastructure which sends direct, and email service
providers that accept all customers, including criminals.   ESP messages
will arrive SPF-aligned with the ESP domain, the From address indicates the
client, and DKIM signing is used when necessary for DMARC compliance.

I don't think I have seen any problems with infected servers or even
infected accounts from trusted sources, which is surprising.   Compliments
to GMail that the worst that I get from them is unwanted-but-persistent
advertising.

Our employee base is measured in 4 digits, not 6, so our volume is smaller
than many, and my desired-sender list is correspondingly small.   That has
meant that I have not had false positives with blacklisting.

When a confirmed spam is received from spam infrastructure, the best
defense is to blacklist the IP, the host domain, and the address domains
(unless one of these has been spoofed.)    In practice, this is tedious to
do consistently.   Blocking on server domain has proved pretty effective.
 When blocking on IP, we often block a subnet.   Depending how quickly we
identify the spam source, the message history sometimes provides a good
outline of the boundaries of the spam infrastructure.   Bottom line:
 spammer domains do change frequently, and spammers often have a bunch of
servers.  But their servers do not actually change very much.   Obviously,
this means I have not yet been attacked by a thousand-member bot-net.

For spam received from ESPs, blocking on the From address works, because
the ESP does verify the client identity and does not allow clients to spoof
each other.   They just don't vet client integrity.    So I classify
messages arriving from the ESP into known-bad=block, known-good=allow, and
unknown=quarantine.   Forwarded messages will typically rewrite the SMTP
domain for SPF compliance.   This means that I no longer know that the
unclassified From address is from the untrusted ESP and therefore needs to
be quarantined.    DMARC is a great solution for authorizing ESPs to send
direct messages on behalf of a domain, because SPF did not work well for
those messages.   It is not a perfect solution for forwarded mail because
even unmodified messages are subjected to data loss during forwarding.

On Accountability:

A message from A to B to C to Gmail does not mean that Gmail has a
relationship with A.    Gmail is acting as your agent, and it does a pretty
good job of protecting you.    A to B to C do have a relationship with each
other, or one of them would have been bypassed.    For legitimate senders,
I expect that the organizational hops will be at most two:    the source
domain, and the outbound email filtering service used by the source domain.

Mailing lists should be the cleanest traffic on the internet, because it
should be a small matter for the list to verify sources and minimize risk
by rejecting even slightly-doubtful messages.    Yet we have had exchanges
about how mailing list do not want to sign messages because they think
it will make them accountable for what they forward.   They are accountable
for what they forward, with or without DKIM.

Auto-forwarding operations are much more problematic because they have
strong incentives to minimize false positives.   They are still
accountable, but they will be perceived by recipient as unreliable - the
same way that I handle my problem ESPs.

New vs Existing messages:

For these purposes, mailing list output is only a new message if the
mailing list is the only party responsible for its content.  I am focused
on identifying malicious and unwanted message sources, and the mailing list
is asserting that it is not the originating source.

DF

--


On Mon, Dec 7, 2020 at 12:15 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, Dec 4, 2020 at 7:58 PM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> First, lets begin with the obvious:   malicious messages come from
>> enterprises that are in the malicious message business.   They rarely send
>> just one message, and their content changes continually.   Therefore, my
>> priority is to block malicious sources.   Messages that are correctly
>> blocked on content, rather than source, are the canary-in-the-mine which
>> warns me that my sender blocks need to be tightened.
>>
>
> I was under the impression from my work in the anti-spam world that
> sources also change.  It's trivial to come from a new IP address or sign
> with a new domain name when I think you're blocking me.  Thus, negative
> reputations are generally not useful to accumulate long term.  On the
> contrary, the thing that's mostly reliable is static sources that have good
> reputations, because they tend to remain (mostly) static, and they work to
> preserve their reputations.  I tend to give them preferential treatment.
>
> If a message is not forwarded, every organization involved in its delivery
>> is assumed to have a relationship to the sender and therefore a shared
>> responsibility for the final product.   DMARC, SPF, and many spam filters
>> assume that the adjacent MTA is the only source that needs to be evaluated.
>>
> This seems overly general.  A message going from A to B to C to me here at
> Gmail means Gmail has a relationship with A?
>
> Forwarding introduces an intermediary organization which presumably
>> operates on behalf of the recipient, rather than the sender.   It is not
>> involved in the creation of the message and has no economic relationship
>> with most of the message sources.   More importantly, because it will be
>> forwarding messages from sources with a variety of reputations, the
>> forwarder will be perceived as having a very unreliable reputation –
>> sending both very much unwanted content and very much wanted content from
>> the same or overlapping identifiers.   SPF and DMARC force the forwarder to
>> reliably identify itself, but in this process, they force the forwarder to
>> hide information that the receiving MTA needs for proper message
>> filtering.  This aggravates any effort to filter based on original-source
>> identity.
>>
> I'm also confused here, because it's ambiguous what you mean by
> Forwarder.  Some forwarders simply replace the envelope and send the
> message on its way with no body modifications and only trace header field
> changes.  They don't meet the definition you're describing because no
> details are hidden.  Others, like MLMs, may mutate the message and re-post
> it, but I would argue that's not forwarding, that's a new message; the list
> is the originator.
>
> -MSK
>