IETF Logo Mail Archive

Re: [ietf-822] Expires header field

Jasper Spaans <jasper-rfc822@use.startmail.com> Wed, 09 November 2022 14:19 UTC

Return-Path: <jasper-rfc822@use.startmail.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F10CC1522C2 for <ietf-822@ietfa.amsl.com>; Wed, 9 Nov 2022 06:19:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level:
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=startmail.com
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 J_zIeZGcOwu4 for <ietf-822@ietfa.amsl.com>; Wed, 9 Nov 2022 06:19:53 -0800 (PST)
Received: from mx-out1.startmail.com (mx-out1.startmail.com [145.131.90.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6145FC1522A8 for <ietf-822@ietf.org>; Wed, 9 Nov 2022 06:19:53 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=startmail.com; s=2020-07; t=1668003589; bh=VOpLkZGGWR16z+EJ9NPdq1JeaXuaeDhuxvBAzYFMF9k=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To:From:Subject:To: Date:Sender:Content-Type:Content-Transfer-Encoding: Content-Disposition:Mime-Version:Reply-To:In-Reply-To:References: Message-Id:Autocrypt; b=Sz4LWqnmdD9MKPyo4IZhri/TCYzKLSNP1Pycuv/icx8HAEMF2NNEGEeyS1OtakSW9 mDerLf+V6EwuEdUYEOT1LSbQBYMVB7Om1dLd1cxLVd828a7WVj3eEzbvsQtJUclan0 GvtFR734AkjVnPxgBam9STcaAf54jf7R34+ng5VKrDGTwrgunbqbG6SNZlkr40SY+Z KvdRAGA6U1+wWJFNTP307GlkP9+tv+tuuhUWEiHNRJ3z18J4T1FF1BhZE4hFFLGQDb fyyXZHvp8ti9tCFqDHZDYLv1xQj5XC2ZZBY8dirNBzJTszXq7REikBRPFhvEsxd87e ebZN+qubt3QZQ==
Mime-Version: 1.0
From: Jasper Spaans <jasper-rfc822@use.startmail.com>
In-Reply-To: <CAL0qLwa+yJkczF3TqepSVEvjMABzc0HR9-LLS3ejAUPt2A83vQ@mail.gmail.com>
Date: Wed, 09 Nov 2022 15:19:38 +0100
Cc: ietf-822@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC3686B2-4832-4269-81A0-0A3CC116D879@use.startmail.com>
References: <CAL0qLwa+yJkczF3TqepSVEvjMABzc0HR9-LLS3ejAUPt2A83vQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/bn-g48NRJjmSsF6mzUjLW3As8QQ>
Subject: Re: [ietf-822] Expires header field
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 14:19:58 -0000

> I have received a request to sponsor and publish this document:
> 
> https://datatracker.ietf.org/doc/draft-billon-expires/
> 
> This is mostly just a change of state for this header field.
> 
> Before I send it to an extended Last Call, I wanted to prompt here for any feedback, support, etc.  Please have at it.

I'm a big fan of this standard, and would like to extend it to the other big mail standards family: IMAP. Is this proposal enough substance to get an $expired keyword into the https://www.iana.org/assignments/imap-jmap-keywords/imap-jmap-keywords.xhtml list? Or would that require another section in this document, or a secondary RFC dedicated to that?
It would be very useful to be able to do server-side filtering on such a flag, and I can imagine IMAP servers having support for exposing such a flag based on the presence and status of an expires header (a bit like the existing $recent flag -- clients cannot set it, but the server will return it when appropriate), but afaik such processing inside IMAP servers is still vaporware right now.


Best regards,
Jasper Spaans
StartMail.com

v2.23.0 | Report a Bug | By Email