IETF Logo Mail Archive

Re: [Extra] imap4rev2 route

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 11 December 2019 14:43 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 591B9120041 for <extra@ietfa.amsl.com>; Wed, 11 Dec 2019 06:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 LQNOvNvoE9nN for <extra@ietfa.amsl.com>; Wed, 11 Dec 2019 06:43:26 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B53B9120033 for <extra@ietf.org>; Wed, 11 Dec 2019 06:43:25 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 5C106C0201; Wed, 11 Dec 2019 14:47:23 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1576075643; bh=eqKgTg6rM3LdkUb6ZArqaK86xV0sXTo7wrPHOzPR2jI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aJ7EdIuOaN9Q17cn0XaN90d2ut7XRzoogQ3mmnVNNM5wRyfP2Sa8/PD/D4wxgsLE8 5T/nNjnZKwfJxgsT7dAzAI/EFo/ezA7YYlKrXSY11ME/inDFIo1XkyCnKBr4o6YOKd vyD/LI9nWSzq1RATekrrbBoqLjyWEOKeEmDtK/Ao=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1576075642-3866-3863/9/31; Wed, 11 Dec 2019 14:47:22 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org
Date: Wed, 11 Dec 2019 15:43:21 +0100
Mime-Version: 1.0
Message-Id: <548400ec-2266-4edf-b289-18cb537e0d8d@gulbrandsen.priv.no>
In-Reply-To: <3c0f5ae6-ae0b-1455-dd59-d46560abf5ff@isode.com>
References: <97DD9939-085B-40FA-844D-056A418ABC01@sirainen.com> <3c0f5ae6-ae0b-1455-dd59-d46560abf5ff@isode.com>
User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.1 (ascii)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/bslZitVVUg8B1HN3GBpCTkNd_Q8>
Subject: Re: [Extra] imap4rev2 route
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2019 14:43:27 -0000

On Wednesday 11 December 2019 14:39:07 CET, Alexey Melnikov wrote:
> I think the answer to this is whether or not you want to 
> preserve fidelity of very old messages. I agree there is no 
> reason to generate source route, but I am not sure that 
> IMAP4rev2 is the right place to deprecate its use.

I assume that "use" means "display" in this paragraph? Timo isn't 
suggesting to forbid anyone from sending source routes, he's effectively 
suggesting that IMAP4rev2 suppress their display.

Does anyone on the list have a largish collection of clients and a 
convenient way to test? I suspect that a majority of recent clients already 
do suppress the source routes. If that is correct, then suppressing them in 
the protocol has advantages and no real cost.

Arnt

v2.23.0 | Report a Bug | By Email