Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP

"John Levine" <johnl@taugh.com> Wed, 01 January 2020 18:42 UTC

Return-Path: <johnl@iecc.com>
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 764191200C4 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 10:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=jJxceXpL; dkim=pass (1536-bit key) header.d=taugh.com header.b=TL65mI1N
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 sFhWf-9Fzq0f for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 10:42:05 -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 1B4CA120044 for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 10:42:05 -0800 (PST)
Received: (qmail 78208 invoked from network); 1 Jan 2020 18:42:03 -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=1317d.5e0ce7fb.k2001; i=printer-iecc.com@submit.iecc.com; bh=vpJUksoRm5F9lrW6ry0H3XDFrHDpDWGmfHJs52KVXEk=; b=jJxceXpLmya+J6T0mWOc1u46eIeFYMSGjxr6M1HOIt/kg9ZB2wX5jU4HqOELOjHaJJ/vTrZR/WObxsM6n1xhSDJF2XabKrQ91Z/2MVcwvBtpBZkn3Mq9a7SnD//o+DUC8uaaFxs1Eg7DV2FYOXKJMqX7NIUrkbcJCHrz8iNxhrFqV3QEUoNw1KLvnQyXUVN1Tug2mz8SbvNnJLVKgKAbJOczjelaQyNSP3RVLURzApI6LuzLUSutzLTIcIqgvOfK
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=1317d.5e0ce7fb.k2001; olt=printer-iecc.com@submit.iecc.com; bh=vpJUksoRm5F9lrW6ry0H3XDFrHDpDWGmfHJs52KVXEk=; b=TL65mI1NXCKbbZKKexb9NxrU9ybHxLC5fTVjZy0/hN8KJ/2k9xH4HQhg0eI7rMEoMw7ERUTAFJJfNVgDf2vmODE7FPAHBxFKFEqgCrGbKd8r2S1XOApnIMNfTqi/jXCWkFrbydNkixyjvrj2B+Wq72aTXT0yWFYHFfOBR/I6v7+ag+1JLHNXarmmy9tLb6KRQwZtjkoTNAdGRUcEIlmo1ya5KLvO1v2p55uemCPUuxLUXGvlud8vTvv4fJZqE4UC
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 ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 01 Jan 2020 18:42:03 -0000
Received: by ary.qy (Postfix, from userid 501) id 3F7AA11E2EAD; Wed, 1 Jan 2020 13:42:02 -0500 (EST)
Date: Wed, 01 Jan 2020 13:42:02 -0500
Message-Id: <20200101184203.3F7AA11E2EAD@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: moore@network-heretics.com
In-Reply-To: <994e7a23-9e80-4751-6067-8863ad0ee72f@network-heretics.com>
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/ietf-smtp/67awBfPC8eDWnvnaGuqSgXTFcZw>
Subject: Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP
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: Wed, 01 Jan 2020 18:42:07 -0000

In article <994e7a23-9e80-4751-6067-8863ad0ee72f@network-heretics.com> you write:
>And since this would be entirely new practice, it would at least be 
>possible to require Organization Validation or Extended Validation 
>certificates as a condition of accepting mail, or more likely, as a 
>condition of not pessimizing mail... and/or set up email-specific CAs 
>for the purpose of authenticating SMTP clients.

It's still a WKBI.  Whitelisting by source doesn't work at scale, and
for source scoring, I don't see any reason that a cert would tell you
anything more useful than an IP and a host name.  It's not like we have
any trouble now telling when mail is coming from Google or Yahoo or
the university down the road.

R's,
John