Re: portable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 23 May 2022 03:12 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57120C3A4427 for <ietf@ietfa.amsl.com>; Sun, 22 May 2022 20:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level:
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z3t11nR1WIcv for <ietf@ietfa.amsl.com>; Sun, 22 May 2022 20:12:36 -0700 (PDT)
Received: from mail-yw1-f174.google.com (mail-yw1-f174.google.com [209.85.128.174]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14DC5C3A4426 for <ietf@ietf.org>; Sun, 22 May 2022 20:12:36 -0700 (PDT)
Received: by mail-yw1-f174.google.com with SMTP id 00721157ae682-30007f11f88so2145557b3.7 for <ietf@ietf.org>; Sun, 22 May 2022 20:12:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f4X2Qb4PIOXpz9udl/+ixvB+JL0FT6asRaHXudPLWUo=; b=LgT3cGZwKUwvWATeqIiSlsC6j7qC2i37NJXYY3c0UDKpXZfCjrVOhgXVyNB11OXvj7 0I3pyRH8SVMUjh3XMB3fgPoHo6YBzu5QE3fEyGu/Qool2odq1rgfJF0f9D7/kqV9gBwB xB7N0wxFvduuCEpER90OxYDr9kSIAVo3QjMGMiYO/ixs/LqO6REsoJV8fqFeqe28Zbmu 8J7suMx3pndMgUjcB/c5D9oAyeweRRI/AtDLzosl005SkJFG8yDtgFLcQBGszES6muqk 8Sn1R37YsQ2SLLz1I6KBSVx8CtvC5JmGyUGrtvhwhrNzvLHwpb9AhtWWcqdz4Xe3QUFW 1K4A==
X-Gm-Message-State: AOAM531lzIqbYHKkrXEqfFC6qCm8WjKNt2uw8JobyJ02cAjgPV5B8gUB O77ZI+VxH+quowPdlFWDC+nM8oHshiS/EqGssG6ytr3q
X-Google-Smtp-Source: ABdhPJzfeWbpSUsVSkOTvTC4LiNNuR/FfXcjB0PfhwCn+XOlyxecWamlLwZJtHOxu/OCau3yECPfxt7nr6MAALUMdBM=
X-Received: by 2002:a0d:cd81:0:b0:2ff:aa45:4238 with SMTP id p123-20020a0dcd81000000b002ffaa454238mr9605289ywd.155.1653275555124; Sun, 22 May 2022 20:12:35 -0700 (PDT)
MIME-Version: 1.0
References: <20220521010251.61FC7415A1F4@ary.qy> <889051.1653132607@dooku> <CAMm+LwieaYh7L3JpL6+e3z-AxMD0jBNfTR1RL_2F5a-ePhxM7g@mail.gmail.com> <064a5d75-5f05-6560-d5e0-4caad6d4faa6@network-heretics.com>
In-Reply-To: <064a5d75-5f05-6560-d5e0-4caad6d4faa6@network-heretics.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 22 May 2022 23:12:22 -0400
Message-ID: <CAMm+LwhStGXGYHVGDSE6NZK8R_PdK2i1c2WVpFtoP+F=+c8=qg@mail.gmail.com>
Subject: Re: portable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)
To: Keith Moore <moore@network-heretics.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002dd96d05dfa53698"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xxflaa5uOpV-DRL7nvAYlppu9CA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2022 03:12:38 -0000

On Sun, May 22, 2022 at 10:57 PM Keith Moore <moore@network-heretics.com>
wrote:

> On 5/22/22 15:14, Phillip Hallam-Baker wrote:
>
> The architecture of mailing lists sucks. It has always sucked. There is no
> way to implement a push messaging protocol that is not going to suck and a
> push messaging protocol without ubiquitous authentication is going to suck
> really bad.
>
> This says nothing about why, or how, it sucks.  I can guess, but it would
> probably help to know specifically what you mean.
>
The problem with a push messaging protocol is that anyone can gunk up the
mailboxes of the recipients with large amounts of data. So the receiving
server has to decide whether the user is going to want to accept or not and
that must inevitably be a guess at some level.

Authenticating the senders reduces the guessing somewhat but you still end
up having to limit message size. I can't email you a 400GB video file. But
I might easily want someone to edit a file of that size for me.

I am aware someone has an IMAP service somewhere for IETF lists and there
> have been NNTP services. But neither of those work with my mail clients.
> And configuring my clients to be able to post while accessing the mail that
> way sucks even worse.
>
> Perhaps, but unless your mail client is very odd, getting it to work with
> IETF's public IMAP server, or switching to a mail client that does work
> with that IMAP server, still seems like it should be easier than, say,
> getting your mesh system widely deployed.
>
I was not being precise about my problem which is actually the amount of
complaining that we get about these issues and the refusal to look at the
fundamental problem which is that there is an abuse issue and the only
solutions we have involve heuristics which are at root guesses.

I have much higher acceptance criteria for the user experience than most
folk. It is not laziness as I will spend a month coding to avoid the need
for my user to perform a single mouse click.


Keith
>
> p.s. Of course, mailing lists predated by 15-20 years anything resembling
> a fully-connected global network, even if you count on-demand dialup access
> as part of that network.  So if the architecture of mailing lists has
> really always sucked, at one time it at least sucked less than an
> alternative that would have required an interactive connection to either
> the sender's host or a central distribution server
>

I have a vintage computing collection too. I just keep it in museum cases
where it belongs.