IETF Logo Mail Archive

Re: [ietf-822] IMAP $expires, Expires header field

John Levine <johnl@taugh.com> Thu, 10 November 2022 16:43 UTC

Return-Path: <johnl@iecc.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 EBB3FC14CF12 for <ietf-822@ietfa.amsl.com>; Thu, 10 Nov 2022 08:43:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level:
X-Spam-Status: No, score=-1.858 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=iecc.com header.b=IU76odVs; dkim=pass (2048-bit key) header.d=taugh.com header.b=Shv6/2fa
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 6ZaKwtdnAQtF for <ietf-822@ietfa.amsl.com>; Thu, 10 Nov 2022 08:43:23 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 C424CC14CF0B for <ietf-822@ietf.org>; Thu, 10 Nov 2022 08:43:20 -0800 (PST)
Received: (qmail 2327 invoked from network); 10 Nov 2022 16:43:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=912.636d2a27.k2211; bh=NPbTzrZVork4WrISGNvltLNf/loiZh+k4uAHzewejHM=; b=IU76odVsE9COKkRSu54r9q5RUzTd7exNUnFDRjEr6T47IoydpEeGa0Hf29YhiPct1BkSccRXkqOLAMn7qKIDN7xgcGBgVlRO2aHTYfqyxhtGYTI6AYoM92cu3T5o/GwwSL0QUfWEeUllTrIorlbWFT+xwLZrOt7O1sB4C+NGgeVBrxF1dxDSXZYt3f8rh5/aYU/NCQR+hWsnwqpqicLVsoyzxaMWEXzBxTzJZZviUKAWuOHawRnShxOaFf04I24u+S/ShmrICl5ca6Iv4Ahaih+aI1MMLckU4Q0DITbv/9+zrsllPYvdFh2lad6T+Oqnm4G0yaq73xr7r0QM4ZKrtg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=912.636d2a27.k2211; bh=NPbTzrZVork4WrISGNvltLNf/loiZh+k4uAHzewejHM=; b=Shv6/2fau9AMgeo1Ow18RxN8mnq6dVyEc/z8SpNygxmae6+l8BsJ4g0bMbrRAfbiQMKGEvXrkzLm/ohqLc/Bjg0kS4EBQnucY2yLaOsKXnwU73y24mQr1P4mpLDei66j5VyPHgil5TYGIEt2DSCV4IuVQhCQ32nYs/HdIzUOeih4jZ1yndfrDi3y+7677Zea2qmAxubMDMllRMvN3R2O7LG/QFHdZbpEIrCWNxHZh6IxZ1dbWaDLih24tHdYeWyLwbS0A5Ov16/o6Crfim9ML8PqYduHjfJVEsW2VlnvBoty7K6GeJ3RZoLdVFPWk4zKvGiAMJkraFuWbLlS8A1umw==
Received: from dhcp-862b.meeting.ietf.org ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 10 Nov 2022 16:43:18 -0000
Received: by dhcp-862b.meeting.ietf.org (Postfix, from userid 501) id 100D44ECFEA2; Thu, 10 Nov 2022 16:43:17 +0000 (GMT)
Date: Thu, 10 Nov 2022 16:43:17 +0000
Message-Id: <20221110164318.100D44ECFEA2@dhcp-862b.meeting.ietf.org>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: jasper-rfc822@use.startmail.com
In-Reply-To: <AC3686B2-4832-4269-81A0-0A3CC116D879@use.startmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/Z8vI4LvCoTg05P-CTesvr24PQK4>
Subject: Re: [ietf-822] IMAP $expires, 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: Thu, 10 Nov 2022 16:43:29 -0000

It appears that Jasper Spaans  <jasper-rfc822@use.startmail.com> said:
>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?

I asked in the JMAP meeting and people agreed that so long as it's a
binary flag, message is expired or not, it would be straightforward to
implement so why not.

If you want to write a draft I can help with the IETF-ese.

R's,
John

PS: The JMAP group only meets three times a year, so your timing was really impressive.

v2.23.0 | Report a Bug | By Email