[mailmaint] A mailbox provider's view of Expires

Richard Clayton <richard@highwayman.com> Mon, 04 November 2024 18:52 UTC

Return-Path: <richard@highwayman.com>
X-Original-To: mailmaint@ietfa.amsl.com
Delivered-To: mailmaint@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A19C23D0A0 for <mailmaint@ietfa.amsl.com>; Mon, 4 Nov 2024 10:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=highwayman.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 Up2EIvSAF_Bg for <mailmaint@ietfa.amsl.com>; Mon, 4 Nov 2024 10:52:48 -0800 (PST)
Received: from mail.highwayman.com (mail.highwayman.com [82.69.6.249]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F08C23A85F for <mailmaint@ietf.org>; Mon, 4 Nov 2024 10:52:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=highwayman.com; s=rnc1; h=MIME-Version:Subject:From:To:Date:Message-ID: Sender:Reply-To:Cc:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=X/5ouP26iqcKuMSEw8GnF6KvgCTdNssD42WTwGYlAIk=; t=1730746368; x=1731610368; b=o/nQErBSm3HLjqwbYiT1/kVBlPpZt6jgwa8QcZHkH4OmcPxvKrK+IbyiSaZ/MU+CSjHMYXvWAqV IcBuUv7P4/c+JYS1qgW8Ygw58JT8HOSzDJmuNp9GKk03C4Hm+uQ07Zb2d69yOwC7BZWVGquWnQpma pv/de9rMSXtE9xD6Mca9lNBRe7JcvkA0qcsQ/iARoWOEdqm4ZqJ6nbNT2YwY4WqwJxzWSB1QcTqF+ HBDK751ruMDq6kYe9RqUWtP/qbSmfQFif0azA9UGiR3xiToDoLjNZEKx6wQ2AZX8dQjP/dOs/5Rzc dxJycwI4nOCSlK3/f0UXSnxWOvRzCVpEzr/w==;
Received: from [127.0.0.1] (port=36449 helo=happyday.al.cl.cam.ac.uk) by mail.highwayman.com with esmtp (Exim 4.98) (envelope-from <richard@highwayman.com>) id 1t81kQ-00000000IV3-2R6K for mailmaint@ietf.org; Mon, 04 Nov 2024 18:24:18 +0000
Message-ID: <KVphjhMi+QKnFAHO@highwayman.com>
Date: Mon, 04 Nov 2024 18:17:06 +0000
To: mailmaint@ietf.org
From: Richard Clayton <richard@highwayman.com>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.03 M <fF4$+DqT77PqPMKLvGU+duZxou>
Message-ID-Hash: C2KTJCVEX3NMKTYOI4LIFJUKG7NFMP7K
X-Message-ID-Hash: C2KTJCVEX3NMKTYOI4LIFJUKG7NFMP7K
X-MailFrom: richard@highwayman.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mailmaint] A mailbox provider's view of Expires
List-Id: Mail Maintenance <mailmaint.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mailmaint/MgtSuOJFfgWbTFuAZjGwXNDMcqo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mailmaint>
List-Help: <mailto:mailmaint-request@ietf.org?subject=help>
List-Owner: <mailto:mailmaint-owner@ietf.org>
List-Post: <mailto:mailmaint@ietf.org>
List-Subscribe: <mailto:mailmaint-join@ietf.org>
List-Unsubscribe: <mailto:mailmaint-leave@ietf.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I have been consulting with colleagues at Yahoo about the Expires:
proposal.

In our view the current proposal is too vague to be of any use to
anyone. As mailbox providers we are expected to "de-emphasise" expired
messages. That could mean we put them in an archive, hide them from
searches, display them in a different font, or pretty much anything
apart from not doing something useful like moving them to "trash" or
refusing to accept messages such as password resets that have been so
delayed as to be useless to the recipient.

Since mailbox providers who bother to implement anything at all are
likely to make different choices we do not see that the header is of
much practical use to senders either because they can have no well-
founded expectation as to what will occur.

That said we can see some use cases for marking particular emails as
having a "best before" or "use by" date (food labelling distinguishes
between perishable items that may be of lower quality , or may be unsafe
to consume, once a certain time is reached).

We encourage the working group to scrap the current draft and to work on
specific use cases:

        password reset and account recovery;

        marketing email with time-limited offers;

        meeting invitations;

to name just three.

We would be happy to consider supporting well-specified semantics where
it is crystal-clear to all concerned whether out of date messages should
or should not be transported, displayed or stored somewhere specific.

- -- 
richard                                                   Richard Clayton

Those who would give up essential Liberty, to purchase a little temporary 
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBZykPot2nQQHFxEViEQI5hwCeO3mF5p4cNYRXxOWrKD88d6zFsRMAn0ER
nOEhB741xqpkMsUCuCryAft4
=jeyH
-----END PGP SIGNATURE-----