IETF Logo Mail Archive

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

Keith Moore <moore@network-heretics.com> Mon, 30 December 2019 02:25 UTC

Return-Path: <moore@network-heretics.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 CDB071200E5 for <ietf-smtp@ietfa.amsl.com>; Sun, 29 Dec 2019 18:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 qv64i8ic1fK2 for <ietf-smtp@ietfa.amsl.com>; Sun, 29 Dec 2019 18:25:55 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469E412006F for <ietf-smtp@ietf.org>; Sun, 29 Dec 2019 18:25:55 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 66CAD21C48; Sun, 29 Dec 2019 21:25:54 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sun, 29 Dec 2019 21:25:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=j3O9Te 1m7l2CAxAz0F9wbHohzOnXiP5Pu5B1zQbr/Ts=; b=tmuiyZlukkAlubP2FZuNQN SsQLksx5EIdyZA60vr6JwPpyF1CvrLz76waNJnYbd2EYysUWrqaJlLxuJrOifJZJ gTItIFW9Slq1l5Rv9sIXYnqb8pCLgkuUn1W55D/KifoU3wCLkbAqhETogulYyKai jNLn9efLyWFOkdpA30OvY68zboemDhoS7VhMv4++Tz9r5GPYMmxTRL2CmWHnHDyU 1jLB0GMbXSOibs7TneqUXTEUrEGlVDl2VIRe0wwCO7Fk/DdlvENZhd0PlsD8xxHW 2Qo8h63OUx4Hlvhu1fEby3oUnflGCXbvNMcSePQ584vXI29CeOkUmwTBscej9buQ ==
X-ME-Sender: <xms:MmAJXpBq1Hrc_WqCpNGikH7arDpJovugNXMSlEzD4SlsJpr6maACTw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdefgedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpefmvghithhh ucfoohhorhgvuceomhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhmqe enucfkphepuddtkedrvddvuddrudektddrudehnecurfgrrhgrmhepmhgrihhlfhhrohhm pehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:MmAJXge0oCZD79RYdrxN304I_yYPOa2yJdM4ieNNVXzQkyjT9sKq0A> <xmx:MmAJXtUWG0PCDIGuB6yIIdyjQi3UxWgFYyCt8UfF5rFpwab8jZ9Rdw> <xmx:MmAJXm4x8tU3xJMJC0F5rrkZvB0lGjUIN9iiK7Mu6ELBd1QgzyB3ag> <xmx:MmAJXhwRbtCvks4EApXw0Oac-vfguZ6Eh-LXi0-9gCk5SGC_kJCMgw>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id B010780060; Sun, 29 Dec 2019 21:25:53 -0500 (EST)
To: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
References: <20191230013034.2C3E111D376E@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <f894c448-ac91-6d27-98d6-0803de4ea535@network-heretics.com>
Date: Sun, 29 Dec 2019 21:25:53 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191230013034.2C3E111D376E@ary.qy>
Content-Type: multipart/alternative; boundary="------------A67B1A063311596B65C117C0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/d7wc41zyiJJHAflaH9Qd_4OEXBA>
Subject: Re: [ietf-smtp] Possible cont4ibution 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: Mon, 30 Dec 2019 02:25:57 -0000

On 12/29/19 8:30 PM, John Levine wrote:

>> IMO most of the spam-filtering criteria I've seen are countermeasures
>> for short-term, local, and/or ephemeral conditions. ...
> I'm guessing that the spam filtering criteria you're describing bear
> little resemblance to the stuff we talk about at places like M3AAWG
> with people who run systems that filter billions messages a day every
> day.  One of the reasons we can talk about them at M3AAWG is of course
> that the discussions there are not public.

So they're not subject to outside scrutiny.  No wonder email delivery is 
so unreliable.

Keith

v2.23.0 | Report a Bug | By Email