From nobody Mon Dec 3 13:31:41 2018 Return-Path: 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 523E912E036 for ; Mon, 3 Dec 2018 13:31:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 asyN1VLNblQ6 for ; Mon, 3 Dec 2018 13:31:38 -0800 (PST) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id EC0BB12D4ED for ; Mon, 3 Dec 2018 13:31:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1543872697; d=isode.com; s=june2016; i=@isode.com; bh=z3vWAw7KVJgQAJv7kOUs7vDi9Q4LCkQ7BAnReIENe+U=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=vrfrcCWXbHAWo1KwjT05p/Sdjt8b5e4zBvJ9ClDnz6r9HezZyX01KEoh4YAs8q7OCAY0E4 GmgANKs4OAZcg+7uVTaTNlnqRBNPISXC6Q0HeL1XhLhmx3TzzD0aQqk93zTIHaBzlAkgJe TXkvjJjxWvhlfp/yCvJ/gYBWzJhCsSM=; Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Mon, 3 Dec 2018 21:31:37 +0000 To: Ken Murchison , extra References: <2a2f0f33-b056-1a04-aa11-8b8d0a448a4c@isode.com> From: Alexey Melnikov Message-ID: Date: Mon, 3 Dec 2018 21:31:00 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [Extra] AD review of draft-ietf-extra-sieve-fcc-06.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2018 21:31:39 -0000 Hi Ken, So in -07, I now see: 3.1.1.=C2=A0 Imap4flags Extension =C2=A0=C2=A0 Usage: :fcc [:flags ] 3.1.2.=C2=A0 Mailbox Extension =C2=A0=C2=A0 Usage: :fcc [:create] 3.1.3.=C2=A0 Special-Use Extension =C2=A0 Usage: :fcc [:specialuse ] Is your intention that :fcc always goes first? If not, you might want to=20 clarify that. 3.2.=C2=A0 Collected Grammar =C2=A0=C2=A0 For convenience, the "FCC" syntax element is defined here usin= g ABNF =C2=A0=C2=A0 [RFC5234] so that it can be augmented by other extensions. =C2=A0=C2=A0 FCC=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D ":fcc"= string *FCC-OPTS I am somewhat uncomfortable with the above, as it omits all whitespace=20 delimiters between tokens. If you are going to keep this, you should add=20 a comment explaining that this is done once lexical analyzer extracted=20 different non-space elements. Best Regards, Alexey From nobody Mon Dec 3 15:15:36 2018 Return-Path: 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 D953D130F82 for ; Mon, 3 Dec 2018 15:15:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=crCzbbxY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PkNBQOMR 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 33TWksVPSmBk for ; Mon, 3 Dec 2018 15:15:26 -0800 (PST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7E1130E6B for ; Mon, 3 Dec 2018 15:15:23 -0800 (PST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 472F22206F; Mon, 3 Dec 2018 18:15:22 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 03 Dec 2018 18:15:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm1; bh=bVdHQs0lBVR9mp11s13SiNJBfvC 0JQlNXUoICqA/23c=; b=crCzbbxY5q96l1+akq68+dLM0BL7Y0T6YOK3KW0aVs2 iy1mmm8T+hOGn1ibeqjsJWDznZX7qCcV13+gYCmNcdvN2tF7iaaL6PPXhQ0DV5eo /fltHPS24mpI2WBj95wUyPt2DN0IgFMQ+eW6W6Gil8bhY52lR2AbhQV+zsYA2UXW ny5J2f18xj6QuxQkNlOQEDk97jEapRWdfkBYCBqZWRsd2VBSPgBrLa/Vn0wkJxPi 2VOPgqRSA8U/qhCgtZ3IbEiuDFfs6l+cD8iVQgH0c8OzLOUd+z2wo4iHKSyVmnk3 vQNB/6RQVvgOEbwvtjCuMsMcozz90weJMoh+j4dHwXg== 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=fm1; bh=bVdHQs 0lBVR9mp11s13SiNJBfvC0JQlNXUoICqA/23c=; b=PkNBQOMRpR+7GT9uX4ERSf qrxTG/h+A4PnWkM2W5BYoyrc4ueeT5bpaN/SuUrxdkMrjE7QPwKdnPL/46cDP5I2 BjEWc7HNrz8qvZjqyH7npchoQW8FslruhkEMpclnayQ4FNXhbqzKDKoOC7Efrin6 aF/NayxAS4bhMJzLm5xjoUxt+yH5qTtnu8zQGOn57J+i2UwU0ja2ND39CSG4tUnh oxDMA38gLkwHTLLtSTdv1IO+1hL73VwR+VaiDf1sbFzbP/Dkai3zcF8AvC/ToJO2 FS5VI5DaVlU4QoLSmrM+tNBiHO+zi/5DTUC4h5zA7dGsdhZBqx8Gi0oBH8VwONOQ == X-ME-Sender: X-ME-Proxy: Received: from localhost.localdomain (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 69B9FE443C; Mon, 3 Dec 2018 18:15:21 -0500 (EST) To: Alexey Melnikov , extra References: <2a2f0f33-b056-1a04-aa11-8b8d0a448a4c@isode.com> From: Ken Murchison Organization: FastMail US LLC Message-ID: Date: Mon, 3 Dec 2018 18:15:20 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------A071ADFEC705DD7BC38FFEAA" Content-Language: en-US Archived-At: Subject: Re: [Extra] AD review of draft-ietf-extra-sieve-fcc-06.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2018 23:15:33 -0000 This is a multi-part message in MIME format. --------------A071ADFEC705DD7BC38FFEAA Content-Type: multipart/alternative; boundary="------------FF83D3C0483FFF8201A88F72" --------------FF83D3C0483FFF8201A88F72 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 12/3/18 4:31 PM, Alexey Melnikov wrote: > Hi Ken, > > So in -07, I now see: > > 3.1.1.  Imap4flags Extension > >    Usage: :fcc [:flags ] > > 3.1.2.  Mailbox Extension > >    Usage: :fcc [:create] > > > 3.1.3.  Special-Use Extension > >   Usage: :fcc [:specialuse ] > > > Is your intention that :fcc always goes first? No. > If not, you might want to clarify that. Ad will add text to that effect. > 3.2.  Collected Grammar > >    For convenience, the "FCC" syntax element is defined here using ABNF >    [RFC5234] so that it can be augmented by other extensions. > >    FCC         = ":fcc" string *FCC-OPTS > > I am somewhat uncomfortable with the above, as it omits all whitespace > delimiters between tokens. If you are going to keep this, you should > add a comment explaining that this is done once lexical analyzer > extracted different non-space elements. How about: FCC = ":fcc" string *(white-space FCC-OPTS) Or would you prefer that I use text similar to what is in Section 8.2 of RFC5228: "The following is the grammar of Sieve after it has been lexically interpreted. No whitespace or comments appear below." -- Ken Murchison Cyrus Development Team FastMail US LLC --------------FF83D3C0483FFF8201A88F72 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit


On 12/3/18 4:31 PM, Alexey Melnikov wrote:
Hi Ken,

So in -07, I now see:

3.1.1.  Imap4flags Extension

   Usage: :fcc <mailbox: string> [:flags <list-of-flags: string-list>]

3.1.2.  Mailbox Extension

   Usage: :fcc <mailbox: string> [:create]


3.1.3.  Special-Use Extension

  Usage: :fcc <mailbox: string> [:specialuse <special-use-flag: string>]


Is your intention that :fcc always goes first?


No.



If not, you might want to clarify that.


Ad will add text to that effect.



3.2.  Collected Grammar

   For convenience, the "FCC" syntax element is defined here using ABNF
   [RFC5234] so that it can be augmented by other extensions.

   FCC         = ":fcc" string *FCC-OPTS

I am somewhat uncomfortable with the above, as it omits all whitespace delimiters between tokens. If you are going to keep this, you should add a comment explaining that this is done once lexical analyzer extracted different non-space elements.


How about:

FCC = ":fcc" string *(white-space FCC-OPTS)


Or would you prefer that I use text similar to what is in Section 8.2 of RFC5228:

"The following is the grammar of Sieve after it has been lexically
   interpreted.  No whitespace or comments appear below."
-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC
--------------FF83D3C0483FFF8201A88F72-- --------------A071ADFEC705DD7BC38FFEAA Content-Type: text/x-vcard; name="murch.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="murch.vcf" bnVsbA== --------------A071ADFEC705DD7BC38FFEAA-- From nobody Tue Dec 4 03:22:15 2018 Return-Path: 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 D9009130EC1 for ; Tue, 4 Dec 2018 03:22:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 IvLvM3AdzInU for ; Tue, 4 Dec 2018 03:22:12 -0800 (PST) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 99D5112875B for ; Tue, 4 Dec 2018 03:22:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1543922531; d=isode.com; s=june2016; i=@isode.com; bh=oreW0jSXFDAfOLxTzqiqXgKv840E6zzlRJKflt5yazA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Ue8HLw7XEFiH1e34kTRVQPgO0Nqmbpuvrm6MoQj0ZnwCOPQPkM3RWVQHjdOgKE+G/uPf5L TPSD1ddUtjvARdW81JyiKo6uGX7OfY/1eHF7eIFI3TbDtYrVUvYiJQcJYMwZH4CYp09F7a 1CfLGfkaKIMNOi1HbxXOBn2hI0XSXw4=; Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Tue, 4 Dec 2018 11:22:11 +0000 To: Ken Murchison , extra References: <2a2f0f33-b056-1a04-aa11-8b8d0a448a4c@isode.com> From: Alexey Melnikov Message-ID: <417269c0-1ca0-9d47-a140-4e4555bba38d@isode.com> Date: Tue, 4 Dec 2018 11:21:34 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------6064C9342A220FA0CB2F7492" Content-Language: en-GB Archived-At: Subject: Re: [Extra] AD review of draft-ietf-extra-sieve-fcc-06.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2018 11:22:14 -0000 --------------6064C9342A220FA0CB2F7492 Content-Type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: quoted-printable On 03/12/2018 23:15, Ken Murchison wrote: > On 12/3/18 4:31 PM, Alexey Melnikov wrote: > >> Hi Ken, >> >> So in -07, I now see: >> >> 3.1.1.=C2=A0 Imap4flags Extension >> >> =C2=A0=C2=A0 Usage: :fcc [:flags ] >> >> 3.1.2.=C2=A0 Mailbox Extension >> >> =C2=A0=C2=A0 Usage: :fcc [:create] >> >> >> 3.1.3.=C2=A0 Special-Use Extension >> >> =C2=A0 Usage: :fcc [:specialuse ] >> >> >> Is your intention that :fcc always goes first?=20 > > No. > >> If not, you might want to clarify that. > > Ad will add text to that effect. > Great. >> 3.2. Collected Grammar >> >> =C2=A0=C2=A0 For convenience, the "FCC" syntax element is defined here us= ing ABNF >> =C2=A0=C2=A0 [RFC5234] so that it can be augmented by other extensions. >> >> =C2=A0=C2=A0 FCC=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D ":fc= c" string *FCC-OPTS >> >> I am somewhat uncomfortable with the above, as it omits all=20 >> whitespace delimiters between tokens. If you are going to keep this,=20 >> you should add a comment explaining that this is done once lexical=20 >> analyzer extracted different non-space elements. > > > How about: > > FCC =3D ":fcc" string *(white-space FCC-OPTS) > You also need white-space after ":fcc". And in 2 other productions in=20 the same section. > > Or would you prefer that I use text similar to what is in Section 8.2=20 > of RFC5228: > > "The following is the grammar of Sieve after it has been lexically > interpreted. No whitespace or comments appear below." I think this would be the easiest way to address my concern. Thank you, Alexey --------------6064C9342A220FA0CB2F7492 Content-Type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable

On 03/12/2018 23:15, Ken Murchison wrote:

On 12/3/18 4:31 PM, Alexey Melnikov wrote:

Hi Ken,

So in -07, I now see:

3.1.1.=C2=A0 Imap4flags Extension

=C2=A0=C2=A0 Usage: :fcc <mailbox: string> [:flags <list-of-flags: string-list>]

3.1.2.=C2=A0 Mailbox Extension

=C2=A0=C2=A0 Usage: :fcc <mailbox: string> [:create]


3.1.3.=C2=A0 Special-Use Extension

=C2=A0 Usage: :fcc <mailbox: string> [:specialuse <special-use-flag: string>]


Is your intention that :fcc always goes first?

No.

If not, you might want to clarify that.

Ad will add text to that effect.


Great.

3.2.=C2= =A0 Collected Grammar

=C2=A0=C2=A0 For convenience, the "FCC" syntax element is defined he= re using ABNF
=C2=A0=C2=A0 [RFC5234] so that it can be augmented by other extensio= ns.

=C2=A0=C2=A0 FCC=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D= ":fcc" string *FCC-OPTS

I am somewhat uncomfortable with the above, as it omits all whitespace delimiters between tokens. If you are going to keep this, you should add a comment explaining that this is done once lexical analyzer extracted different non-space elements.


How about:

FCC =3D ":fcc" string *(white-space FCC-OPTS)

You also need white-space after ":fcc". And in 2 other productions in the same section.

Or would you prefer that I use text similar to what is in Section 8.2 of RFC5228: 

"The following is the grammar of Sieve after it=
 has been lexically
   interpreted.  No whitespace or comments appear below."

I think this would be the easiest way to address my concern.

Thank you,

Alexey

--------------6064C9342A220FA0CB2F7492-- From nobody Tue Dec 4 08:25:39 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A28A8130ED9; Tue, 4 Dec 2018 08:25:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: extra@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: extra@ietf.org Message-ID: <154394073762.4587.2744695329640946412@ietfa.amsl.com> Date: Tue, 04 Dec 2018 08:25:37 -0800 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-sieve-fcc-08.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2018 16:25:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF. Title : Sieve Extension: File Carbon Copy (Fcc) Authors : Kenneth Murchison Bron Gondwana Filename : draft-ietf-extra-sieve-fcc-08.txt Pages : 14 Date : 2018-12-04 Abstract: The Sieve Email Filtering Language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox. This document updates RFC5230 and RFC5435 by adding a new tagged argument to the "vacation" and "enotify" actions respectively. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-fcc/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-sieve-fcc-08 https://datatracker.ietf.org/doc/html/draft-ietf-extra-sieve-fcc-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-fcc-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Dec 4 08:40:10 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7AE130F8E; Tue, 4 Dec 2018 08:39:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk CC: draft-ietf-extra-sieve-fcc@ietf.org, Jiankang Yao , extra@ietf.org, yaojk@cnnic.cn, extra-chairs@ietf.org, alexey.melnikov@isode.com Reply-To: ietf@ietf.org Sender: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Reply-To: ietf@ietf.org Message-ID: <154394159957.4632.13177911779941747228.idtracker@ietfa.amsl.com> Date: Tue, 04 Dec 2018 08:39:59 -0800 Archived-At: Subject: [Extra] Last Call: (Sieve Extension: File Carbon Copy (Fcc)) to Proposed Standard X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2018 16:40:09 -0000 The IESG has received a request from the Email mailstore and eXtensions To Revise or Amend WG (extra) to consider the following document: - 'Sieve Extension: File Carbon Copy (Fcc)' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2018-12-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Sieve Email Filtering Language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox. This document updates RFC5230 and RFC5435 by adding a new tagged argument to the "vacation" and "enotify" actions respectively. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-fcc/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-fcc/ballot/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: draft-ietf-extra-sieve-special-use: Sieve Email Filtering: Delivering to Special-Use Mailboxes (None - IETF stream) From nobody Tue Dec 4 20:24:12 2018 Return-Path: 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 CEAB4130DCF for ; Tue, 4 Dec 2018 20:24:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.983 X-Spam-Level: X-Spam-Status: No, score=-1.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=xo1eSHkz; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cuhqqu7W 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 LJNxDd4KNrq1 for ; Tue, 4 Dec 2018 20:24:08 -0800 (PST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63960129533 for ; Tue, 4 Dec 2018 20:24:08 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6EF0F21ADA for ; Tue, 4 Dec 2018 23:24:07 -0500 (EST) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Tue, 04 Dec 2018 23:24:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:date:from:to:subject :content-type; s=fm1; bh=rMpyghEcc3p2IK6a1/OHfkMA2prXtph7OhSvbTY lbAM=; b=xo1eSHkzEwc1I9fYJn0WMDrSW/qc2x4TpxRGuP+YC30w52JBNF/V1xc Gj/qI7wCBnVEBLANXCvkPliOxG8bFWwu0Dwokal3SOKurRm9QGZvijIV+XdG5VOy 98uLTxUlDjQ9HojIxgooaJh5QK4pbJ75gdveZcqhUlqbWslbF+Sx4Kfb4YepamHe 4lCS251n9Ny8SKGxerTWoAPRyByDp+n5M24+H0y+q8aHr271x4u99buhaIW0EU1Z UAa9M+kTB7GwX62+D6u5zRzAz06nVR3/s21Uk+wJ+4G5cxtoL91LGIAf9o58BKqV IT59z4AKMcA9pG1rwA56VqWCC2lEwDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id:subject :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=rMpyghEcc3p2IK6a1/OHfkMA2prXtph7OhSvbTYlbAM=; b=cuhqqu7W 5zgx/ubqGCugAe/kIvNZcPg6sbgjKZT5kDouLE0ujBvc8eoeNDguTd5rAKVJ6nAy Zrn6dPRNFvrn7XSW13kG4zPiputDOTB+GpNB+7qeaaM6XQSqO8YQ2r63ARg0cVbJ Nn+hZEPxjkRtDECTp5FhE09Yjl5QL9EqQc7M1ls7c4FbZdPPPSdWyUpv09Qv1Wdb rxYfitYrOVN6BLBJpou6FV0lv5MI59erlUOVrMmY3FhtI1zS/LpvTkMnMAzF/SX5 gx/OaqacozDUqVRLEDqcMKwlos39RYTXDHY73BHTk72BVs1xC6vcLu/nU7hmVgmF 6dg8AosTrY1xIg== X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id DA6952030C; Tue, 4 Dec 2018 23:24:06 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface Message-Id: User-Agent: Cyrus-JMAP/3.1.5-681-g8713b31-fmstable-20181205v1 X-Me-Personality: 56629417 Date: Tue, 04 Dec 2018 23:24:06 -0500 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=6a4b441cd8b64361b70cf668fe7bfa54 Archived-At: Subject: [Extra] PREVIEW draft in Working Group Last Call X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2018 04:24:10 -0000 --6a4b441cd8b64361b70cf668fe7bfa54 Content-Type: text/plain Hi All, As discussed in Bangkok, preview is basically done. The only outstanding issue I'm aware of is the exact maximum length of the preview. This is the text in the current draft: The server SHOULD limit the length of the preview text to 200 preview characters. This length should provide sufficient data to generally support both various languages (and their different average word lengths) and different client display size requirements. The server MUST NOT output preview text longer than 256 preview characters. And the text in JMAP as submitted for publication is: o *preview*: "String" (immutable; server-set) A plain text fragment of the message body. This is intended to be shown as a preview line on a mailbox listing, and may be truncated when shown. The server may choose which part of the message to include in the preview; skipping quoted sections and salutations and collapsing white-space can result in a more useful preview. This MUST NOT be more than 256 characters in length. These two specifications are congruent, which makes me very happy! I also intent to write a full review of this draft as part of the working group last call, and possibly to implement it! Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --6a4b441cd8b64361b70cf668fe7bfa54 Content-Type: text/html
Hi All,

As discussed in Bangkok, preview is basically done.  The only outstanding issue I'm aware of is the exact maximum length of the preview.  This is the text in the current draft:

   The server SHOULD limit the length of the preview text to 200 preview
   characters.  This length should provide sufficient data to generally
   support both various languages (and their different average word
   lengths) and different client display size requirements.

   The server MUST NOT output preview text longer than 256 preview
   characters.

And the text in JMAP as submitted for publication is:

   o  *preview*: "String" (immutable; server-set) A plain text fragment
      of the message body.  This is intended to be shown as a preview
      line on a mailbox listing, and may be truncated when shown.  The
      server may choose which part of the message to include in the
      preview; skipping quoted sections and salutations and collapsing
      white-space can result in a more useful preview.  This MUST NOT be
      more than 256 characters in length.

These two specifications are congruent, which makes me very happy!

I also intent to write a full review of this draft as part of the working group last call, and possibly to implement it!

Cheers,

Bron.

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


--6a4b441cd8b64361b70cf668fe7bfa54-- From nobody Wed Dec 5 17:43:09 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87BDC130F4C; Wed, 5 Dec 2018 17:43:08 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Jiankang Yao To: X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk Cc: extra@ietf.org, yaojk@cnnic.cn, iesg-secretary@ietf.org, Jiankang Yao , extra-chairs@ietf.org Message-ID: <154406058851.31797.13490612508746987918.idtracker@ietfa.amsl.com> Date: Wed, 05 Dec 2018 17:43:08 -0800 Archived-At: Subject: [Extra] Publication has been requested for draft-ietf-extra-sieve-special-use-04 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Dec 2018 01:43:09 -0000 Jiankang Yao has requested publication of draft-ietf-extra-sieve-special-use-04 as None on behalf of the EXTRA working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-special-use/ From nobody Thu Dec 6 06:11:43 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63571126CB6; Thu, 6 Dec 2018 06:11:41 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk CC: Jiankang Yao , extra@ietf.org, yaojk@cnnic.cn, extra-chairs@ietf.org, draft-ietf-extra-sieve-special-use@ietf.org, alexey.melnikov@isode.com Reply-To: ietf@ietf.org Sender: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Reply-To: ietf@ietf.org Message-ID: <154410550134.3473.655825216991929479.idtracker@ietfa.amsl.com> Date: Thu, 06 Dec 2018 06:11:41 -0800 Archived-At: Subject: [Extra] Last Call: (Sieve Email Filtering: Delivering to Special-Use Mailboxes) to Proposed Standard X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Dec 2018 14:11:42 -0000 The IESG has received a request from the Email mailstore and eXtensions To Revise or Amend WG (extra) to consider the following document: - 'Sieve Email Filtering: Delivering to Special-Use Mailboxes' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2018-12-20. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The SPECIAL-USE capability of the IMAP protocol (RFC 6154) allows clients to identify special-use mailboxes; e.g., where draft or sent messages should be put. This simplifies client configuration. In contrast, the Sieve mail filtering language (RFC 5228) currently has no such capability. This memo defines a Sieve extension that fills this gap: it adds a test for checking whether a special-use attribute is assigned for a particular mailbox or any mailbox, and it adds the ability to file messages into an anonymous mailbox that has a particular special-use attribute assigned. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-special-use/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-special-use/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Mon Dec 17 12:14:56 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FC1126F72; Mon, 17 Dec 2018 12:14:54 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Stephen Farrell To: Cc: extra@ietf.org, draft-ietf-extra-sieve-special-use.all@ietf.org, ietf@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <154507769480.4171.7860732594241016456@ietfa.amsl.com> Date: Mon, 17 Dec 2018 12:14:54 -0800 Archived-At: Subject: [Extra] Secdir last call review of draft-ietf-extra-sieve-special-use-04 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2018 20:14:55 -0000 Reviewer: Stephen Farrell Review result: Ready As stated in the draft I see no new security issues here, given that SIEVE already includes the ability to deliver messages and create mailboxes. A non-security comment, that you should feel free to ignore: as a mail user it is irritating to have multiple folders (that may or may not have a "special-use" attribute associated with 'em) created by multiple MUAs and into which messages can be deposited in a manner that's unpredictable to me as a user . I understand that this spec is already trying to help with that, by reducing the likelihood that such redundant folders get created. But I already have a bunch of those folders, so while this is likely the wrong place for such text, I'd have been happier if the guidance for what to do when there's >1 matching special-use mailbox had been more deterministic, even when the SIEVE-supplied default one doesn't exist. For example, if you'd been able to say to sort the matching folders in some way and then pick the first that'd be better I think, but maybe there are reasons why you can't do that in SIEVE. (I'd be even happier if someone was working on specs/tooling to help merge all those folders somehow, but that's definitely out of scope here.) From nobody Mon Dec 17 14:12:59 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24A3D12958B; Mon, 17 Dec 2018 14:12:45 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Ines Robles To: Cc: extra@ietf.org, ietf@ietf.org, draft-ietf-extra-sieve-fcc.all@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.89.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <154508476504.4235.1662228852126189639@ietfa.amsl.com> Date: Mon, 17 Dec 2018 14:12:45 -0800 Archived-At: Subject: [Extra] Genart last call review of draft-ietf-extra-sieve-fcc-08 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2018 22:12:46 -0000 Reviewer: Ines Robles Review result: Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at . Document: draft-ietf-extra-sieve-fcc-08 Reviewer: Ines Robles Review Date: 2018-12-17 IETF LC End Date: 2018-12-18 IESG Telechat date: Not scheduled for a telechat Summary: I believe the draft is technically good. This document is well written and clear to understand. This document defines an extension to Sieve Email Filtering Language commands to allow a copy of any generated message to be filed into a target mailbox. This document updates RFC5230 and RFC5435 by adding a new tagged argument to the "vacation" and "enotify" actions respectively. Major issues: Not found. Minor issues: Not found. Nits/editorial comments: Page 3. "how it interfacts with :fcc." => how it interacts with :fcc.? Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Thanks for this document, Ines. From nobody Wed Dec 19 22:14:46 2018 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC75B130E16; Wed, 19 Dec 2018 22:14:43 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Shwetha Bhandari To: Cc: extra@ietf.org, draft-ietf-extra-sieve-special-use.all@ietf.org, ietf@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.89.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <154528648390.1826.9611677888436906800@ietfa.amsl.com> Date: Wed, 19 Dec 2018 22:14:43 -0800 Archived-At: Subject: [Extra] Opsdir last call review of draft-ietf-extra-sieve-special-use-04 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 06:14:44 -0000 Reviewer: Shwetha Bhandari Review result: Ready I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Summary: This document extends the SIEVE mail filtering language (RFC 5228) with capability similar to SPECIAL-USE capability of the IMAP protocol. This extension to SIEVE does not have any new issues related to operations and manageability.