Re: [ietf-smtp] why I'm discussing the spam filtering problem

Keith Moore <moore@network-heretics.com> Mon, 05 October 2020 04:06 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 AAA133A0BE5 for <ietf-smtp@ietfa.amsl.com>; Sun, 4 Oct 2020 21:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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=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 lxJtKuXJuhCD for <ietf-smtp@ietfa.amsl.com>; Sun, 4 Oct 2020 21:06:28 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17F593A0BDF for <ietf-smtp@ietf.org>; Sun, 4 Oct 2020 21:06:27 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id C5838DF3 for <ietf-smtp@ietf.org>; Mon, 5 Oct 2020 00:06:26 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 05 Oct 2020 00:06:26 -0400
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=Pr/Krs iqjFMMH7RM0Y+OfpGs/tvCNFAaZo7sr3K0iKc=; b=hFZs1NRBUIyqUwa/aNxUpe 3XaHK28QStIGEdr5NzsNwvUesV8cJtGKPZjs4ApI8O/91GKeXeRMpCTp0DuReQMl p57nsDrbY7gAHaa9Oq4oXhnZIjAu2pLKo6Ja20L0eHayP70PchxBHfiC3hwMdgv8 p8QeP8aslsqx1cJzJNl63PrQXbtV7YMwgu7k5f6HcGXc4uM1ktxOGSLtcNjC6vlW /TBSxD0xlclNeo2B76EFBv7C+VRAjYClFIWYBz/ktBTEHppk38EMIAQDI4ovMUUq x4ZbcxFipfTUDjL2HisQ6ceBigLkZKAz0xMxPgYK1XSziOvoQdN3oSSWDSrG456g ==
X-ME-Sender: <xms:wpt6X2LJJTlURxIPmgBUYFnYUdkcnUdrWGVRKb5BeQhPqg8Vc0gEKw> <xme:wpt6X-LmUjKy2UQPFeS7yeQImdt4QAMgVIBWEMb0iQtZv63TsuFJny11cpRLrN6za F7nLnfVoykEZQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrgedugdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtderre dtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthifohhr khdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeevfeetudeigedtle dvvddtudefjeejffdvfeetjeeiueelgfdtgfegtdffkeetudenucfkphepuddtkedrvddv uddrudektddrudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:wpt6X2uyc7RNOIwoAcgHjISGtLHwnlZ3W3FN2Xb-RLnYRnhvTjqA5g> <xmx:wpt6X7aFFlGYtJHO6ifEpazQz5COWeNRurjdEz23QYEHEHsAP1LQ_w> <xmx:wpt6X9Y2xBY0UMVUzto6o2IyXo6I-Q_g3fVLiwBFK8Fk0omE7hAymw> <xmx:wpt6X9oVkl4gj9CgQZa-3BD5tbJoUyp8I4ygjPUFLuBowZZUpla1aQ>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id DFECD3064674 for <ietf-smtp@ietf.org>; Mon, 5 Oct 2020 00:06:25 -0400 (EDT)
To: ietf-smtp@ietf.org
References: <50ef6e2a-d25a-1a7b-9676-ccd910e2ddd8@network-heretics.com> <7794114.ycBYOQNFYP@zini-1880>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <9d765dfa-fc0c-778c-39c6-47ea028243c3@network-heretics.com>
Date: Mon, 5 Oct 2020 00:06:25 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <7794114.ycBYOQNFYP@zini-1880>
Content-Type: multipart/alternative; boundary="------------8D5A86DBB526E48C2B73A20F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/N1WPgGGxu-AYJS9D1dKLuw3KzTs>
Subject: Re: [ietf-smtp] why I'm discussing the spam filtering problem
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, 05 Oct 2020 04:06:30 -0000

On 10/4/20 11:48 PM, Scott Kitterman wrote:

> On Sunday, October 4, 2020 10:18:08 PM EDT Keith Moore wrote:
>> It's because I care about Internet email, and having it work well.
>> It's because I hate to see Internet email lose out to FacedOut and
>> LockedBook and Tooter and Frop and most of the other profoundly
>> dysfunctional toys that people use for interpersonal messaging these
>> days.   It's because (and I'll probably regret saying this) RFC821,
>> RFC822, and their descendants have actually held up fairly well in terms
>> of functionality, especially in comparison to these toys, though there's
>> clearly a need for improvement by now.
>>
>> I'd like to think that other people here also care about having Internet
>> email work well, but so far the loudest people just seem to be screaming
>> for their right to sabotage it.   Maybe there's some good intent and
>> good faith buried in those arguments, but it's hard to see.
> My advice would be stare harder.
>
> In my view, email without spam filtering would be totally unusable.

Well, in my experience, that depends.   I operate some accounts with no 
spam filtering, some with, using different accounts for different 
purposes.   That has worked fairly well for me.  I do get some spam on 
the unfiltered accounts, but not enough to be terribly bothersome, and 
it's certainly better to leave spam filtering off for those accounts 
than to risk losing a gig.

(I have other accounts that get horrendous amounts of spam despite 
having spam filtering.   I'm phasing those out but it can take a long 
time to update everyone's idea of your email address.)

> Spam filtering email may cause problems, but it is still a net benefit.
I do find spam filtering useful in some instances, but don't see a 
general net benefit.  Sometimes it's a win, sometimes it's a huge lose.

> It's necessary precisely because email is such a great messaging system.
I don't follow that.   Certainly spam filter is sometimes necessary, 
though, because email is so accessible.
> What's your solution?  Don't filter and deliver everything isn't a solution.
> It merely transfers the problem to someone else.

Agree, but I wouldn't expect the optimum to be at such an extreme anyway.

I have some ideas, but I don't think I could work out the entire 
solution by myself.   And in an environment with as much hostility as 
this one, I don't think suggesting something that isn't both 
comprehensive and comprehensible is likely to produce any kind of 
constructive discussion.

Keith