[Extra] RFC 9042 on Sieve Email Filtering: Delivery by MAILBOXID

rfc-editor@rfc-editor.org Thu, 01 July 2021 02:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 BA11D3A10F5; Wed, 30 Jun 2021 19:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Rowk_hcl-bJN; Wed, 30 Jun 2021 19:34:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 379993A10F1; Wed, 30 Jun 2021 19:34:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E4767F4076A; Wed, 30 Jun 2021 19:33:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, extra@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210701023350.E4767F4076A@rfc-editor.org>
Date: Wed, 30 Jun 2021 19:33:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/6Oo6_AQSzFkeCH0Q3kc6SFn6s7A>
Subject: [Extra] RFC 9042 on Sieve Email Filtering: Delivery by MAILBOXID
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: Thu, 01 Jul 2021 02:34:15 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9042

        Title:      Sieve Email Filtering: Delivery by 
                    MAILBOXID 
        Author:     B. Gondwana, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2021
        Mailbox:    brong@fastmailteam.com
        Pages:      8
        Updates:    RFC 5228

        I-D Tag:    draft-ietf-extra-sieve-mailboxid-09.txt

        URL:        https://www.rfc-editor.org/info/rfc9042

        DOI:        10.17487/RFC9042

The OBJECTID capability of IMAP (RFC 8474) allows clients to identify
mailboxes by a unique identifier that survives renaming.

This document extends the Sieve email filtering language (RFC 5228)
to allow using that same unique identifier as a target for fileinto
rules and for testing the existence of mailboxes.

This document is a product of the Email mailstore and eXtensions To Revise or Amend Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC