Re: [ietf-smtp] DKIM and DMARC, Email explained from first principles

Dave Crocker <dhc@dcrocker.net> Tue, 25 May 2021 01:42 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82C143A0913 for <ietf-smtp@ietfa.amsl.com>; Mon, 24 May 2021 18:42:25 -0700 (PDT)
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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=dcrocker.net
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 CMvQbYQR7dzw for <ietf-smtp@ietfa.amsl.com>; Mon, 24 May 2021 18:42:20 -0700 (PDT)
Received: from purple.birch.relay.mailchannels.net (purple.birch.relay.mailchannels.net [23.83.209.150]) (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 98AE13A0912 for <ietf-smtp@ietf.org>; Mon, 24 May 2021 18:42:20 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id F1A375A10DB; Tue, 25 May 2021 01:42:18 +0000 (UTC)
Received: from nl-srv-smtpout3.hostinger.io (100-101-162-48.trex.outbound.svc.cluster.local [100.101.162.48]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id DB44D5A17D4; Tue, 25 May 2021 01:42:17 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout3.hostinger.io ([UNAVAILABLE]. [145.14.159.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.101.162.48 (trex/6.2.1); Tue, 25 May 2021 01:42:18 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Reign-Spot: 0f7fd4bd7264b483_1621906938722_4095921865
X-MC-Loop-Signature: 1621906938722:3598247487
X-MC-Ingress-Time: 1621906938721
Received: from [192.168.0.111] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout3.hostinger.io (smtp.hostinger.com) with ESMTPSA id 8673231F59FF; Tue, 25 May 2021 01:42:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1621906936; bh=XrYu374WoZZgx4aZSn8FYE1qGzNOLAHdoqBq1M57Ylw=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=USew34YF/onazDaCJD88+5p3Ve/jqbs6J0z1IXF6OzdDEARe1d7GhFHlOQ1eKb50t /7ahpUOl0kMPdAuvVxW/tY8Sde5IryQEFuW48Q1Iax0xdkpITxkKuRFEdwlBJMHycN vOyt3p/9bU3ytn+XG5QD+kOVNEIq3WF2dyCbFZOQt7GHDFb4Ivi0plVaGhqDW9DWTZ HnYB6S4F04Jt/8G+L1qRqQ5VwSe6885ujht4EbUyFDEk9aM/erMWGcS2BMatPIIX/q w8nO8n+eCLwkdwXVTE+3fvlDOsmiFVQNRR9V7+hhlBVKdcyOEfcFRIY3HRveq2Sm9a 1ElgcZ0zcB21w==
Reply-To: dcrocker@bbiw.net
To: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Cc: mrsam@courier-mta.com
References: <20210525012345.E42AE8A790D@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <ec4bc748-c61d-4f83-6327-0374f979ecc5@dcrocker.net>
Date: Mon, 24 May 2021 18:42:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <20210525012345.E42AE8A790D@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/20MppHuKczExO3g57C3I0srWZKE>
Subject: Re: [ietf-smtp] DKIM and DMARC, Email explained from first principles
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 May 2021 01:42:26 -0000

On 5/24/2021 6:23 PM, John Levine wrote:
> For DKIM, the point is to have a reliable identifier for the message
> that is better than an IP address.

yup.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net