Re: [ietf-smtp] SMTP server reply extensions

Tony Finch <dot@dotat.at> Wed, 08 April 2020 17:41 UTC

Return-Path: <dot@dotat.at>
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 8A21E3A14BD for <ietf-smtp@ietfa.amsl.com>; Wed, 8 Apr 2020 10:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 djbdWAf845qw for <ietf-smtp@ietfa.amsl.com>; Wed, 8 Apr 2020 10:41:28 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (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 C0C4A3A14BC for <ietf-smtp@ietf.org>; Wed, 8 Apr 2020 10:41:28 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:34772) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1jMEha-000DE9-eT (Exim 4.92.3) (return-path <dot@dotat.at>); Wed, 08 Apr 2020 18:41:26 +0100
Date: Wed, 8 Apr 2020 18:41:26 +0100
From: Tony Finch <dot@dotat.at>
To: Timo Sirainen <timo@sirainen.com>
cc: ietf-smtp@ietf.org
In-Reply-To: <8CF389F4-7BD3-44D0-85F4-91E66120A59B@sirainen.com>
Message-ID: <alpine.DEB.2.20.2004081834160.27062@grey.csi.cam.ac.uk>
References: <8CF389F4-7BD3-44D0-85F4-91E66120A59B@sirainen.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/M2mNOpGelhM-ngv7c7S0XJRTxL8>
Subject: Re: [ietf-smtp] SMTP server reply extensions
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, 08 Apr 2020 17:41:31 -0000

Timo Sirainen <timo@sirainen.com> wrote:
>
> 1. IMAP-like login referrals (RFC 2221)

Jeremy gave you the suggestion I was thinking of :-)

> 2. Single instance storage for deliveries between backends in a cluster

You might be able to use RFC 4468 BURL to refer to an existing copy of the
message, but I don't have a good LMTPish suggestion for getting a URL
from the back end.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rattray Head to Berwick upon Tweed: Cyclonic 4 or 5 becoming variable 2 to 4,
then becoming east or southeast 3 to 5 later. Smooth or slight. Rain or
drizzle then fair. Good, occasionally moderate at first.