IETF Logo Mail Archive

Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields

Dave Crocker <dcrocker@gmail.com> Tue, 02 June 2020 23:02 UTC

Return-Path: <dcrocker@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 D96A93A10EE for <dmarc@ietfa.amsl.com>; Tue, 2 Jun 2020 16:02:14 -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, FREEMAIL_FROM=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 URppgNW0gnXd for <dmarc@ietfa.amsl.com>; Tue, 2 Jun 2020 16:02:13 -0700 (PDT)
Received: from mail-ot1-x343.google.com (mail-ot1-x343.google.com [IPv6:2607:f8b0:4864:20::343]) (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 9FDA83A1129 for <dmarc@ietf.org>; Tue, 2 Jun 2020 16:02:11 -0700 (PDT)
Received: by mail-ot1-x343.google.com with SMTP id u23so305889otq.10 for <dmarc@ietf.org>; Tue, 02 Jun 2020 16:02:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=4udBsD/DOWQbUXf9NT7JRMWAlDaLHhs4xQ1q+1KNeF0=; b=jwT0S7RazL8HcvEmj9+bQYT4VK4f+dz5js6l3xtbxXekAms06ysNWCuAO5BH2DTp8n /Jr5dZiZojDbyNEh+joujPF8P22xa1B0z+8icp3dkvNBgb9Vn1Sjx75LXiNtYzFQUuWi jOju9j84J3voL+LrksqeWmv+OAOsI1VgfkFUdlLLWXSuFhLQD4L7UCmKSGjqHFMtN/7a hA2tscfYqImRrtH5XXpxygqa0b4rBHPbZWvKtfY1NEXJfK2sPdzlJd911+uQIKPvx/ZO Gm6OnAPd6u0r/6fs51Y3tOIisMdE0XT8j340jE4rTqwFSkTm2pKqJfpOQgoqzmj9ePvO HSrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=4udBsD/DOWQbUXf9NT7JRMWAlDaLHhs4xQ1q+1KNeF0=; b=MzfBVX7PwCEk4Vz0duyEaimdAhde6MfAUS938o7fJadBKy1l+ncd0QYwZbQbSyPo4A So+3D2/fSHg7ZpmijYIp4XP2szd6jenWY8/0DwYLL/INr2oG0aOIxGxBsJp/+3B+Fgan EFXffJACxizToZ1QR6I/ApjdBBAk8Fn0t+lKR5XmJ3iZznjcGewzf2wkTN5iM6CSdB4+ V1GYLpw5dvobnEmBu3QZEFxbKgSdRBatOzeGpy4+oqt7GHq4INYAAhWQMhY4bX1R0egD yy4Dmp1BhtvkZ+TT3QUSlEYB0kOerc18kZtRpaY2dJLSi85oDGHwz0terYTr82lMBvtw guOQ==
X-Gm-Message-State: AOAM532rPLemecFS4rjPVz284Xht0teqSGFpCtCF6JuZMKlVa0AfRHjP UCwsNNu0k2qUC55rGZHv6p86rwEX
X-Google-Smtp-Source: ABdhPJxns7suq5tRUAoojVK9cp2103hhj0BJ6fvluvTbv6nceBWFxieadaHx8FEc0I9tAf0Ang9zyw==
X-Received: by 2002:a9d:4703:: with SMTP id a3mr1075982otf.219.1591138930766; Tue, 02 Jun 2020 16:02:10 -0700 (PDT)
Received: from ?IPv6:2600:1700:a3a0:4c80:74d5:2e17:a5f6:1e77? ([2600:1700:a3a0:4c80:74d5:2e17:a5f6:1e77]) by smtp.gmail.com with ESMTPSA id d66sm128475oia.47.2020.06.02.16.02.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Jun 2020 16:02:10 -0700 (PDT)
To: Seth Blank <seth@valimail.com>, Dotzero <dotzero@gmail.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
References: <DM5PR0601MB367115AD49513EAF3953716CF68B0@DM5PR0601MB3671.namprd06.prod.outlook.com> <18441e8d-cf87-053e-4957-7b9d6ea9690c@gmail.com> <CABa8R6s7Lh_nihfH4Y8=JFCDFL6T_iEd+dBf7C=iW+5S3K4i3A@mail.gmail.com> <1093905c-7556-ab65-ae9f-6c97d1707878@gmail.com> <CAL0qLwYm=QnSLQ_n_+xq_vvEh47TJT+HXZKem5uKhtfRotKAbQ@mail.gmail.com> <c03d4ea4-20e1-12a6-9581-f51a81330ca5@gmail.com> <CAOZAAfO42WrYi6drByD=fdoU=1su-WO6nGH0OoEN1Txw2ONNvA@mail.gmail.com> <CAJ4XoYcyr-3Sdk+96AxJuKAjH124ziTLZV=1K__5ZF-ME3=G5Q@mail.gmail.com> <CAOZAAfMxVt8JsmXJcui-ejjvsjz3zdTegphA9jUJKQaVxEum-A@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <150bd1d9-dc9c-8183-308f-5e251caeac74@gmail.com>
Date: Tue, 02 Jun 2020 16:02:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <CAOZAAfMxVt8JsmXJcui-ejjvsjz3zdTegphA9jUJKQaVxEum-A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QyaEtBysgQNRWBo1x9tKcC7e2Pw>
Subject: Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields
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: Tue, 02 Jun 2020 23:02:21 -0000

On 6/2/2020 3:53 PM, Seth Blank wrote:
> The point I was trying to make is that consumers are susceptible to 
> fraud,

Of course they are.  Unfortunately, that point is irrelevant, because it 
isn't the question at hand.


> and the system needs to stop these messages before they ever get in 
> front of a user.

Exactly.  And that's why claiming that making the From: field domain 
name better (or worse) in changing recipient user behavior is wrong.


> The signal I was talking about is from the data: when something tries 
> to authenticate to an MTA but then tell the user it's someone else. 
> That's what alignment fixes and what's so powerful about DMARC.

Seth, your statement is so confused, I'm not sure I can fix it up. 
"Authenticate to the MTA?"  DKIM and DMARC don't do that.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email