
From nobody Wed Jun  2 11:20:21 2021
Return-Path: <ned.freed@mrochek.com>
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 318483A15A1 for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 11:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
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 puKO___7MsTe for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 11:20:14 -0700 (PDT)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B74893A15A4 for <extra@ietf.org>; Wed,  2 Jun 2021 11:20:14 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RZRE8Z8BXC008N98@mauve.mrochek.com> for extra@ietf.org; Wed, 2 Jun 2021 11:15:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1622657709; bh=5t9eFrIJYdLiagSgHhqb4t0dE4Nuzizgk3hvjqdu7WM=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=fnCaZTAkN+NTu8v7G/CSe6S/nwe4DqUu+ZXNfZnT4Tx05nYGMtOU/Bb5EMU5t02bz GMzxSJDLUWpDr4viV21NEakKQo5Tjdfs5V/EBhf+VozvB36UfIXcH6Aa6XxTashLt+ ZTlB9fCW8a39v5+3Fe/dy17Tt4QqHNVpL+bsdDQM=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RZMX49RI1S0085YQ@mauve.mrochek.com>; Wed, 2 Jun 2021 11:15:06 -0700 (PDT)
Cc: extra@ietf.org, ned.freed@mrochek.com
Message-id: <01RZRE8TLZH40085YQ@mauve.mrochek.com>
Date: Wed, 02 Jun 2021 11:12:28 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 26 May 2021 22:23:27 -0400" <20210527022328.4BEFC8C9E39@ary.qy>
References: <01RZHH2IBJQ80085YQ@mauve.mrochek.com> <20210527022328.4BEFC8C9E39@ary.qy>
To: John Levine <johnl@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/vgykLfiNXpMO3w2Cmo6uwRghsoE>
Subject: Re: [Extra] New Version Notification for draft-bosch-sieve-eai-01.txt
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, 02 Jun 2021 18:20:19 -0000

> It appears that Ned Freed  <ned.freed@mrochek.com> said:
> >I'm afraid this document has a lot of probems, some of which may not be easy to
> >resolve.
> >
> >The biggest problem by far is that the idea of invoking an extension in order to
> >be able to process an EAI message is intrinsicly nonsensical: A message
> >presented to the Sieve interpreter is either an EAI message or it's not, and
> >there's nothing the Sieve interpreter or Sieve author can do to change that. (It
> >may not even know if a given message was intended to be in EAI format - there's
> >no reliable marker for this.) ...

> Yup.  I think it might be possible to redo this draft as advice on what a sieve
> implementation has to do to handle EAI mail, but your sieve code either handles
> EAI mail, in which case it makes sense to let it process EAI messages, or it
> doesn't, so the behavior with EAI messages is undefined.

I'll be happy to suggest text if there's consensus on it being recast as a client
issue, not an extension.

I do think an extension makes some sense in order to be able to redirect to
an EAI address or initiate new EAI messages.

It might also make sense for this to be split into two documents, one dealing
with compliance, the other with any extension. Or not - I have no real
opinion on the point.

				Ned


From nobody Wed Jun  2 12:00:36 2021
Return-Path: <stephan.bosch@open-xchange.com>
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 C8F8C3A182A for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 12:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
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 pkSUvIAqhSbz for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 12:00:21 -0700 (PDT)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CABE63A1784 for <extra@ietf.org>; Wed,  2 Jun 2021 12:00:18 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.217.131.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id 418116A0DB; Wed,  2 Jun 2021 21:00:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1622660416; bh=hqN74oU0orQmg7GZCE/hA076o+Fp6IfKV24sODWuDZE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=xtMhC8r/vV7R2x1t+xuErL0lbmiF+mTsRRoYaN+YadRRIqe54yUmRQREtKYQyLDXK nnC3Z5rVrTgBFt3+uEPROCEJA0qbZvYDG9VSk/5pum0pnrkurqLTodKmJM7T4sW0VC NgB1M/PC3LIw9baMCWGnkltZu1v3Sq5SS6VaOeWv+jXPREKlJxW5Fm35CRBPms95Yu rfBt7GXSez3ZyNz6Jt7yUfd9E9vv+wEoMgWCinmwVLOWfRxi7Nem/XpEEfai4zYwHV r0F2fmXqulfPdiksoVDykGX0r8Ec/CmcjP7UKB5ENNeXur5flarOWiyVMrj2fFf5S8 CjXK6UEAYlgWg==
Received: from [10.168.3.2] ([10.217.131.18]) by imap.open-xchange.com with ESMTPSA id mhf6C0DVt2D+OAAA3c6Kzw (envelope-from <stephan.bosch@open-xchange.com>); Wed, 02 Jun 2021 21:00:16 +0200
To: Bron Gondwana <brong@fastmailteam.com>, extra@ietf.org
References: <162197041125.31097.10318601097144383125@ietfa.amsl.com> <cfa2fc35-a68d-16fc-c05f-8fbae2cf07e4@open-xchange.com> <b4e89d86-1276-47f3-80ec-fa21e2fbee35@dogfood.fastmail.com>
From: Stephan Bosch <stephan.bosch@open-xchange.com>
Message-ID: <205b16ff-f199-c37c-77c5-0b9a61339e06@open-xchange.com>
Date: Wed, 2 Jun 2021 21:00:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <b4e89d86-1276-47f3-80ec-fa21e2fbee35@dogfood.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/GcX_6ImL5uuzQA5CbvJHBe8NIWs>
Subject: Re: [Extra] New Version Notification for draft-bosch-sieve-eai-01.txt
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, 02 Jun 2021 19:00:33 -0000

On 26/05/2021 14:53, Bron Gondwana wrote:
> Awesome.  Are you planning to progress this document further?  I was 
> about to email the list to see if there's interest in meeting at 
> IETF111, and that probably depends if we have any work to do :)

Well, yes, although I am not sure I have time to make progress on this 
very quickly. The aftermath of Corona infection of a months ago 
definitely is not helping. And I am not a great fan of the idea of a 
whole WG waiting for me to finish this. :)

Regards,

Stephan.


> 
> Cheers,
> 
> Bron.
> 
> On Wed, May 26, 2021, at 05:28, Stephan Bosch wrote:
>> Hi,
>>
>> This is just a refresh of the document submission. Apart from my address
>> information, nothing changed.
>>
>> -------- Forwarded Message --------
>>
>> A new version of I-D, draft-bosch-sieve-eai-01.txt
>> has been successfully submitted by Stephan Bosch and posted to the
>> IETF repository.
>>
>> Name: draft-bosch-sieve-eai
>> Revision: 01
>> Title: Sieve: Internationalized Email
>> Document date: 2021-05-25
>> Group: Individual Submission
>> Pages: 8
>> URL: https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.txt 
>> <https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.txt>
>> Status: https://datatracker.ietf.org/doc/draft-bosch-sieve-eai/ 
>> <https://datatracker.ietf.org/doc/draft-bosch-sieve-eai/>
>> Html:
>> https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.html 
>> <https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.html>
>> Htmlized: https://datatracker.ietf.org/doc/html/draft-bosch-sieve-eai 
>> <https://datatracker.ietf.org/doc/html/draft-bosch-sieve-eai>
>> Diff: https://www.ietf.org/rfcdiff?url2=draft-bosch-sieve-eai-01 
>> <https://www.ietf.org/rfcdiff?url2=draft-bosch-sieve-eai-01>
>>
>> Abstract:
>>     This document defines an extension to the Sieve language called "eai"
>>     which adds full support for internationalized email.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>> _______________________________________________
>> Extra mailing list
>> Extra@ietf.org <mailto:Extra%40ietf.org>
>> https://www.ietf.org/mailman/listinfo/extra 
>> <https://www.ietf.org/mailman/listinfo/extra>
>>
> 
> --
>    Bron Gondwana, CEO, Fastmail Pty Ltd
>    brong@fastmailteam.com
> 
> 
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 


From nobody Wed Jun  2 12:28:42 2021
Return-Path: <stephan.bosch@open-xchange.com>
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 9F0483A181D for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 12:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
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 d7iswDB98pmQ for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 12:28:35 -0700 (PDT)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9485B3A181C for <extra@ietf.org>; Wed,  2 Jun 2021 12:28:35 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.217.131.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id 081CC6A0C9; Wed,  2 Jun 2021 21:28:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1622662113; bh=d7AZHdBr8eLSHSHRs8iW9+gWFQ6zYTKkbgTAoHC8iXc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=gZR4ulIhlJxa26h6gAso2L4nIxEn2t/hK1v5iEftv0Hd21QzEEJKD3CwLXYXWNxV5 aQhsP/OKBfrneSprnQJUfgWtWBVtjjwnx6gsUlpQACIXkK50MMmJZRWz6Mgm/rHx5x oZWlcwp9n6JjfnCFYk/L6tGA7IWeBMhxLSv5WmYpalD1dFJpZDZEoutkHsFS0tQpKH HWi1nE/LEJ6udCs8UyK6lusO+uEiwJ/7U8U3svmwW4r1yxLgVpPHJ/et3Zrb0ALJ7i OstVFaEr7V2qbhXT+HsU/cEqMKVgEQOzd3r6aYpzCZ/ATf33u9/Z/gSYKaI4dEbvmA R7NSoADg1+AEQ==
Received: from [10.168.3.2] ([10.217.131.18]) by imap.open-xchange.com with ESMTPSA id Qtp5OeDbt2AVPwAA3c6Kzw (envelope-from <stephan.bosch@open-xchange.com>); Wed, 02 Jun 2021 21:28:32 +0200
To: Ned Freed <ned.freed@mrochek.com>, Stephan Bosch <stephan.bosch=40open-xchange.com@dmarc.ietf.org>
Cc: extra <extra@ietf.org>
References: <162197041125.31097.10318601097144383125@ietfa.amsl.com> <cfa2fc35-a68d-16fc-c05f-8fbae2cf07e4@open-xchange.com> <01RZHH2IBJQ80085YQ@mauve.mrochek.com>
From: Stephan Bosch <stephan.bosch@open-xchange.com>
Message-ID: <848b0844-4bb3-20d5-f712-0be27a292469@open-xchange.com>
Date: Wed, 2 Jun 2021 21:28:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <01RZHH2IBJQ80085YQ@mauve.mrochek.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/0kNTySApNSBux752D809_9pbBps>
Subject: Re: [Extra] New Version Notification for draft-bosch-sieve-eai-01.txt
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, 02 Jun 2021 19:28:41 -0000

Hi Ned,

(Ugh.. why does Thunderbird make a mess of quoting your message...)

On 26/05/2021 15:27, Ned Freed wrote:
> I'm afraid this document has a lot of probems, some of which may not be 
> easy to
> resolve.
> 
> The biggest problem by far is that the idea of invoking an extension in 
> order to
> be able to process an EAI message is intrinsicly nonsensical: A message
> presented to the Sieve interpreter is either an EAI message or it's not, 
> and
> there's nothing the Sieve interpreter or Sieve author can do to change 
> that. (It
> may not even know if a given message was intended to be in EAI format - 
> there's
> no reliable marker for this.)
> 
> And now things start to get sticky: There's no telling what will happen 
> if you
> feed an EAI message into a Sieve implementation that's not itself EAI 
> aware.
> Will it simply process the UTF-8 it finds by leaving it alone (likely)? 
> Or will
> it treat the UTF-8 it finds in headers as illegal - whatever that means? 
> Will it
> know that message/global contains a message, and if so, will it be able 
> to look
> inside of an encoded message/global (probably not)?

> 
> The ineluctable conclusion here is that an email system that supports 
> both EAI
> and Sieve in a compliant way MUST support EAI in Sieve. This is a 
> compliance
> matter, plain and simple, and cannot be handled as an extension. So the 
> first
> task of this document needs to be to define what this form of compliance 
> means.
> It definitely includes saying that the header and address tests must 
> allow for
> unencoded UTF-8, proper handling of message/global, and probably a bunch of
> other stuff.
> 

Yes, that is all true and I agree. But wouldn't it also be necessary to 
know whether the script author is expecting message/global messages? The 
eai extension would indicate that the script was written with the 
possibility of receiving message/global in mind. I haven't read the 
relevant RFCs in a while (and not going to right now), but what is 
supposed to happen when the server has EAI support but the mail 
retrieval agent (IMAP client) does not? I remember something about 
downgrade or placeholder messages. Most solutions I'd imagine would be 
far from ideal. The most crude solution could be to make the recipient 
server reject message/global outright when it somehow knows the 
destination user doesn't have the software installed to read the 
messages. Our software doesn't do much of the EAI stuff yet, so I can't 
say I have implementation/deployment experience. My point is: forcing 
Sieve scripts to handle EAI messages when they were not written with 
such messages in mind could pose problems. What to do? I don't know...

Also, the ManageSieve client would need to know somehow that EAI is 
supported by the server. It could connect to IMAP first and find out, 
but I think that is not the way to handle this. Of course this could be 
a ManageSieve capability then and not a Sieve extension.

> But now things get even stickier: A-labels. EAI extends the message 
> format to
> allow, among other things, U-Labels in domains, but AFAIK doesn't 
> explicitly say
> that A-Labels cannot be used. (Except in the case of domains in trace 
> fields,
> and as a recent discussion has shown, it appears this requirement is being
> widely ignored.)
> 
> Domains appear in a lot more header fields than addresses, and it would be
> asking a lot of a Sieve implementation to know how to parse them all and 
> convert
> A-labels to U-labels. FWIW, I think the right answer is to only perform the
> conversion in the address test, but I could be persuaded  otherwise.
I'd say all Sieve bits that compare addresses (address test, vacation 
:addresses etc.) or domains should normalize them in several ways, 
including the A-label/U-label format.

> 
> Redirect, vacation, notify, and any other action that sends a message 
> are where
> an smtputf8, as opposed to an eai, Sieve extension makes sense. And note 
> that
> all of these actions can send an EAI even if the original message wasn't 
> EAI.
> 

Agreed.

> A careful review of every Sieve extension with an eye to how it interacts
> with EAI needs to be done, but that should be deferred until we're settled
> on the overall approach.
> 
> Finally, I note that there's some odd language in the current document
> about not interpreting encoded-words in EAI messages. This makes no sense
> to me as messsages are often Frankensteinian in origin and can easily
> end up with a mix of UTF-8 and encoded-words.

I guess you're right. It's been a long time since I wrote this, but I 
think I must have picked this up from one of the RFCs, as I find it 
unlikely that I came up with this restriction myself. I'll look that up 
when I continue writing.

Regards,

Stephan.

> 
>                  Ned
> 
>> Hi,
> 
>> This is just a refresh of the document submission. Apart from my address
>> information, nothing changed.
> 
>> -------- Forwarded Message --------
> 
>> A new version of I-D, draft-bosch-sieve-eai-01.txt
>> has been successfully submitted by Stephan Bosch and posted to the
>> IETF repository.
> 
>> Name:        draft-bosch-sieve-eai
>> Revision:    01
>> Title:        Sieve: Internationalized Email
>> Document date:    2021-05-25
>> Group:        Individual Submission
>> Pages:        8
>> URL:            
>> https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-bosch-sieve-eai/
>> Html:
>> https://www.ietf.org/archive/id/draft-bosch-sieve-eai-01.html
>> Htmlized:       
>> https://datatracker.ietf.org/doc/html/draft-bosch-sieve-eai
>> Diff:           
>> https://www.ietf.org/rfcdiff?url2=draft-bosch-sieve-eai-01
> 
>> Abstract:
>>     This document defines an extension to the Sieve language called "eai"
>>     which adds full support for internationalized email.
> 
> 
> 
> 
>> The IETF Secretariat
> 
> 
>> _______________________________________________
>> Extra mailing list
>> Extra@ietf.org
>> https://www.ietf.org/mailman/listinfo/extra
> 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra


From nobody Wed Jun  2 13:40:28 2021
Return-Path: <ned.freed@mrochek.com>
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 AB6DA3A1A48 for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 13:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
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 UbFEjJhntt37 for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 13:40:21 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 193C83A1A42 for <extra@ietf.org>; Wed,  2 Jun 2021 13:40:21 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RZRJ4PRZ5S00IGHV@mauve.mrochek.com> for extra@ietf.org; Wed, 2 Jun 2021 13:35:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1622666117; bh=RfB8vc85lPlqtUSgO0FLjCBQ4B57ys+Z0yVZxhbNhg8=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=cMOrLlD7fOvxBcHLFw3vYna3WfUeJP7SKDp05TZXYz5J8Jew8dhO3XD1WQtqVc93j jd2YtKtjTZzx8FkASYjP9X1/jx/XkZCXgqWke5DPbshDtgNt5a8yIuiczN7cyaS+8l eMhDrstutXH5jdrgE2Jdk8mlIYAblk4Cenkd8kts=
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=utf-8; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RZMX49RI1S0085YQ@mauve.mrochek.com>; Wed, 2 Jun 2021 13:35:08 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, Stephan Bosch <stephan.bosch=40open-xchange.com@dmarc.ietf.org>, extra <extra@ietf.org>
Message-id: <01RZRJ4GMIBI0085YQ@mauve.mrochek.com>
Date: Wed, 02 Jun 2021 12:41:43 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 02 Jun 2021 21:28:31 +0200" <848b0844-4bb3-20d5-f712-0be27a292469@open-xchange.com>
References: <162197041125.31097.10318601097144383125@ietfa.amsl.com> <cfa2fc35-a68d-16fc-c05f-8fbae2cf07e4@open-xchange.com> <01RZHH2IBJQ80085YQ@mauve.mrochek.com> <848b0844-4bb3-20d5-f712-0be27a292469@open-xchange.com>
To: Stephan Bosch <stephan.bosch=40open-xchange.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/e4i_4nFKhjMKjeYtXU0hRltJJhE>
Subject: Re: [Extra] New Version Notification for draft-bosch-sieve-eai-01.txt
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, 02 Jun 2021 20:40:26 -0000

> > The ineluctable conclusion here is that an email system that supports both EAI
> > and Sieve in a compliant way MUST support EAI in Sieve. This is a compliance
> > matter, plain and simple, and cannot be handled as an extension. So the first
> > task of this document needs to be to define what this form of compliance means.
> > It definitely includes saying that the header and address tests must allow for
> > unencoded UTF-8, proper handling of message/global, and probably a bunch of
> > other stuff.

> Yes, that is all true and I agree. But wouldn't it also be necessary to
> know whether the script author is expecting message/global messages?

I don't see why. Sieve interpreters by default decode encoded words and
translate them to UTF-8, which effectively changes the message format from
message/rfc822 to message/global. The one place where UTF-8 can occur that it
couldn't previously is in addresses and domains, but since you can already
compare UTF-8 strings to addresses and domain in Sieve (they won't match but
won't produce an error), and variables can contain UTF-8 values, I'm not seeing
a reason why there's any need for an extension to announce this.

And perhaps more to the point, what's an interpreter supposed to do with an EAI
message when the script says it can't handle it? Downgrade? We've tried twice to
define a viable downgrade format, and I can pretty much guarantee that use of
either one is a cure that's much worse than the disease. I for one would not
even consider implementing such a thing.

> The
> eai extension would indicate that the script was written with the
> possibility of receiving message/global in mind.

And therein lies the problem. Given the way Sieve is defined the overwhelming 
majority of scripts will work fine with EAI messages. (Weren't we clever?) Your
proposal, taken to the logical conclusion, will penalize all of those scripts
for the sake of a few edge cases.

> I haven't read the
> relevant RFCs in a while (and not going to right now), but what is
> supposed to happen when the server has EAI support but the mail
> retrieval agent (IMAP client) does not?

You either deny access or downgrade, although in practice I suspect "just send
EAI" happens a lot.

> I remember something about
> downgrade or placeholder messages. Most solutions I'd imagine would be
> far from ideal.

Yes they are.

> The most crude solution could be to make the recipient
> server reject message/global outright when it somehow knows the
> destination user doesn't have the software installed to read the
> messages. Our software doesn't do much of the EAI stuff yet, so I can't
> say I have implementation/deployment experience. My point is: forcing
> Sieve scripts to handle EAI messages when they were not written with
> such messages in mind could pose problems. What to do? I don't know...

Well, I *can* speak from experience. Making an MTA EAI-aware in a way that
actually provides a somewhat satisfactory experience is a real PITA, because you
have to figure out *why* the message was marked as EAI in order to hanle it
optimally.

IMAP is also difficult because of the downgrade issue.

In contrast, converting our core Sieve interpreter to support EAI was easy. It's
entirely a matter of how you handle previously illegal 8bit in a few contexts. 
You probably already have code for that - and if you don't and are passing 8bit
through unchanged it will mostly work - so that's where the changes go.

> Also, the ManageSieve client would need to know somehow that EAI is
> supported by the server. It could connect to IMAP first and find out,
> but I think that is not the way to handle this. Of course this could be
> a ManageSieve capability then and not a Sieve extension.

Again, I don't see why. If there's no EAI extension there's nothing
to detect. An smtputf8 extension is another matter, of course.

> > But now things get even stickier: A-labels. EAI extends the message
> > format to
> > allow, among other things, U-Labels in domains, but AFAIK doesn't
> > explicitly say
> > that A-Labels cannot be used. (Except in the case of domains in trace
> > fields,
> > and as a recent discussion has shown, it appears this requirement is being
> > widely ignored.)
> >
> > Domains appear in a lot more header fields than addresses, and it would be
> > asking a lot of a Sieve implementation to know how to parse them all and
> > convert
> > A-labels to U-labels. FWIW, I think the right answer is to only perform the
> > conversion in the address test, but I could be persuaded  otherwise.

> I'd say all Sieve bits that compare addresses (address test, vacation
> :addresses etc.) or domains should normalize them in several ways,
> including the A-label/U-label format.

Much as I wish it were otherwise, there's no defined normalization for
local-parts, so applying a default normalization may actually produce bogus
results. The good news is Sieve supports comparators, and comparators can
specify normalization, including on the address test. Not ideal, but given how
EAI is defined, I don't know what else could be done.

				Ned


From nobody Wed Jun  2 16:59:47 2021
Return-Path: <brong@fastmailteam.com>
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 5A6533A20D9 for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 16:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=NsI7WNl7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=eu8i8Obi
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 IRkWnKmNTSDZ for <extra@ietfa.amsl.com>; Wed,  2 Jun 2021 16:59:40 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18DE03A20D4 for <extra@ietf.org>; Wed,  2 Jun 2021 16:59:39 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 02A9F5C00DE for <extra@ietf.org>; Wed,  2 Jun 2021 19:59:37 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute6.internal (MEProxy); Wed, 02 Jun 2021 19:59:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=ORHa917 Tp9MYB1ppAHWm/myUoaSYMb0vNDVDoTnGA1Q=; b=NsI7WNl7kw9CSUorrwA6ESn zRSbhcem7CBWFcg/65kX5VS8ldJUv4DD69667lgru5o4VsMSrtvZzvQbWRCAy7hx DeiB8+ruCpHpS2iQlrQspeUTEzD9oo4ghmtPXuMIZgivXDHs6uNvSRKO6JrZHqP4 +D4OK2O1V3PU5U/J/XHMiTK8oJuRIbDfCRW09dfDS2o91VY2ygt3LaU5/H3j3kwb kSfJF8qNnkaPVb/Fskf44TLQFrVtBKa/ixleur72EDLODOG4GFOk5b7fb5t0ied9 cUqQ2AXw3+t2MLb9gqQhYZL4DA2HEpA0X2Rrm/rspNb9cqRnbsNIpJRPOjhaF/A= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ORHa91 7Tp9MYB1ppAHWm/myUoaSYMb0vNDVDoTnGA1Q=; b=eu8i8Obi/Howh2CQsYNh6Q MRtU1lU/dzfPOVfvcBHs9ueUppybgaIMa/Na9FZxuP9NFZl5uvjBzuJ8laVwLIID fAuTJUn8XrR67/7UuX+hIEWqIrHzULIKWPsl6V2ewJheUagpKZzs8jrT8q6PC097 vLzHyRr8NANojXyeMR2cl5OHEyY7QkYeRbC8gnq8kSk3f/q/HNPFvEkNdCQrluhZ 2edLf1REEKnQjwLPAauIiMHZiHFu4unZyFn0GTi0iBGZ2DfuSlj0jw+DsYkPNXYH mc1pluq0F4vcpF+0ff5agMoILEfgm5nt/SMUb1Zt/CbEQZecYaJJRUkfnBRnMF9Q ==
X-ME-Sender: <xms:aBu4YGiH2GTJojANvw8JtQLdeepj_fxX1KAiQT8bDWN8WQe_fUH9dQ> <xme:aBu4YHAzr8UGzFzFCdfKf1FJVCHB7w592PdDaDyljRgDKhYgoIWDHflouyrlCBmB1 5sRqAAOr2A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdelkedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpedvudeuieehgf dvheeuueejjeeuudfgiefgveetfeelteeffffgtdejjefgueduvdenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrg hilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:aBu4YOHebxZErwqwipYle1MYOGz5ixiXWAW2PMWHUChqOeP2krG7Lw> <xmx:aBu4YPR3L-ol_a0jmusJZo41oNwPz1P6eF9_KZCfbgzWWwN2zzhDng> <xmx:aBu4YDwPL8X7BLHCdG_VdWu_1zZ6RjIaCJauQWVZqX2YYj8YLRb3Zg> <xmx:aBu4YC93WzIK_7r5tfecH3p4ZhWqC6Ulr8ltM_hUCWKmBzKMwORpJQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 58F24AC0061; Wed,  2 Jun 2021 19:59:36 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-701-g78bd539edf-fm-ubox-20210517.001-g78bd539e
Mime-Version: 1.0
Message-Id: <ca9e0a5f-b992-433c-bea7-61f8ee5f807b@dogfood.fastmail.com>
In-Reply-To: <205b16ff-f199-c37c-77c5-0b9a61339e06@open-xchange.com>
References: <162197041125.31097.10318601097144383125@ietfa.amsl.com> <cfa2fc35-a68d-16fc-c05f-8fbae2cf07e4@open-xchange.com> <b4e89d86-1276-47f3-80ec-fa21e2fbee35@dogfood.fastmail.com> <205b16ff-f199-c37c-77c5-0b9a61339e06@open-xchange.com>
Date: Thu, 03 Jun 2021 09:59:14 +1000
From: "Bron Gondwana" <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary=05926ab689524c0b8d5b3095e7a8d97e
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/mITPw3XnSWaapcxLcmX1jHvaMEc>
Subject: Re: [Extra] New Version Notification for draft-bosch-sieve-eai-01.txt
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, 02 Jun 2021 23:59:46 -0000

--05926ab689524c0b8d5b3095e7a8d97e
Content-Type: text/plain

On Thu, Jun 3, 2021, at 05:00, Stephan Bosch wrote:
> 
> 
> On 26/05/2021 14:53, Bron Gondwana wrote:
> > Awesome.  Are you planning to progress this document further?  I was 
> > about to email the list to see if there's interest in meeting at 
> > IETF111, and that probably depends if we have any work to do :)
> 
> Well, yes, although I am not sure I have time to make progress on this 
> very quickly. The aftermath of Corona infection of a months ago 
> definitely is not helping. And I am not a great fan of the idea of a 
> whole WG waiting for me to finish this. :)

Oh, we're going to stay open regardless - there will be other documents in future - it's more "is it worth meeting at IETF111" which depends if we have any work to do this cycle.  It sounds like the answer is no.

Cheers,

Bron.

P.S. sorry to hear about the Corona - I hope you recover OK.  I hear that it can have ongoing issues.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--05926ab689524c0b8d5b3095e7a8d97e
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">On Thu, Jun 3, 2021, at 05:00, Stephan Bosch wrote:<br></d=
iv><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-fam=
ily:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><div s=
tyle=3D"font-family:Arial;">On 26/05/2021 14:53, Bron Gondwana wrote:<br=
></div><div style=3D"font-family:Arial;">&gt; Awesome.&nbsp; Are you pla=
nning to progress this document further?&nbsp; I was&nbsp;<br></div><div=
 style=3D"font-family:Arial;">&gt; about to email the list to see if the=
re's interest in meeting at&nbsp;<br></div><div style=3D"font-family:Ari=
al;">&gt; IETF111, and that probably depends if we have any work to do :=
)<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fon=
t-family:Arial;">Well, yes, although I am not sure I have time to make p=
rogress on this&nbsp;<br></div><div style=3D"font-family:Arial;">very qu=
ickly. The aftermath of Corona infection of a months ago&nbsp;<br></div>=
<div style=3D"font-family:Arial;">definitely is not helping. And I am no=
t a great fan of the idea of a&nbsp;<br></div><div style=3D"font-family:=
Arial;">whole WG waiting for me to finish this. :)<br></div></blockquote=
><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:A=
rial;">Oh, we're going to stay open regardless - there will be other doc=
uments in future - it's more "is it worth meeting at IETF111" which depe=
nds if we have any work to do this cycle.&nbsp; It sounds like the answe=
r is no.<br></div><div style=3D"font-family:Arial;"><br></div><div style=
=3D"font-family:Arial;">Cheers,<br></div><div style=3D"font-family:Arial=
;"><br></div><div style=3D"font-family:Arial;">Bron.<br></div><div style=
=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">P.S.=
 sorry to hear about the Corona - I hope you recover OK.&nbsp; I hear th=
at it can have ongoing issues.<br></div><div style=3D"font-family:Arial;=
"><br></div><div id=3D"sig56629417"><div class=3D"signature">--<br></div=
><div class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br=
></div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br></div><=
div class=3D"signature"><br></div></div><div style=3D"font-family:Arial;=
"><br></div></body></html>
--05926ab689524c0b8d5b3095e7a8d97e--


From nobody Wed Jun 30 19:34:20 2021
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 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/6Oo6_AQSzFkeCH0Q3kc6SFn6s7A>
Subject: [Extra] =?utf-8?q?RFC_9042_on_Sieve_Email_Filtering=3A_Delivery_?= =?utf-8?q?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


