From nobody Fri Mar 2 09: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 7F71812DA45 for ; Fri, 2 Mar 2018 09:24:10 -0800 (PST) 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, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=gmail.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 BaexMWfKi26F for ; Fri, 2 Mar 2018 09:24:09 -0800 (PST) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D23E12DA49 for ; Fri, 2 Mar 2018 09:24:09 -0800 (PST) Received: by mail-qk0-x236.google.com with SMTP id b130so12801822qkg.9 for ; Fri, 02 Mar 2018 09:24:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=PPpGEyjF2JsMpdgqGE/R3gABZdNPENv8zqtzx91Tsso=; b=hXnSevtjEEFGcJA3A5Zrdv5ernUbcMmneI0picSXwqZUhWWqsRcoH76D8/iFGWRscO Oxd9cxEAdnGPFSxvGBUZCkygVuno/Vh2MjheJzJQGchrta62J2BxcJk+CE7C3EMyEQeF e4/9g9mVX6fmbI9LvkYEaI437lfmiiOC5FrkO8C9I3OSaqInLDPBAhrW5cU3vY1zr0mb iFAAXhWsDqunPnG0EB2K0CxWq3efHVKQsfA3QwyjJTlPBdOlzhK1XCzEv1fYW5vAX9y9 G7R+9EFQguO6cGSrxqk5mC8SRGNQgArtG90w63dRULb9gpEDHtGhci7Alz+Q9TYb6lsT 3bUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=PPpGEyjF2JsMpdgqGE/R3gABZdNPENv8zqtzx91Tsso=; b=M3gejzAXkco2Iq6YYw8VhUP2efXCUpg6JfX1QpcFgV97RHw7uGaK2boaJTW/GW+zyW BnMrBUeLL1vUKjzFOSnPhjg9b1c8yXxlfqtoN4bC9ltm+pl1zaVIQXeVk3mT47/xJP4D vyMHvJ+wOUUM/fy4Y9+Irm8Pjlye4Cgb2HjpWENz9l73N7/Z/W4eO37kNtbHm6S0ZBHF oMDIcj9Pmw3E5lRnvFyuHAvA9eKiKwehrusExbornsnSuZQjDqtutx3Uks9x083zpAcJ EFG0lqlTnlrttr/oBbQKq6fvudc5VX76Q//fiR5PVg/6GxL+ngOynlA7pl+6dEjxe4Lw 35Kg== X-Gm-Message-State: AElRT7FF9/vH/ttt1zH2ZfPkxb4id66U/RACYeGDV2oR63ZFV/9yIear b58PRica9C3Lz/zU7NVgjblmOkDkzXjNGXAT5vk= X-Google-Smtp-Source: AG47ELv4anFuoY5qNcuHBbi7zKmt3AC9ThRyQI6Fdx7jILO26xyXa+OVoIpi1/FoRyZj38zRdycy+Y/Bs/kHZD/rEgQ= X-Received: by 10.55.123.197 with SMTP id w188mr9521012qkc.70.1520011448247; Fri, 02 Mar 2018 09:24:08 -0800 (PST) MIME-Version: 1.0 Sender: barryleiba.mailing.lists@gmail.com Received: by 10.200.54.215 with HTTP; Fri, 2 Mar 2018 09:24:07 -0800 (PST) In-Reply-To: <282DF82F-92FF-4EEC-B1CF-54EE475AB898@glyphein.mailforce.net> References: <20171115160621.GC17058@meili> <1510799355.3640467.1174131992.15AF5270@webmail.messagingengine.com> <1e08751e-eb51-7fc6-eb39-214eca7f48af@isode.com> <282DF82F-92FF-4EEC-B1CF-54EE475AB898@glyphein.mailforce.net> From: Barry Leiba Date: Fri, 2 Mar 2018 12:24:07 -0500 X-Google-Sender-Auth: 1aSFuOtvS3AKkKuWLQKGFqcft7M Message-ID: To: Stan Kalisch Cc: extra@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Extra] "IMAP $Important Keyword and \Important Special-Use Attribute" X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 02 Mar 2018 17:24:11 -0000 > I've only been able to take a quick look at this document, but in line 113, the > phrase "specific meaning of general" strikes me as a bit awkward. Yes, it strikes me that way too; thanks for pointing it out, Stan. I've simply removed the word "specific" in my working copy for the next update. Barry From nobody Sun Mar 4 09:26:58 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 12A94124B18; Sun, 4 Mar 2018 09:26:51 -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.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152018441102.11996.16139669468419652701@ietfa.amsl.com> Date: Sun, 04 Mar 2018 09:26:51 -0800 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-64bit-03.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 17:26:51 -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 : 64bit body part and message sizes in IMAP4 Authors : Alexey Melnikov Jayantheesh S B Filename : draft-ietf-extra-imap-64bit-03.txt Pages : 7 Date : 2018-03-04 Abstract: This document defines an IMAPv4rev1 extension that extends the existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit. Both the base IMAP specification (RFC 3501) and several extensions are updated. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-64bit/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-64bit-03 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-64bit-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap-64bit-03 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 Sun Mar 4 11:31:20 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 91D04124B17 for ; Sun, 4 Mar 2018 11:31:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 QLT5NwV3eSXP for ; Sun, 4 Mar 2018 11:31:17 -0800 (PST) Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id BED541242F7 for ; Sun, 4 Mar 2018 11:31:16 -0800 (PST) Received: from [10.168.3.2] (klara.student.utwente.nl [130.89.162.218]) by mail.dovecot.fi (Postfix) with ESMTPSA id 6E4082B3CD6; Sun, 4 Mar 2018 21:31:14 +0200 (EET) To: Ned Freed Cc: extra@ietf.org References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <01QNLYA7BLVQ000051@mauve.mrochek.com> <01QNNBB3GEW0000051@mauve.mrochek.com> From: Stephan Bosch Message-ID: Date: Sun, 4 Mar 2018 20:31:12 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <01QNNBB3GEW0000051@mauve.mrochek.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sun, 04 Mar 2018 19:31:18 -0000 Hi Ned, Op 1/9/2018 om 10:44 PM schreef Ned Freed: > >>> Section 3 says: >>> >>> If the "mailbox" string argument is omitted, the "specialuse_exists" >>> test yields true if all of the following statements are true for each >>> of the special-use flags listed in the "special-use-flags" argument: >>> >>> a. at least one mailbox exists in the mail store that has that >>> particular special-use flag assigned, and >>> >>> b. that mailbox allows the user in whose context the Sieve script >>> runs to "deliver" messages into it. >>> >>> I'm concerned about a. - the phrase "the mail store" conjures up an image >>> of searching through folders belonging to millions of users looking for >>> one that has an ACL allowing the sieve owner to write to it. >>> >>> I'm pretty sure you don't intend this to cover shared folders, so I suggest >>> changing the text to say something like: >>> >>> a. at least one mailbox exists in the user's personal namespace >>> [NAMESPACE] that has that particular special-use flag assigned, and >>> >>> And add the [NAMESPACE] reference pointing at RFC 2342. >> I must say I didn't consider any special problems with shared mailboxes. >> The scenario you describe is that lots of people are sharing some of >> their mailboxes with pretty much everyone. > It's not a question of lots of people doing it, it's a question of whether or > not you have an optimized way of looking through the entire list of mailboxes > in a deployment. > > Remember that per RFC 6154 section 2, special use attributes are not required > to be user-specific. (Although oddly, they only appear in private metadata.) > >> In that case, indeed, it >> could be a lengthy lookup. I guess the impact is >> implementation/deployment-dependent. I think we should warn about >> situations like this, but not restrict access to the personal >> namespace(s) in the specification. > I'm afraid I have to disagree. Restricting things to the personal > namespace needs to be an allowed implementation option. Frankly, I'm > not all that comfortable with even a MAY on allowing more, because I don't > think the implications of special-use flags on shared folders have > been given any real scrutiny, especially when they are not necessarily > per-user. > > At an absolute minimum this is going to require some discussion > in the security considerations. A situation where someone can > create a shared folder, open it up with an ACL, and then gather > up sent mail from a new user is not really acceptable. I've addressed this in the latest Github version. It is now fully restricted to the user's personal namespace. I've added some explanation to the "Security Considerations" section. I've left the option open to define a new special use flag that does have an application for shared mailboxes. Regards, -- Stephan Bosch Senior Developer Phone: +49 2761 75252 00 Fax: +49 2761 75252 30 Email: stephan.bosch@dovecot.fi ------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt Dovecot Oy, Lars Sonckin Kaari 10, 02600 Espoo, Finland Managing Director: Markku Kentta Chairman of the Board: Timo Sirainen Board Member: Carsten Dirks ------------------------------------------------------------------------------------- From nobody Sun Mar 4 11:37:10 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 5CA95127775 for ; Sun, 4 Mar 2018 11:36:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] 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 0Kqb9kj2qxRd for ; Sun, 4 Mar 2018 11:36:58 -0800 (PST) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 CE47012D80F for ; Sun, 4 Mar 2018 11:36:57 -0800 (PST) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QPQL9Z9H4W00EGJB@mauve.mrochek.com> for extra@ietf.org; Sun, 4 Mar 2018 11:34:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1520192052; bh=noa3xaXkc6kyrB/+7yxjPOpJPqN26TnDq2PbOhWgGVY=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=hvH1JtjozNl+JpWRAIGQhwAAX32SVPFsnmNJ+9m6Lp2wVSSscsNENFFUFUcidK53o IpK+aXZdnkr5wcant7ctKzlLOJ3YWsADwjKVKr6QYUJxiYAbsvWPly+5NJftqPjCh6 xMmscS+4OzmAx11XsbrfFk4qky9qFrHE2VHrBM3A= 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 <01QPJK8UA574000051@mauve.mrochek.com>; Sun, 4 Mar 2018 11:34:07 -0800 (PST) Cc: Ned Freed , extra@ietf.org Message-id: <01QPQL9VWBH0000051@mauve.mrochek.com> Date: Sun, 04 Mar 2018 11:33:52 -0800 (PST) From: Ned Freed In-reply-to: "Your message dated Sun, 04 Mar 2018 20:31:12 +0100" References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <01QNLYA7BLVQ000051@mauve.mrochek.com> <01QNNBB3GEW0000051@mauve.mrochek.com> To: Stephan Bosch Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sun, 04 Mar 2018 19:37:05 -0000 > Hi Ned, > Op 1/9/2018 om 10:44 PM schreef Ned Freed: > > > >>> Section 3 says: > >>> > >>> If the "mailbox" string argument is omitted, the "specialuse_exists" > >>> test yields true if all of the following statements are true for each > >>> of the special-use flags listed in the "special-use-flags" argument: > >>> > >>> a. at least one mailbox exists in the mail store that has that > >>> particular special-use flag assigned, and > >>> > >>> b. that mailbox allows the user in whose context the Sieve script > >>> runs to "deliver" messages into it. > >>> > >>> I'm concerned about a. - the phrase "the mail store" conjures up an image > >>> of searching through folders belonging to millions of users looking for > >>> one that has an ACL allowing the sieve owner to write to it. > >>> > >>> I'm pretty sure you don't intend this to cover shared folders, so I suggest > >>> changing the text to say something like: > >>> > >>> a. at least one mailbox exists in the user's personal namespace > >>> [NAMESPACE] that has that particular special-use flag assigned, and > >>> > >>> And add the [NAMESPACE] reference pointing at RFC 2342. > >> I must say I didn't consider any special problems with shared mailboxes. > >> The scenario you describe is that lots of people are sharing some of > >> their mailboxes with pretty much everyone. > > It's not a question of lots of people doing it, it's a question of whether or > > not you have an optimized way of looking through the entire list of mailboxes > > in a deployment. > > > > Remember that per RFC 6154 section 2, special use attributes are not required > > to be user-specific. (Although oddly, they only appear in private metadata.) > > > >> In that case, indeed, it > >> could be a lengthy lookup. I guess the impact is > >> implementation/deployment-dependent. I think we should warn about > >> situations like this, but not restrict access to the personal > >> namespace(s) in the specification. > > I'm afraid I have to disagree. Restricting things to the personal > > namespace needs to be an allowed implementation option. Frankly, I'm > > not all that comfortable with even a MAY on allowing more, because I don't > > think the implications of special-use flags on shared folders have > > been given any real scrutiny, especially when they are not necessarily > > per-user. > > > > At an absolute minimum this is going to require some discussion > > in the security considerations. A situation where someone can > > create a shared folder, open it up with an ACL, and then gather > > up sent mail from a new user is not really acceptable. > I've addressed this in the latest Github version. It is now fully > restricted to the user's personal namespace. I've added some explanation > to the "Security Considerations" section. I've left the option open to > define a new special use flag that does have an application for shared > mailboxes. WFM. Ned From nobody Sun Mar 4 11:40:05 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 C2E0C126BF6 for ; Sun, 4 Mar 2018 11:40:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 jsKmFNxaIvJY for ; Sun, 4 Mar 2018 11:39:58 -0800 (PST) Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id D6E65126BFD for ; Sun, 4 Mar 2018 11:39:57 -0800 (PST) Received: from [10.168.3.2] (klara.student.utwente.nl [130.89.162.218]) by mail.dovecot.fi (Postfix) with ESMTPSA id 06BF72B3CD6; Sun, 4 Mar 2018 21:39:56 +0200 (EET) To: Ned Freed Cc: extra@ietf.org References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <01QNLYA7BLVQ000051@mauve.mrochek.com> From: Stephan Bosch Message-ID: <401f753f-e242-cfe4-aa11-68d43583d450@dovecot.fi> Date: Sun, 4 Mar 2018 20:39:55 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <01QNLYA7BLVQ000051@mauve.mrochek.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sun, 04 Mar 2018 19:40:04 -0000 Hi Ned, Op 1/8/2018 om 5:50 PM schreef Ned Freed: > The sieve language is designed not to be specific to IMAP. However, this > extension seems to specifically tied to IMAP in general and to RFC 6154 > in particular. This means there's really no reason not to tighten the > association - in particular, would it not make sense to provide sample > IMAP command sequences to implement the various things in this specification? > > This would be quite helpful to implementors, who might otherwise overlook an > important step. I made a Github issue for this: https://github.com/ietfextra/tracking/issues/16 This will not be applied in the document before the IETF draft cut-off. Regards, -- Stephan Bosch Senior Developer Phone: +49 2761 75252 00 Fax: +49 2761 75252 30 Email: stephan.bosch@dovecot.fi ------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt Dovecot Oy, Lars Sonckin Kaari 10, 02600 Espoo, Finland Managing Director: Markku Kentta Chairman of the Board: Timo Sirainen Board Member: Carsten Dirks ------------------------------------------------------------------------------------- From nobody Sun Mar 4 11:41:31 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 D0D32126BF6 for ; Sun, 4 Mar 2018 11:41:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 6-uK5Qg9JlM8 for ; Sun, 4 Mar 2018 11:41:28 -0800 (PST) Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id 71C811242F7 for ; Sun, 4 Mar 2018 11:41:28 -0800 (PST) Received: from [10.168.3.2] (klara.student.utwente.nl [130.89.162.218]) by mail.dovecot.fi (Postfix) with ESMTPSA id A92252B3CD6 for ; Sun, 4 Mar 2018 21:41:27 +0200 (EET) From: Stephan Bosch To: extra@ietf.org References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <01QNLYA7BLVQ000051@mauve.mrochek.com> <01QNNBB3GEW0000051@mauve.mrochek.com> <990a2344-d003-5a05-6b5c-c9d72a259753@dovecot.fi> <8affa07e-7e2f-ef54-fcbd-e450b5636eed@dovecot.fi> Message-ID: Date: Sun, 4 Mar 2018 20:41:26 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <8affa07e-7e2f-ef54-fcbd-e450b5636eed@dovecot.fi> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sun, 04 Mar 2018 19:41:30 -0000 Op 2/15/2018 om 11:30 PM schreef Stephan Bosch: > Op 1/17/2018 om 12:14 AM schreef Stephan Bosch: >> Hi Ned, >> >> Op 1/9/2018 om 10:44 PM schreef Ned Freed: > Slowly making progress on this one. > > I just gave the point below a fresh look: > >>>>> The other aspect of the many-many mapping is the fact that a single mailbox can >>>>> have multiple special use attributes. The draft supports this in the context of >>>>> specialuse_exists but not in the context of fileinto. I think this is fine, but >>>>> I want to make sure everyone is happy with this limitation, including the fact >>>>> that because of this you won't be able to create mailbox with fileinto with >>>>> multiple special use attributes. >>>> Good point. For sake of discussion, let's assume we allow a string list >>>> for the :specialuse parameter. The semantics for creation of a mailbox >>>> would be quite clear: all of those flags are assigned to the new >>>> mailbox. >>> Seems reasonable. >>> >>>> But what would that mean for the mailbox lookup? Are we looking >>>> for a mailbox that has all of these flags, one of these flags or just >>>> the first flag listed? >>> The convention elsewhere seems pretty clearly to be for it to be an AND rather >>> than an OR. >> I agree. >> >>>> Another question is whether mailboxes with several special-use flags are >>>> really that useful. >>> Apart from \All, which I would hope is not up to clients to set, I don't see >>> them as being useful. But I may be missing some use cases, which is why I >>> brought it up. >> Ok. > Now my question to everyone is: do I need to change anything or is the > fileinto limitation acceptable? Opinions anyone? Regards, -- Stephan Bosch Senior Developer Phone: +49 2761 75252 00 Fax: +49 2761 75252 30 Email: stephan.bosch@dovecot.fi ------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt Dovecot Oy, Lars Sonckin Kaari 10, 02600 Espoo, Finland Managing Director: Markku Kentta Chairman of the Board: Timo Sirainen Board Member: Carsten Dirks ------------------------------------------------------------------------------------- From nobody Mon Mar 5 10:45:51 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 9B21A12E05D; Mon, 5 Mar 2018 10:45:42 -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.74.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152027554256.14535.9402189875041066112@ietfa.amsl.com> Date: Mon, 05 Mar 2018 10:45:42 -0800 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-02.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 05 Mar 2018 18:45:46 -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 Email Filtering: Delivering to Special-Use Mailboxes Author : Stephan Bosch Filename : draft-ietf-extra-sieve-special-use-02.txt Pages : 8 Date : 2018-03-05 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 IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-special-use/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-sieve-special-use-02 https://datatracker.ietf.org/doc/html/draft-ietf-extra-sieve-special-use-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-sieve-special-use-02 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 Mon Mar 5 11:05:07 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 CBF8212E039 for ; Mon, 5 Mar 2018 11:05:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mailforce.net header.b=xMavQpGE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=NczVD+b0 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 HBE61P89e6La for ; Mon, 5 Mar 2018 11:05:00 -0800 (PST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8037312D86B for ; Mon, 5 Mar 2018 11:05:00 -0800 (PST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E199920DC4; Mon, 5 Mar 2018 14:04:59 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Mon, 05 Mar 2018 14:04:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=cc:content-transfer-encoding:content-type:date:from :in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UvD29xeNGCvoAEVZv BMrgOQ8PelP1JbTv/6jJWv8hYQ=; b=xMavQpGE5zaBMCc9/YGJ0lXEOTQNrBQqZ +TNZy7qBYTqn2ciBNJloz/Tf3l0T41hicRIfgc19nnpvt16e8A760mbqr+QZ3WYV pt9b7JHbGABKb8uMDlnM2/SvQHjjVgokn0gUHFLNDDRHV+CE2LGcVcPNLoFnAAvb j0PqNNXh43pI9qwIEvthRKcKCSIUYHphQzgR3TuDq/BP2o3g/yGW1cZDKqeq3WUy pUjanksQY4L5M88inQygzhJsm67tab+FQOQxH+1qNXvswGFZDHKzBxD1nTCDGNT4 dtfjsnuodbaLgVyYHoy163RavqbXCA+3smnnIlZseMPbwDdlDJ6Ew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UvD29x eNGCvoAEVZvBMrgOQ8PelP1JbTv/6jJWv8hYQ=; b=NczVD+b0dvnHCRdOysh16Z KjaKKZAYF82bje5G4uMFAewFQBtJFVJ/oLaMSz1DiiThULZXK/l/cdYlDToejQrJ wOoF8ZSS7/P5V+Ze98IEL2hlfo3QV6mYdjNwX/BCuQp7zpF1l9FqPPvrTbkQTxK2 GW2BJZ9/kSWOMPD+m2FlpxGTCU8i5NOkWR5ikdx4lDMnxuv0SPHQ7V0Z8cUuNjWo 6mxwbZHbBZvNJdo9gBTg6Ef3QQm3J570+/Pc37X34E+ytwdTRkOX4KEkvH4f+jrY cTJx8Uh4p138Dmy4VlhP4XTjDwvBkKTc6ZZiW65yP2pcSIvMFvvZy1WdX0+BpRKg == X-ME-Sender: Received: from [192.168.1.71] (108-84-31-27.lightspeed.tukrga.sbcglobal.net [108.84.31.27]) by mail.messagingengine.com (Postfix) with ESMTPA id 83BD37E591; Mon, 5 Mar 2018 14:04:59 -0500 (EST) References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <01QNLYA7BLVQ000051@mauve.mrochek.com> <01QNNBB3GEW0000051@mauve.mrochek.com> <990a2344-d003-5a05-6b5c-c9d72a259753@dovecot.fi> <8affa07e-7e2f-ef54-fcbd-e450b5636eed@dovecot.fi> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <1ED47E4F-C8E0-471E-B0D5-ACBDB20498E6@glyphein.mailforce.net> Cc: extra@ietf.org X-Mailer: iPhone Mail (13G36) From: Stan Kalisch Date: Mon, 5 Mar 2018 14:04:56 -0500 To: Stephan Bosch Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 05 Mar 2018 19:05:06 -0000 >> On Mar 4, 2018, at 2:41 PM, Stephan Bosch wrot= e: >> I just gave the point below a fresh look: >>=20 >>>>>> The other aspect of the many-many mapping is the fact that a single m= ailbox can >>>>>> have multiple special use attributes. The draft supports this in the c= ontext of >>>>>> specialuse_exists but not in the context of fileinto. I think this is= fine, but >>>>>> I want to make sure everyone is happy with this limitation, including= the fact >>>>>> that because of this you won't be able to create mailbox with fileint= o with >>>>>> multiple special use attributes. >>>>> Good point. For sake of discussion, let's assume we allow a string lis= t >>>>> for the :specialuse parameter. The semantics for creation of a mailbox= >>>>> would be quite clear: all of those flags are assigned to the new >>>>> mailbox. >>>> Seems reasonable. >>>>=20 >>>>> But what would that mean for the mailbox lookup? Are we looking >>>>> for a mailbox that has all of these flags, one of these flags or just >>>>> the first flag listed? >>>> The convention elsewhere seems pretty clearly to be for it to be an AND= rather >>>> than an OR. >>> I agree. >>>=20 >>>>> Another question is whether mailboxes with several special-use flags a= re >>>>> really that useful. >>>> Apart from \All, which I would hope is not up to clients to set, I don'= t see >>>> them as being useful. But I may be missing some use cases, which is why= I=20 >>>> brought it up. >>> Ok. >> Now my question to everyone is: do I need to change anything or is the >> fileinto limitation acceptable? >=20 > Opinions anyone? For the sake of argument, the only somewhat plausible scenario I can come up= with is one for outgoing messages, where the sender wants messages dynamica= lly assigned to \Sent mailboxes on based on the identities of recipients. T= he sender, however, wants the retention of these messages to be ephemeral, s= o they also mark these mailboxes with the attribute of \Trash. Stan= From nobody Mon Mar 5 15:32:27 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 0F95712EB5A for ; Mon, 5 Mar 2018 15:31:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 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, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 eFGnk8cqdZ-W for ; Mon, 5 Mar 2018 15:31:54 -0800 (PST) Received: from aserp2120.oracle.com (aserp2120.oracle.com [141.146.126.78]) (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 80DD3120227 for ; Mon, 5 Mar 2018 15:31:39 -0800 (PST) Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w25NVdIa002417 for ; Mon, 5 Mar 2018 23:31:39 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=ptWCDcf+XdAue62r4P0xycYRCUwacLOqUrdgAwOKMmo=; b=KG6ybYLo4WR0LIMTTTyjM6N9Xn2v/wSOQed+Vdvd/32OY4xHPViuzolxy4ZLFHD2GiJu wccq4d5C/qFeJcwi7ck/y2LQph/6aiQ1mh1UzfmL27C1t0nU2UPvvO0Ndg9iNhfvLGyU G2U/4C3OUek0UvPCjTuTP/TvLkBxkYLt1YJbk1F0YzXyJkdqHrN9eW1sFPJEaXy7Es7v uBH29AzNn4ygEn5L6GQRwdUoY3VVmtQseD9Zm8yOH6qgUDLOuVfMSwTz0x36+nnbusbj nSdEyFhfkpEokxgoCqURmL/bNxqbbMJx/VQ4jxKj4nyEmMv6uf19vD/BDqd3yTlMXMZt 6g== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2120.oracle.com with ESMTP id 2ghe3kgbjq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 05 Mar 2018 23:31:38 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w25NVY6e011020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 5 Mar 2018 23:31:35 GMT Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w25NVYG2024452 for ; Mon, 5 Mar 2018 23:31:34 GMT Received: from [10.145.183.55] (/10.145.183.55) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 05 Mar 2018 15:31:34 -0800 From: "Chris Newman" To: extra@ietf.org Date: Mon, 05 Mar 2018 15:31:29 -0800 X-Mailer: MailMate (1.10r5443) Message-ID: <111D54E3-27EE-4D2E-8EFD-1FA0879A8E22@oracle.com> In-Reply-To: <152018441102.11996.16139669468419652701@ietfa.amsl.com> References: <152018441102.11996.16139669468419652701@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8823 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=13 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=518 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803050267 Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap-64bit-03.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 05 Mar 2018 23:32:05 -0000 On 4 Mar 2018, at 9:26, internet-drafts@ietf.org wrote: > 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 : 64bit body part and message sizes in IMAP4 > Authors : Alexey Melnikov > Jayantheesh S B > Filename : draft-ietf-extra-imap-64bit-03.txt > Pages : 7 > Date : 2018-03-04 > > Abstract: > This document defines an IMAPv4rev1 extension that extends the > existing IMAPv4rev1 32 Bit message and body part sizes to 63 bit. > Both the base IMAP specification (RFC 3501) and several extensions > are updated. I reviewed this document. This document fails to state how the server should respond if a message in a mailbox has a size larger than 32-bit when a traditional IMAP client accesses that mailbox. What value does the server provide for the SIZE FETCH attribute in this case? Can a server return NO on select of a mailbox with a jumbo message when the client is a "legacy" client? Where are the examples of this behavior in the specification? What is the end-user experience for this? If a legacy end-user has a shared mailbox and allows another user to append a "jumbo" message to the shared mailbox, will that create a hidden channel problem? Would we need a separate ACL bit or flag of some sort to grant permission to insert "jumbo" messages into a mailbox to avoid such problems? This isn't merely changing the protocol, it's changing the implied persistent mail store format in an incompatible fashion. This has serious backwards compatibility issues for clients not updated to support this. A change like this requires both a solid justification and discussion of the compatibility implications (see RFC 6855). I believe this document is incomplete and inappropriate for advancement until it covers both topics. Setting a precedent that it's ok to change the implied persistent mail store semantics without strong justification is something I oppose. I note that this does not appear to change the IMAP UID to be 64-bit although it doesn't say why. This is also an omission from the document. Finally, if we're getting into the business of changing persistent storage semantics, I'd like to do it as few times as possible to minimize overall disruption to the infrastructure. There's a clear need for a unique message identifier that is not mailbox-specific. That's also an incompatible change to the implied persistent storage semantics. If we're going to make that change at some point in the future (something I would support on the grounds of compatibility with both JMAP and deployed mail services with tag-based mailboxes), I'd like to see both proposed incompatible persistent storage format changes made at the same time to minimize the disruption to the infrastructure. I also note that this change forces an IMAP URL resolver to either unconditionally send "enable 64bit" (if the capability is present) or to try once and retry with "enable 64bit" if the first attempt fails in a way that is recognizable (something presently not specified). Both options are a significant increase in the complexity of such a URL resolver. At this point, I find this proposal to be high cost/disruption with no stated benefit or justification. I presently oppose advancement of this proposal. - Chris From nobody Mon Mar 5 16:13:41 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 3D27012D7FC; Mon, 5 Mar 2018 16:13:40 -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.74.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152029522021.12846.15559615969586678409@ietfa.amsl.com> Date: Mon, 05 Mar 2018 16:13:40 -0800 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-status-size-00.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 06 Mar 2018 00:13:40 -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 : Internet Message Access Protocol (IMAP) - STATUS=SIZE Extension Author : Stephan Bosch Filename : draft-ietf-extra-imap-status-size-00.txt Pages : 5 Date : 2018-01-07 Abstract: This document adds a new capability called "STATUS=SIZE" to the Internet Message Access Protocol (IMAP). It allows retrieving the total storage size of a mailbox with a single STATUS command rather than retrieving and summing the sizes of all individual messages in that mailbox. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-status-size/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-status-size-00 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-status-size-00 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 Mon Mar 5 16:14:08 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 1253912EAA5; Mon, 5 Mar 2018 16:14:03 -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.74.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152029524303.12745.14838554271521574335@ietfa.amsl.com> Date: Mon, 05 Mar 2018 16:14:03 -0800 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-savedate-00.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 06 Mar 2018 00:14:04 -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 : Internet Message Access Protocol (IMAP) - SAVEDATE Extension Author : Stephan Bosch Filename : draft-ietf-extra-imap-savedate-00.txt Pages : 6 Date : 2018-01-07 Abstract: This document adds a new capability called "SAVEDATE" to the Internet Message Access Protocol (IMAP). It defines a new IMAP message attribute called 'save date' that, unlike the existing 'internal date' attribute, always indicates the moment at which the message was saved in its current mailbox. The SAVEDATE capability extends the FETCH command with the means to retrieve the save date attribute and it extends the SEARCH command to allow using that attribute in searching criteria. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-savedate/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-savedate-00 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-savedate-00 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 Mon Mar 5 16:21:44 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 D892112EAA5 for ; Mon, 5 Mar 2018 16:21:36 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=RDTJOfsk; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LQhtq+x/ 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 uPDw_o6MTVtT for ; Mon, 5 Mar 2018 16:21:35 -0800 (PST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EADC12EABF for ; Mon, 5 Mar 2018 16:21:35 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0F3EB21806 for ; Mon, 5 Mar 2018 19:21:34 -0500 (EST) Received: from web5 ([10.202.2.215]) by compute6.internal (MEProxy); Mon, 05 Mar 2018 19:21:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=y8lMiZxvyGCMIrdTfQNeCja3oRsTLLGL/LNBHxxzw ik=; b=RDTJOfskVFKC5Oksmi4uhm2w/zaL1GINo0AQSNFM3HbC9/3T38C/A24Jd EAAFfP+fnc1dS5oXKuay4/yqc1qp79Nip4Vr4+OahuTiZHWZitREb9Fh5SKya2iE Mmbww091Imz/EScNNoSZ5GJw4ODq+K7yj9xq7plMl4TZTqPxPnFj/tmtAe3eB8i+ XYuHkYsEiGOjCg0qT7RhIUm9m+aVmX33dqnat7q2/s7XCAWYEDfpFiOg/VyGZqHv OL7mSPnqMP8Yr35rL75jeiACxcjWv0S3COPmtJKeY3TuHaFKSaPTX3xF/S81oSAV 1SQwClXfkzHiGs6Vztpie3sVVACiw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=y8lMiZxvyGCMIrdTfQNeCja3oRsTL LGL/LNBHxxzwik=; b=LQhtq+x/XwRmbACgsSRX1Dgjf3LXgaWhfpl6seQSYlweB daDuVY+q0ADAnYa03alce1iyDhltoOaIKOwHkcgPS3bPScxNSp5t7UbnE95u3n6t 0QI03MyYB4UBz5VVV9Y4BG05Igy1k1jJMSyTAGnLR5cT6msg2w0TDbCHwnU44KX0 1SpOJzsJI+9XeyQvr3Ep5Y2heIIqIENH3UIR9DNfePowkhQ/8oXzZHmuMKEoAN0I xBA2UsGqABCQvlX9OgiEdBf8TfJGkq7hWNKwtSNAPLDLRXC7i85u8val/ofRrpAD ymsYSShhRVPQ2e7g2QeqEuBb0O6DjsyCS8HjadoGg== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id D6B699E1DA; Mon, 5 Mar 2018 19:21:33 -0500 (EST) Message-Id: <1520295693.2226452.1292705376.1696A8CF@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152029569322264520" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b86e6959 Date: Tue, 06 Mar 2018 11:21:33 +1100 Archived-At: Subject: [Extra] SAVEDATE and STATUS=SIZE drafts X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 06 Mar 2018 00:21:41 -0000 This is a multi-part message in MIME format. --_----------=_152029569322264520 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Apologies for the late arrival of those two as accepted documents. It was entirely me not knowing how to drive the software and assuming they were already accepted. Hopefully Stephen's revisions are able to be accepted into the system before the cutoff still. If not, I'm sure we will be happy to receive them over the mailing list and review them as if they were accepted, and I'll enter them as soon as IETF101 starts and submissions are allowed again. Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152029569322264520 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Apologies for the late arrival of those two as accepted documents.  It was entirely me not knowing how to drive the software and assuming they were already accepted.  Hopefully Stephen's revisions are able to be accepted into the system before the cutoff still.

If not, I'm sure we will be happy to receive them over the mailing list and review them as if they were accepted, and I'll enter them as soon as IETF101 starts and submissions are allowed again.

Bron.

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


--_----------=_152029569322264520-- From nobody Sat Mar 10 12:52:24 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 7BF65127333 for ; Sat, 10 Mar 2018 12:52:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mailforce.net header.b=KkrMOADX; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RAHvxawn 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 vD9cIhs5oKZ2 for ; Sat, 10 Mar 2018 12:52:21 -0800 (PST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9864D127444 for ; Sat, 10 Mar 2018 12:52:21 -0800 (PST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E0F9820C2B; Sat, 10 Mar 2018 15:52:20 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sat, 10 Mar 2018 15:52:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=cc:content-transfer-encoding:content-type:date:from :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=QlukGbD2JZvDZn1bl/NVGwUuoriJu jPGy+yWD6VpZRU=; b=KkrMOADX/7ADvgASDFMl3OXfRf2U5vs53GgyK62Sn8Y1T LsLK6ZSu6UqNJIwpWvTrtCAeY+Ljn2w2vw8+IWAy9YbvQFXNIka4ZG+dgidSLxoG 0ndjIaRzExrvtbgxhMPZADrF/f2EBkFGC6b6VU5KKacP99hwKYOby/L2PKfp2gUz EajsV3fBOEPAJ3/a9h6ISt1a1CxgONeh1ecQGMwrQjguOscBslA/OEXRG+GE4ew+ zcsFkRVWDnN0mXA4pDZfEINvD6SBMo8PZCv4HTzVrI/HHSKhei2QhFBFAdKXGxyO QYfSMTr18H5p4avZYrTi+zRKjIdGSn40TttB1ky6A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QlukGbD2JZvDZn1bl /NVGwUuoriJujPGy+yWD6VpZRU=; b=RAHvxawnEyAUYvpfr0/dxwlcbyvALjWk3 q5Mo/spn5aeS67YnW2tHIF1OHrMRM0CprRell57HQ6ZgtTMzhFoRLp0mbIXVST3t nJR7bWHWc8HzOT4RjXQc9YdO3UJ+dJ83Db3n3vBRoKRSpALdIZfmyZdU0jRcgGFy gOYhweXa2uci0/kZJqJMUWmnGggsd6u13RxThsoJ9HLa+0pzHwztG7jPxRTqTTwY YxPGIv9bvIe8N7T4unJYmKoDga+g6JJ+asps5gh/UhERl/BTfNI8iNlYZMgjZQO4 iyDfB+2J1IgTSbvGvpjFSf5HM7BbYfF+il48YsjHe3/YFoemhA4bA== X-ME-Sender: Received: from [192.168.1.71] (108-84-31-27.lightspeed.tukrga.sbcglobal.net [108.84.31.27]) by mail.messagingengine.com (Postfix) with ESMTPA id 8E8457E0F0; Sat, 10 Mar 2018 15:52:20 -0500 (EST) References: <8111b364-7f60-681f-bac6-ceacce003135@aegee.org> From: Stan Kalisch Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-5D5D761C-7D1C-4159-8D30-12D2E0024DDA X-Mailer: iPhone Mail (13G36) Message-Id: <2457E01E-CB0D-4B45-88CE-41BB926EE668@glyphein.mailforce.net> Date: Sat, 10 Mar 2018 15:52:17 -0500 Cc: =?utf-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= Content-Transfer-Encoding: 7bit To: extra@ietf.org Archived-At: Subject: [Extra] Fwd: [sieve] iana.org/assignments/sieve-extensions/ - fileinto X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 10 Mar 2018 20:52:23 -0000 --Apple-Mail-5D5D761C-7D1C-4159-8D30-12D2E0024DDA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Is this something Extra can take up at IETF 101? It seems especially timely= considering the request WRT draft-ietf-extra-sieve-special-use. Thanks, Stan Begin forwarded message: > From: =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0= =BE=D0=B2 > Date: March 1, 2018 at 3:04:09 PM EST > To: sieve@ietf.org > Subject: [sieve] iana.org/assignments/sieve-extensions/ - fileinto >=20 > Hello, >=20 > I propose amending to https://www.iana.org/assignments/sieve-extensions/si= eve-extensions.xhtml#sieve-extensions-2 >=20 > Capability name: fileinto > RFC number: [RFC5228] (Sieve base spec) >=20 > to >=20 > RFC number: [RFC5228] (Sieve base spec), [RFC5490][RFC3894][RFC5232] >=20 > as the latter add the :create, :copy and :flags parameters. >=20 > Also consider adding draft-ietf-extra-sieve-special-use there. >=20 > Regards > =D0=94=D0=B8=D0=BB=D1=8F=D0=BD >=20 > _______________________________________________ > sieve mailing list > sieve@ietf.org > https://www.ietf.org/mailman/listinfo/sieve --Apple-Mail-5D5D761C-7D1C-4159-8D30-12D2E0024DDA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi,

Is this something Extra can take u= p at IETF 101?  It seems especially timely considering the request WRT <= span style=3D"background-color: rgba(255, 255, 255, 0);">draft-ietf-extra-si= eve-special-use.


=
Thanks,
Stan
=

Begin forwarded message:
From: =D0=94=D0=B8=D0=BB=D1=8F= =D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 <dilyan.palauzov@aegee.org>
Date: March 1, 2018 at 3:04:09 PM EST
To: sieve@ietf.org
Subject: [sieve] iana.org/assignments/sieve-extensions/= - fileinto

Hello,

I propose amending to https://www.iana.org/assignments/sieve-extensions/sieve= -extensions.xhtml#sieve-extensions-2

Ca= pability name: fileinto
RFC number: [RFC5228] (Sieve base sp= ec)

to

RFC= number: [RFC5228] (Sieve base spec), [RFC5490][RFC3894][RFC5232]
=
as the latter add the :create, :copy and :flags param= eters.

Also consider adding draft-ietf-extr= a-sieve-special-use there.

Regards  =D0=94=D0=B8=D0=BB=D1=8F=D0=BD

_______________________________________________
sieve mai= ling list
sieve@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/sieve
= = --Apple-Mail-5D5D761C-7D1C-4159-8D30-12D2E0024DDA-- From nobody Mon Mar 12 05:00:40 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 D59CC124B0A for ; Mon, 12 Mar 2018 05:00:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 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, T_RP_MATCHES_RCVD=-0.01] 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 zUWlVetO2hI3 for ; Mon, 12 Mar 2018 05:00:30 -0700 (PDT) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 8C822126C83 for ; Mon, 12 Mar 2018 05:00:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1520856029; d=isode.com; s=june2016; i=@isode.com; bh=TvLd0LHu7fyo6X0RvigYYradqYL3+Kc3bpiIXnzrqdU=; 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=rDo5XD3ISUNj60RMJYGw0iBPUrn2kMdsP+pG9qjlXU1eYGBvoV+Ef0KBQ2iIUeRY4J0BjX H6b7MiHIdoGITniJ4g6W9Lkbq615FXY7llzyiin+3lg+DjR1vm/rpo+7JeNWCRnpMIC1al Da7HVQTpfWGG2HX5eEH2o18EK0LliHY=; 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, 12 Mar 2018 12:00:29 +0000 To: Stan Kalisch , extra@ietf.org Cc: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= References: <8111b364-7f60-681f-bac6-ceacce003135@aegee.org> <2457E01E-CB0D-4B45-88CE-41BB926EE668@glyphein.mailforce.net> From: Alexey Melnikov Message-ID: <7756d2cc-a283-f07f-edde-d0f2acbf0c06@isode.com> Date: Mon, 12 Mar 2018 12:00:25 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 In-Reply-To: <2457E01E-CB0D-4B45-88CE-41BB926EE668@glyphein.mailforce.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------77428DC4DD4B05EB11F86FB2" Content-Language: en-GB Archived-At: Subject: Re: [Extra] Fwd: [sieve] iana.org/assignments/sieve-extensions/ - fileinto X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 12 Mar 2018 12:00:33 -0000 --------------77428DC4DD4B05EB11F86FB2 Content-Type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: quoted-printable Hi, On 10/03/2018 20:52, Stan Kalisch wrote: > Hi, > > Is this something Extra can take up at IETF 101? =C2=A0It seems especially= =20 > timely considering the request WRT draft-ietf-extra-sieve-special-use. I was thinking the same. This might either need a short document or=20 maybe it can be done by directly talking to IANA. Best Regards, Alexey > Thanks, > Stan > > Begin forwarded message: > >> *From:* =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0= =B7=D0=BE=D0=B2 > > >> *Date:* March 1, 2018 at 3:04:09 PM EST >> *To:* sieve@ietf.org >> *Subject:* *[sieve] iana.org/assignments/sieve-extensions/=20 >> - fileinto* >> >> Hello, >> >> I propose amending to=20 >> https://www.iana.org/assignments/sieve-extensions/sieve-extensions.xhtml#= sieve-extensions-2 >> >> Capability name: fileinto >> RFC number: [RFC5228] (Sieve base spec) >> >> to >> >> RFC number: [RFC5228] (Sieve base spec), [RFC5490][RFC3894][RFC5232] >> >> as the latter add the :create, :copy and :flags parameters. >> >> Also consider adding draft-ietf-extra-sieve-special-use there. >> >> Regards >> =C2=A0=D0=94=D0=B8=D0=BB=D1=8F=D0=BD >> >> _______________________________________________ >> sieve mailing list >> sieve@ietf.org >> https://www.ietf.org/mailman/listinfo/sieve > > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra --------------77428DC4DD4B05EB11F86FB2 Content-Type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable

Hi,

On 10/03/2018 20:52, Stan Kalisch wrote:

Hi,

Is this something Extra can take up at IETF 101? =C2=A0It seems especially timely considering the reques= t WRT draft-= ietf-extra-sieve-special-use.

I was thinking the same. This might either need a short document or maybe it can be done by directly talking to IANA.

Best Regards,
Alexey
Thanks,
Stan

Begin forwarded message:

From: =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB= =D0=B0=D1=83=D0=B7=D0=BE=D0=B2 <dilyan.palauzov@aegee.org>
Date: March 1, 2018 at 3:04:09 PM EST
To: sieve@ietf.org
Subject: [sieve] iana.org/assignments/sieve-extensions= / - fileinto

Hello,

I propose amending to https://www.iana.org/assignments/siev= e-extensions/sieve-extensions.xhtml#sieve-extensions-2

Capability name: fileinto
RFC number: [RFC5228] (Sieve base spec)

to

RFC number: [RFC5228] (Sieve base spec), [RFC5490][RFC3894][RFC5232]

as the latter add the :create, :copy and :flags parameters.

Also consider adding draft-ietf-extra-sieve-special-use there.

Regards
=C2=A0=D0=94=D0=B8=D0=BB=D1=8F=D0=BD

_______________________________________________
sieve mailing list
s= ieve@ietf.org
https://www.ietf.org/mailman/listinfo= /sieve


_______________________________________________
Extra mailing list
Extra@i=
etf.org
https://www.ietf.org/mailman/listinfo/extra

--------------77428DC4DD4B05EB11F86FB2-- From nobody Thu Mar 15 08:36:09 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 D723B12711E for ; Thu, 15 Mar 2018 08:36:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.009 X-Spam-Level: X-Spam-Status: No, score=-2.009 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, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 rGlq3fSxl7Ci for ; Thu, 15 Mar 2018 08:36:06 -0700 (PDT) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id E7F7F1273B1 for ; Thu, 15 Mar 2018 08:36:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1521128165; d=isode.com; s=june2016; i=@isode.com; bh=qpuh7np6VR3UVt1EEKcspGhxXgYdpGyWgcfT+L3OQIQ=; 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=Wt/g525JAE0RfpCws0L6fDb7dXXiUvaNJ/uU3o0R0YEi1hzrVec+EaXfR715/YeQAtFu8q 9hJHYk0qdwETkFMpmpqZnqFMJBthmrpch4rc0CZyZAw4FODYIKXGyADZkJg+QGkanBQsHL V8vHbhfvcLoMNMzboztb8YnJt3U6rys=; 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 ; Thu, 15 Mar 2018 15:36:05 +0000 To: Bron Gondwana , extra@ietf.org References: <1519691879.2831523.1284423560.70A87A64@webmail.messagingengine.com> From: Alexey Melnikov Message-ID: <0f0df36a-4ce8-7b41-3407-db3d43e8a24a@isode.com> Date: Thu, 15 Mar 2018 15:35:42 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 In-Reply-To: <1519691879.2831523.1284423560.70A87A64@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------6598956339BD6844759A3C0C" Content-Language: en-GB Archived-At: Subject: Re: [Extra] Spam Reporting? X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 15 Mar 2018 15:36:08 -0000 This is a multi-part message in MIME format. --------------6598956339BD6844759A3C0C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 27/02/2018 00:37, Bron Gondwana wrote: > Digging through my very old FLAGGED emails to see if there was > anything I should be looking at, this sprung up: > > https://datatracker.ietf.org/doc/draft-ordogh-spam-reporting-using-imap/ > > In a discussion from Alexey following on from my Fosdem report at the > time: > > https://www.mail-archive.com/search?l=cyrus-devel%40lists.andrew.cmu.edu&q=subject%3A%22FOSDEM+Report+%5C-+Saturday%22&x=0&y=0 > > Is there any appetite for reviving discussion of a standard way to > report spam/phishing/whatever from clients such that the server knows > that a user has explicitly made the determination? > IMHO, whether this is going to be a new command or just use of a keyword/special-use mailbox, we should document the API for doing this. --------------6598956339BD6844759A3C0C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On 27/02/2018 00:37, Bron Gondwana wrote:

Digging through my very old FLAGGED emails to see if there was anything I should be looking at, this sprung up:


In a discussion from Alexey following on from my Fosdem report at the time:


Is there any appetite for reviving discussion of a standard way to report spam/phishing/whatever from clients such that the server knows that a user has explicitly made the determination?


IMHO, whether this is going to be a new command or just use of a keyword/special-use mailbox, we should document the API for doing this.

--------------6598956339BD6844759A3C0C-- From nobody Mon Mar 19 11:11:01 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 B9BD712D7FC for ; Mon, 19 Mar 2018 11:10:59 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=ZMyIZLbh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=F3yosuFM 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 9EdmCf_aGOA2 for ; Mon, 19 Mar 2018 11:10:57 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31C30126C25 for ; Mon, 19 Mar 2018 11:10:56 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5171E20DAD for ; Mon, 19 Mar 2018 14:10:55 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Mon, 19 Mar 2018 14:10:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=fIPbPxzrvJ7CMMkFNvNzIpUZNz33sLNk2LEgyVUR9 sU=; b=ZMyIZLbh3tb0hAIjYGOdtPCUlb1QmR702++qO72iyvh/F8A9cNrHjKFad VWseE/GeIXWZ3biKxrJmLutUo640czPJtaDEt3YDCytk01VApOCmIGJxHFUT9o2h k//TJOWZ7yK6B/kCr3hxlIFywJKtFTPTvLVk2bv00hSJXeMvMNM5GtpRrErtGVE5 YrGJh2kwEMKBaxk2QuFf11fDalYePLHbijlKAun3NE5VQaTuOGZ0diSZ6CWW7b81 yzUrMI2HNRqVwfQBjaNwM8Xtatfo/7QuuFKRX47aJ0fOFUG/X9XZ9/eo+CF2PMmb N7TGQ5MjlXzDcpvY8M3U7ym4uTJRw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=fIPbPxzrvJ7CMMkFNvNzIpUZNz33s LNk2LEgyVUR9sU=; b=F3yosuFMSrjCD24TXGbK1P0Enhx2ApLvjk4cr9IrXacB+ Cs6UxCTSp+4XzHHzhGomWdAWiXlN4SRkZBHWBEjTu4yNiwrTbHByZ/NctVWPH8GI UC4hNMoZBazv/7fRYh6mE+cYRo75cC8j/SW3TBCi0gbzMmueVtWo/9cm9DUXSXbX ylVBCKLENS16iW41Ce4Sh+ZEk921NxQWwSxEOsA3uqkApDOKMkkrTc2Sybz+xeUJ qIrAXK3D6M0SCHJHSphNH5IUYpfTK8X4zVHXgKZXCTLfcsxaZCXpaAlaq3mvMG58 nNdySg+hIn1GPlfOy5HCxtn45fCuGw2LNlU/osc7g== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 2A290BA43B; Mon, 19 Mar 2018 14:10:55 -0400 (EDT) Message-Id: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152148305440076541" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Tue, 20 Mar 2018 05:10:54 +1100 Archived-At: Subject: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 19 Mar 2018 18:11:00 -0000 This is a multi-part message in MIME format. --_----------=_152148305440076541 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" https://datatracker.ietf.org/doc/draft-gondwana-imap-uniqueid/ This is a pretty rough first draft, so the wording will need some smithing, but the implementation looks good in Cyrus IMAP: brong@zula:~/src/cyrus-imapd$ git show | diffstat imapd.c | 43 +++++++++++++++++++++++++++++--------- imapd.h | 15 ++++++++----- imapparse.c | 29 ++++++++++++++++++++++++++ index.c | 26 +++++++++++++++++++++++ mailbox.h | 3 +- search_expr.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++6 files changed, 162 insertions(+), 18 deletions(-) That implements the entire spec. Of course, we already have the unique IDs stored internally, and we've already implemented all the JMAP support for IDs, so it makes sense that it was easy for me. Open questions: * bytestring 1..255 for everything? * more "prior art" discussion for X-GM work? Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152148305440076541 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"

This is a pretty rough first draft, so the wording will need some smithing, but the implementation looks good in Cyrus IMAP:

brong@zula:~/src/cyrus-imapd$ git show | diffstat
imapd.c       |   43 +++++++++++++++++++++++++++++---------
imapd.h       |   15 ++++++++-----
imapparse.c   |   29 ++++++++++++++++++++++++++
index.c       |   26 +++++++++++++++++++++++
mailbox.h     |    3 +-
search_expr.c |   64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 162 insertions(+), 18 deletions(-)

That implements the entire spec.  Of course, we already have the unique IDs stored internally, and we've already implemented all the JMAP support for IDs, so it makes sense that it was easy for me.

Open questions:
* bytestring 1..255 for everything?
* more "prior art" discussion for X-GM work?

Cheers,

Bron.

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


--_----------=_152148305440076541-- From nobody Tue Mar 20 03:45:40 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 9D5821242F7 for ; Tue, 20 Mar 2018 03:45:37 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 vA00VfUHEzdi for ; Tue, 20 Mar 2018 03:45:34 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EF7E126D0C for ; Tue, 20 Mar 2018 03:45:21 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 6DB4EFA00AD; Tue, 20 Mar 2018 10:45:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521542719; bh=rrDe+aT8DW4/MSM+s80FOqBgadJK80pfmNdmxfMv0+4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mJ0IXXzHnmFb7egwARPK7LGHXnJWSc+0tplsSOgsdUT9ll/ptoIJl4tnXtb05i8EC lECPxj/Ov1Lc35HDS448O3AVPABWs9bs4NBUuSCN6im91DAR+k8YjzPU4pdDr5xkTo oZEwN9Joj2K7VHlG8Rbwd0u6CqmsbzdpXNruK2R4= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521542718-12074-31493/11/1; Tue, 20 Mar 2018 10:45:18 +0000 From: Arnt Gulbrandsen To: Bron Gondwana Cc: extra@ietf.org Date: Tue, 20 Mar 2018 10:45:17 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: In-Reply-To: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 10:45:38 -0000 Bron Gondwana writes: > https://datatracker.ietf.org/doc/draft-gondwana-imap-uniqueid/ > > This is a pretty rough first draft, so the wording will need > some smithing, but the implementation looks good in Cyrus IMAP: I see you didn't do any thread id. A thread ID has been a very convenient part of gmail's extensions, most importantly to fetch and display a thread without having to engage with the entire mailbox, which can be very, very big on gmail. > * bytestring 1..255 for everything? I bet the cyrus implementation doesn't use that. It uses something that needs no quoting anywhere. Right? Specs that say "anything goes" and are implemented with a nice restricted repertoire are trouble magnets. Clients will use e.g. JSON and forget to quote, and later when the first "\/ comes along, there's a bug. Needless. Better to specify a repertoire that's reasonably well filled by running code. We've discussed this before and you know my opinion, but really, anything is okay so long as the the spec is mostly tested by running code. > * more "prior art" discussion for X-GM work? Doesn't matter IMO. Arnt From nobody Tue Mar 20 04:56:22 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 D608D126DC2 for ; Tue, 20 Mar 2018 04:56:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=KYWfV9+k; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PlmZekaM 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 3XDRCZvW7Hfv for ; Tue, 20 Mar 2018 04:56:17 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEBD6126D85 for ; Tue, 20 Mar 2018 04:56:16 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3675521679; Tue, 20 Mar 2018 07:56:16 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Tue, 20 Mar 2018 07:56:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4vXO/h 4MpImPtKY2b40jmKCcpI2U6ZnTVyzW2XPLkOA=; b=KYWfV9+kTC2EROJepoxh9g zrkG8wJiLiMDQwQyBdqdtd6Lx4UoNB60PCqUmQA7JfItFSobyb+oynm6E1h2gLAE JyAo3V/mF331TG19CXE+QRkiyJOyyrFm9RvGpklujMpO5hQPAKkGsJ3mDuZQHmdc mdGgb+iowgndAUNFdKNhULVWS1FEqeIFpR+PrUBCG8blCqb+HhVzc3nbMwIi4v9a uFCcN8/cZFdMM5wtMU4JYPI9w7XxgxMi65t7L2KPVaST6HNr+TMXD3kQ12qixCGh nb/aEzpn+o9mEYuLF+Q96mF2i7XKKwb6P5un3KW5jjHJTZ/rD2I7BPRMpCGDv2ww == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4vXO/h 4MpImPtKY2b40jmKCcpI2U6ZnTVyzW2XPLkOA=; b=PlmZekaMXnnEs0oJoDLVwy VpiT6U9YWdCIImJ6IpCRhfmjw7UzzZeRkyVB7/q4/7QplguAJHNUT0vKnZQJk1Br Cy0L9ulvnqx47hxRDqQRXKiSRBkcBg0sBj0mUpTZsrFQJ1uzj0UyH5e9WZ8LDOZ2 mgBj11QBt782f2mogCamLBxKREPlS+FNI5UDfGOaEPpcJjIZpw8mtH/B1nIuGd8X mT5wQ1pBxToTu8pmc3RbwNkRHBd7lhzKyOA9gGkaDbW1xH5npZKC2mBVkhUUoo+d lUSaXkCXS6pRkbMniCfCXoyXFHjNopkiWCa49M2cVfXAMHsYGJCZVMRpuD9C00JA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 03B81621BF; Tue, 20 Mar 2018 07:56:15 -0400 (EDT) Message-Id: <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> From: Bron Gondwana To: Arnt Gulbrandsen Cc: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152154697529664721" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> In-Reply-To: Date: Tue, 20 Mar 2018 22:56:15 +1100 Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 11:56:21 -0000 This is a multi-part message in MIME format. --_----------=_152154697529664721 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Tue, 20 Mar 2018, at 21:45, Arnt Gulbrandsen wrote: > Bron Gondwana writes: >> https://datatracker.ietf.org/doc/draft-gondwana-imap-uniqueid/ >> >> This is a pretty rough first draft, so the wording will need >> some smithing, but the implementation looks good in Cyrus IMAP: > > I see you didn't do any thread id. Yes, THRID is exactly a thread id. > A thread ID has been a very convenient part of gmail's > extensions, most> importantly to fetch and display a thread without having to engage > with the> entire mailbox, which can be very, very big on gmail. > >> * bytestring 1..255 for everything? > > I bet the cyrus implementation doesn't use that. It uses > something that> needs no quoting anywhere. Right? Kinda. Cyrus uses a guid for mailbox uniqueid which may need quoting. The emailid from jmap and thread id I've copied exactly into the Cyrus implementation of this draft. In particular, the message id is the first 24 characters of the hex representation of the full digest.sha1, and the thread id is the hex of a 64 bit number which is derived from the sha1 of the first seen message in that thread. Yes, I do plan to move away from sha1 eventually! > Specs that say "anything goes" and are implemented with a nice > restricted> repertoire are trouble magnets. Clients will use e.g. JSON and > forget to> quote, and later when the first "\/ comes along, there's a bug. > Needless.> > Better to specify a repertoire that's reasonably well filled by > running> code. We've discussed this before and you know my opinion, but really,> anything is okay so long as the the spec is mostly tested by > running code. Something that can be an atom would be nice for sure. Easy enough to convert Cyrus over, not sure about everything else. We'll have to bring jmap along with whatever it is, because compatibility is important. >> * more "prior art" discussion for X-GM work? > > Doesn't matter IMO. > > Arnt > > _________________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152154697529664721 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"



On Tue, 20 Mar 2018, at 21:45, Arnt Gulbrandsen wrote:
Bron Gondwana writes:

This is a pretty rough first draft, so the wording will need
some smithing, but the implementation looks good in Cyrus IMAP:

I see you didn't do any thread id.

Yes, THRID is exactly a thread id.

A thread ID has been a very convenient part of gmail's extensions, most
importantly to fetch and display a thread without having to engage with the
entire mailbox, which can be very, very big on gmail.

* bytestring 1..255 for everything?

I bet the cyrus implementation doesn't use that. It uses something that
needs no quoting anywhere. Right?

Kinda. Cyrus uses a guid for mailbox uniqueid which may need quoting. The emailid from jmap and thread id I've copied exactly into the Cyrus implementation of this draft.

In particular, the message id is the first 24 characters of the hex representation of the full digest.sha1, and the thread id is the hex of a 64 bit number which is derived from the sha1 of the first seen message in that thread.

Yes, I do plan to move away from sha1 eventually!

Specs that say "anything goes" and are implemented with a nice restricted
repertoire are trouble magnets. Clients will use e.g. JSON and forget to
quote, and later when the first "\/ comes along, there's a bug. Needless.

Better to specify a repertoire that's reasonably well filled by running
code. We've discussed this before and you know my opinion, but really,
anything is okay so long as the the spec is mostly tested by running code.

Something that can be an atom would be nice for sure. Easy enough to convert Cyrus over, not sure about everything else.  We'll have to bring jmap along with whatever it is, because compatibility is important.

* more "prior art" discussion for X-GM work?

Doesn't matter IMO.

Arnt

_______________________________________________
Extra mailing list

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

--_----------=_152154697529664721-- From nobody Tue Mar 20 05:10:52 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 21B1D126D85 for ; Tue, 20 Mar 2018 05:10:51 -0700 (PDT) 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 KWia3M-UqMaf for ; Tue, 20 Mar 2018 05:10:50 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D0751200B9 for ; Tue, 20 Mar 2018 05:10:50 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4B660FA00AD; Tue, 20 Mar 2018 12:10:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521547847; bh=4b4+LLnIGiE//kfHOh68LjwbNzLiX6qxhWEqZf3YGfA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ORR0r+19SqfT5PoYcrLvRpOpbuqFg8pCDWV8Ft6yf7SBclOSZjFJXcn7leUwCKjJN lwUasXA4/3EAd/pHiG+DXBbA9ea4zJYe2myWoIiYoVEO5Bvnzye/unuPNesdMP1K9O 6AA8NdJ+8Urq5heW+j/G/nkgKOYRO7KnOFNqSOV0= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521547846-12902-31493/11/1; Tue, 20 Mar 2018 12:10:46 +0000 From: Arnt Gulbrandsen To: Bron Gondwana Cc: extra@ietf.org Date: Tue, 20 Mar 2018 12:10:45 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> In-Reply-To: <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 12:10:51 -0000 Just one comment. Bron Gondwana writes: > Yes, THRID is exactly a thread id. Optional, ie. not reliably there. Gmail's is reliable. You write one path of code and that works and is fast, and that's what makes it convenient. Arnt From nobody Tue Mar 20 05:23:20 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 AD405126D85 for ; Tue, 20 Mar 2018 05:23:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=UZ2S+y8q; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CTqazhFi 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 krTZHNhRU1LR for ; Tue, 20 Mar 2018 05:23:17 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E86B124234 for ; Tue, 20 Mar 2018 05:23:17 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 79D1520CEB; Tue, 20 Mar 2018 08:23:16 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Tue, 20 Mar 2018 08:23:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=eVSKRs 1xK7xsRXXd+SePbY1RuAqqglgfNXtwFC6dV4E=; b=UZ2S+y8qMtJiXQbYNF6tQW YvuJo9/hHNraLke4DgrVfbzcrb+7DyRtc8Qnet50/iHzWq3sk4FJAm1itfZIvx1e TDUR350ceYOxW1xg6WSMTIUFh+mwFCfFlYPSlRygt+cStB/S3XSh3RyOYfznjtG0 m6kKy3pdM8zbA88VdNB8n2U5+EmCIs288dtf/tFhSFXyYAMDV5YeLE8xcS4GqMpx efaLvxIuBpetAC7IuwwkAinQY37fzCHZQ1So2leXYTmW2tjV0AUa8+fpbIEn/+eJ oinb/UwJj0oI3MT2L2/Yra0TOFJBadfkkMuRejfOri/2XiNE9w/ujz7LEp0F2RdA == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=eVSKRs 1xK7xsRXXd+SePbY1RuAqqglgfNXtwFC6dV4E=; b=CTqazhFiz78kFBB8DtH8u1 yYT52bzzy2WYro5ARMOsl7K58c3gZe86LkYHthrEq0a9EQ9Ejrojs9q/3tafkjzo yToQfSffC97b8OcSd7q0qjWWxFEmKqjpVbZfzgST7dIws8vFBI+Stc9GMxxS2kmL KbaG92Ooc/niT+mvvYU+Gif8SGxKMVn31y+kUI/ZAyEmdz1oeBhE6h1HSXrqfYWh /Q3EAzuetrKxFuqtZUwNBBqpg3V2x+u2fM2I4268gtR1zXeYhUMzpot466BGtruJ cIIPx4XS2ipGU4JxC3TRLr/VHYDz3dwNQEgQTeVoJvB9g+6f0eFv5VZAAsX6LNnQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 51D58621DA; Tue, 20 Mar 2018 08:23:16 -0400 (EDT) Message-Id: <1521548596.2977027.1309502344.0BBC69AB@webmail.messagingengine.com> From: Bron Gondwana To: Arnt Gulbrandsen Cc: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152154859629770272" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Tue, 20 Mar 2018 23:23:16 +1100 In-Reply-To: <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 12:23:19 -0000 This is a multi-part message in MIME format. --_----------=_152154859629770272 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Fallback is to treat each message as its own thread. I could also define it to return the msgid if the server doesn't support threading, but then the client can't know. I guess that's a legit question to the list though, what would people prefer as the behaviour for a server which doesn't have thread data stored? I've been very careful to make this standard implementable in a way that doesn't need any additional data stored in the server, albeit with reduced usefulness in that case. Bron. On Tue, 20 Mar 2018, at 23:10, Arnt Gulbrandsen wrote: > Just one comment. > > Bron Gondwana writes: >> Yes, THRID is exactly a thread id. > > Optional, ie. not reliably there. Gmail's is reliable. You write > one path> of code and that works and is fast, and that's what makes it > convenient.> > Arnt > > _________________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152154859629770272 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Fallback is to treat each message as its own thread. I could also define it to return the msgid if the server doesn't support threading, but then the client can't know.

I guess that's a legit question to the list though, what would people prefer as the behaviour for a server which doesn't have thread data stored?

I've been very careful to make this standard implementable in a way that doesn't need any additional data stored in the server, albeit with reduced usefulness in that case.

Bron.


On Tue, 20 Mar 2018, at 23:10, Arnt Gulbrandsen wrote:
Just one comment.

Bron Gondwana writes:
Yes, THRID is exactly a thread id.

Optional, ie. not reliably there. Gmail's is reliable. You write one path
of code and that works and is fast, and that's what makes it convenient.

Arnt

_______________________________________________
Extra mailing list

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

--_----------=_152154859629770272-- From nobody Tue Mar 20 05:40:34 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 255D7127078 for ; Tue, 20 Mar 2018 05:40:33 -0700 (PDT) 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 jSEDTBt_5T5Z for ; Tue, 20 Mar 2018 05:40:32 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D58E5126DED for ; Tue, 20 Mar 2018 05:40:31 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4D784FA00AD; Tue, 20 Mar 2018 12:40:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521549630; bh=eiBmZh5SPpPhQTCXUDMuTHq0vCVNam5RyxYYNylRcDE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=N7V/d9O9Fucs6YwzdBzLyRzC1okGN8lhkZRWxcxLloYechppB/ApwA/3RW7zpvTX8 Uowvp3ewIwXNPxW6Z9uK48W99P7bj/rekj6eV6N1JEwkK2P1rXGk3o7a2FWMieaYYs uwCPeftwb0mJEfTTo+wfyQPVDkFbAbe7FySiPYME= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521549629-12902-31493/11/2; Tue, 20 Mar 2018 12:40:29 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Tue, 20 Mar 2018 12:40:29 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: <6f2ec9f6-5b55-47cd-ba76-0b6710f3a987@gulbrandsen.priv.no> In-Reply-To: <1521548596.2977027.1309502344.0BBC69AB@webmail.messagingengine.com> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> <1521548596.2977027.1309502344.0BBC69AB@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 12:40:33 -0000 Bron Gondwana writes: > Fallback is to treat each message as its own thread. I could > also define it to return the msgid if the server doesn't support > threading, but then the client can't know. > > I guess that's a legit question to the list though, what would > people prefer as the behaviour for a server which doesn't have > thread data stored? You could get both by saying that if a message's own ID and its thread ID are the same, that means the message cannot be threaded by the server, either because the server doesn't thread, because the message lacks a message-id, or for some other reason. This permits the clients that prefer simplicity use one code path, while clients that want to can detect the situation. The downside is that a compliant server must somehow make sure that its thread and message IDs don't clash. Arnt From nobody Tue Mar 20 06:40:10 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 1470A126DED for ; Tue, 20 Mar 2018 06:40:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=E5sPWZK3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=mAYOWEVQ 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 T7qzFo5kfJWi for ; Tue, 20 Mar 2018 06:40:02 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80055124B17 for ; Tue, 20 Mar 2018 06:40:02 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id EE6042086D for ; Tue, 20 Mar 2018 09:40:01 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute6.internal (MEProxy); Tue, 20 Mar 2018 09:40:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Dgt5LMdS+tWzilHr4 F/+TuCUWXs2j8nkiW6td7k3M1w=; b=E5sPWZK3N+HjJHR4+nF8KHIu0zU7CiCUA KiQ+8y9yHlXWWowYKRCAHHa+ICH1b8QvrxbVzOe79pM6N7IGwQqqdh4gUk7Cy7QW Yxvh5zzQ/1TZF6m5x168D8F+3RSUslCwxYG8xiTNNhkbI0DgW0yi+/mmcQH8x+UK i3t1duqn4E5DgQfzokHvLsQsHOz0PVWx+ejyUaZoDRSTrvRp2wggbtoZ6LguVBGb Y2qcRjBlNFj/6l2Va//Oqwj3N8Wjxeo8qW/KH5Z7XFUnfPK7+STUa9gcb5CXR0bQ 8GA7iEmx329PsNnZeBJF36KCwbYxhAmnnf96CEqjF5L9fNVICY6gg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Dgt5LM dS+tWzilHr4F/+TuCUWXs2j8nkiW6td7k3M1w=; b=mAYOWEVQKWAuRwcA0UjVSK aHYDXVGZA3S1Gf4yXyG/iJ1RPMTsh+D454cy6e5vi43d0JqlosPd9FUVtzBwENmm 8gvJpwW1lnaLRuJ1J5cxwjC1uecOc2GQT6mNHo+Z2VrziT+uG4MCWjXKPvsNF3Eq guj6KdDkkPht/10OEeveZJ1cA23Ef2k3H8U8faAhVBZ3Dz8FjJtaw189Qk9JESk/ zpKb3b70SuDnER+7mnZUhnpCEmJHsRKU/grQZiUwccOx5Sg3EG+IjlY6T3l0A5KN l9x6m4deCYnW+48ubH/2AotzTfwZeZ9worGRI4yoXgf3wh5aTCa6JyeHf71l1RuA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id C9C8094127; Tue, 20 Mar 2018 09:40:01 -0400 (EDT) Message-Id: <1521553201.4100432.1309592480.73E523D6@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152155320141004320" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba In-Reply-To: <6f2ec9f6-5b55-47cd-ba76-0b6710f3a987@gulbrandsen.priv.no> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> <1521548596.2977027.1309502344.0BBC69AB@webmail.messagingengine.com> <6f2ec9f6-5b55-47cd-ba76-0b6710f3a987@gulbrandsen.priv.no> Date: Wed, 21 Mar 2018 00:40:01 +1100 Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 13:40:09 -0000 This is a multi-part message in MIME format. --_----------=_152155320141004320 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Tue, 20 Mar 2018, at 23:40, Arnt Gulbrandsen wrote: > Bron Gondwana writes: >> Fallback is to treat each message as its own thread. I could >> also define it to return the msgid if the server doesn't support >> threading, but then the client can't know. >> >> I guess that's a legit question to the list though, what would >> people prefer as the behaviour for a server which doesn't have >> thread data stored? > > You could get both by saying that if a message's own ID and its > thread ID> are the same, that means the message cannot be threaded by the server,> either because the server doesn't thread, because the message lacks a> message-id, or for some other reason. > > This permits the clients that prefer simplicity use one code > path, while> clients that want to can detect the situation. The downside is that a> compliant server must somehow make sure that its thread and > message IDs> don't clash. Sounds like a possibility. I'll bring that up on Thursday, and propose the alternatives to the list in a separate message afterwards to collect opinions. Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152155320141004320 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Tue, 20 Mar 2018, at 23:40, Arnt Gulbrandsen wrote:
Bron Gondwana writes:
Fallback is to treat each message as its own thread. I could
also define it to return the msgid if the server doesn't support
threading, but then the client can't know.

I guess that's a legit question to the list though, what would
people prefer as the behaviour for a server which doesn't have
thread data stored?

You could get both by saying that if a message's own ID and its thread ID
are the same, that means the message cannot be threaded by the server,
either because the server doesn't thread, because the message lacks a
message-id, or for some other reason.

This permits the clients that prefer simplicity use one code path, while
clients that want to can detect the situation. The downside is that a
compliant server must somehow make sure that its thread and message IDs
don't clash.

Sounds like a possibility.  I'll bring that up on Thursday, and propose the alternatives to the list in a separate message afterwards to collect opinions.

Bron.


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


--_----------=_152155320141004320-- From nobody Tue Mar 20 10:38: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 A175112D7E4 for ; Tue, 20 Mar 2018 10:38:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.71 X-Spam-Level: X-Spam-Status: No, score=-2.71 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 gQz60aI1-vpM for ; Tue, 20 Mar 2018 10:38:08 -0700 (PDT) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FC43126BF7 for ; Tue, 20 Mar 2018 10:38:08 -0700 (PDT) Received: by mail-it0-x22e.google.com with SMTP id e195-v6so3490766ita.5 for ; Tue, 20 Mar 2018 10:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=491XfI4vhAVWptWaon8FlQxa/fqGDG3cQvBn1JTesN4=; b=L+2Zz/0e+7cztqo4mTWvgpVqyRM1OXCklENnDruhnrJiHvjJsggPnkfbBy5fdI1Zm2 w9VVdR8kE4MTnLsOenNBJVOdH15Mh6Dc/cDK7Ff8knSwRsYdwspuWlE7HuGGMTDfgwMw nNj2vFV9VhA5ZvwgqK7WVZFC6UA8ePjzGkqTqgH36nzZ+/vcjN53TNTup1JYCOy1F3YD ASAiwU+dzq4BU8Spdnu8ppuJoDMz9MnLMVk8jfZ0hmmeyCZe2kHfBxtrbFyMGKZXPifa OOVAuMifOnIV7XWJB/3HP5E0X7fZxFIK4CCzH4GR1t5lUEb55Y+sAAMDVtE4UBF51+YO 6g7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=491XfI4vhAVWptWaon8FlQxa/fqGDG3cQvBn1JTesN4=; b=QgWXtAhG4Kj3ZevhaQ47E8yKWNNQfvs41QnN0N4LX1EhZyg8RqYaBl/KbuYPF+qpHf Wxyw02RXXsVq64rLmHZGGingUJbqGeRuvgFmG64az1soATaDcDyTfVdJ3KbqEmPLXe+g ++i1AfewEpY5cRvBgOsSFhyArMVkXM0k0gZW7Cg71psU/vNOKXC3SsBzJtIXKaRqraSQ XshGH9zOdEvWlyVW7fabrLRWhchxsrE7bcqp89PXgsS430oAZqlUlm+gwmkXEtDzvDlR d7S5ftAQ1veCVGVygVmKC18RtvOlq8BPUaBA2hHGi1me+Yu45x58cUSroo2R491mWkbC gPXQ== X-Gm-Message-State: AElRT7FXwM8DfJ5YdO2HqgggOSiUZHsIrN5dhHi9ohu6OexkghlD5AQD tvQBFRrFuibCezOwk/bZxIg+RI7TsE9gwqdxYjxU X-Google-Smtp-Source: AG47ELsyu4tPcrKJtbQdYQyV3Fui1erESo9mMf0SKUMUvnmou4w1Azo4qLB/H3b4pUWBNL1wYMO0X64X+DYOmGXf4tQ= X-Received: by 2002:a24:3d55:: with SMTP id n82-v6mr582864itn.31.1521567487302; Tue, 20 Mar 2018 10:38:07 -0700 (PDT) MIME-Version: 1.0 References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <1521546975.2966472.1309475312.303AE996@webmail.messagingengine.com> <677391e6-eab9-4113-a402-7ec26dfbd8f8@gulbrandsen.priv.no> <1521548596.2977027.1309502344.0BBC69AB@webmail.messagingengine.com> <6f2ec9f6-5b55-47cd-ba76-0b6710f3a987@gulbrandsen.priv.no> <1521553201.4100432.1309592480.73E523D6@webmail.messagingengine.com> In-Reply-To: <1521553201.4100432.1309592480.73E523D6@webmail.messagingengine.com> From: Brandon Long Date: Tue, 20 Mar 2018 17:37:52 +0000 Message-ID: To: Bron Gondwana Cc: extra@ietf.org Content-Type: multipart/alternative; boundary="00000000000095c0570567db8923" Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 20 Mar 2018 17:38:14 -0000 --00000000000095c0570567db8923 Content-Type: text/plain; charset="UTF-8" Note that in Gmail, the threadid is the msgid of the first message on the thread, so our impl wouldn't be compatible. Brandon On Tue, Mar 20, 2018, 6:40 AM Bron Gondwana wrote: > On Tue, 20 Mar 2018, at 23:40, Arnt Gulbrandsen wrote: > > Bron Gondwana writes: > > Fallback is to treat each message as its own thread. I could > also define it to return the msgid if the server doesn't support > threading, but then the client can't know. > > I guess that's a legit question to the list though, what would > people prefer as the behaviour for a server which doesn't have > thread data stored? > > > You could get both by saying that if a message's own ID and its thread ID > are the same, that means the message cannot be threaded by the server, > either because the server doesn't thread, because the message lacks a > message-id, or for some other reason. > > This permits the clients that prefer simplicity use one code path, while > clients that want to can detect the situation. The downside is that a > compliant server must somehow make sure that its thread and message IDs > don't clash. > > > Sounds like a possibility. I'll bring that up on Thursday, and propose > the alternatives to the list in a separate message afterwards to collect > opinions. > > Bron. > > > -- > Bron Gondwana, CEO, FastMail Pty Ltd > brong@fastmailteam.com > > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > --00000000000095c0570567db8923 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Note that in Gmail, the threadid is the msgid of the firs= t message on the thread, so our impl wouldn't be compatible.

Brandon

On Tue, Mar 20, 2018, 6:40 AM Bron Gondwana <= brong@fastmailteam.com> wr= ote:
On Tue, 20 Mar 2018, at 23:40, Arnt G= ulbrandsen wrote:
Bron Gondwana writes:
Fallback is to treat each message as its own thread. I cou= ld
also define it to return the msgid if the server doesn't support
threading, but then the client can't know.

I guess that's a legit question to the list though, what would
=
people prefer as the behaviour for a server which doesn't have
=
thread data stored?

You could get both by saying that if a message's own ID and its th= read ID
are the same, that means the message cannot be threaded by the server,=
either because the server doesn't thread, because the message lack= s a
message-id, or for some other reason.

This permits the clients that prefer simplicity use one code path, whi= le
clients that want to can detect the situation. The downside is that a<= br>
compliant server must somehow make sure that its thread and message ID= s
don't clash.

Sounds like a possibility.=C2=A0 I'll = bring that up on Thursday, and propose the alternatives to the list in a se= parate message afterwards to collect opinions.

Bron.


--
=C2=A0 Bron Gondwana, CEO, Fa= stMail Pty Ltd
=C2=A0 brong@fastmailteam= .com


_______________________________________________
Extra mailing list
Extr= a@ietf.org
https://www.ietf.org/mailman/listinfo/extra
--00000000000095c0570567db8923-- From nobody Wed Mar 21 07:43:31 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 DAFE112E893 for ; Wed, 21 Mar 2018 07:43:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.012 X-Spam-Level: X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 OtJId5moQxj0 for ; Wed, 21 Mar 2018 07:43:22 -0700 (PDT) Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 82B8612E871 for ; Wed, 21 Mar 2018 07:43:22 -0700 (PDT) Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2LEZkf0145478; Wed, 21 Mar 2018 14:43:17 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=bYTlM35k1PHiNaDUvX86+SvDIPbAtsFgHoxWetGwmDc=; b=CRmu+Yo7qrEXpCIMkW58Uj86liSwpvUNmXuyX5/7igjwvBPwaW8ncA7CdBUWp1rTktQz RNWq7XHHeT//IkgV3/gbfre4c945ayil9xwrm7xJIEW7hY2RIh3ncBUDtvsraXphG8qu a1+Mk+m8XHsRHnEPnWJ0P1CSj7ORT1MVUjjVIWPk86J66tuxodDoercPFOUKKPPZ4VzU tLTg5RL8f/tR7EK4KZRfsJxYjgGg+B0OPl0FMnzm7ZJZeahBRYRc3Tf0/sewmJQn2B85 drXjtqTiVK6b0J53DWUWXDNRdYwBOqDNVu4fZ0ibFqdKT7xkv6eGU7HI7EvtpTiiodiw 6w== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp2120.oracle.com with ESMTP id 2gus9ug1mj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 14:43:17 +0000 Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w2LEhHk0023219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 14:43:17 GMT Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2LEhHnW023967; Wed, 21 Mar 2018 14:43:17 GMT Received: from [31.133.145.111] (/31.133.145.111) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 21 Mar 2018 07:43:16 -0700 From: "Chris Newman" To: "Bron Gondwana" Cc: extra@ietf.org Date: Wed, 21 Mar 2018 14:43:01 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: In-Reply-To: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8838 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=971 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 14:43:30 -0000 We already have a protocol element called "unique identifer" in base-spec IMAP. Adding a new protocol element called "UNIQUEID" with different semantics from "unique identifier" is confusing. I suggest FOLDERID or MAILBOXID as alternatives that are less confusing. FYI, we've implemented this protocol element (right now it's called VENDOR.ORACLE-FOLDERID and the argument is an integer). Adding a new IMAP protocol element called "MSGID" with different semantics from the existing RFC 5322 protocol element "message id" is confusing. I suggest EID or EMAILID as an alternative. I'm not sure THRID is a good name. It looks a lot like a misspelling of THIRD which may make the protocol harder to read. I suggest either TID or THREADID as alternatives. The specification needs ABNF. The specification does not follow the syntax model in RFC 4466 for STATUS. You would have to make the folder id an integer or put an extra layer of () around the folderid string to follow that syntax model. I'm not convinced it's important to follow the RFC 4466 syntax model for STATUS, but I thought I'd point out the issue so it can be discussed. Other than those issues, I support this proposal and am interested in implementing the parts of it we have not already implemented (EID & THRID). Our implementation also has a VENDOR.ORACLE-FOLDERMODSEQ status item. This is updated when mailbox metadata (RFC 5464) changes. Please consider if that feature would be a useful part of this feature bundle. The two status items (folder id & folder modseq) make it easier to build a stateless activesync gateway to IMAP. - Chris From nobody Wed Mar 21 08:45:28 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 0E393126D3F for ; Wed, 21 Mar 2018 08:45:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=Xcyru/tm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hKAtftW7 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 0SQsox2bboRt for ; Wed, 21 Mar 2018 08:45:25 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6FC9124B18 for ; Wed, 21 Mar 2018 08:45:25 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 173CE211A9 for ; Wed, 21 Mar 2018 11:45:25 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Wed, 21 Mar 2018 11:45:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=A3qZo+37XpcjgxJwx SYHz3yMntDpo5kSQKJ8kldOlHc=; b=Xcyru/tmVbP0UImomPEPHsuSPlFu4ufaE PVjBqq8+DJ5x9Cqt3zpEk3x7YQRmAXI4bz4GXG0afVSJ8jmuZjcN1LMSCnx9tgpM F/9UozppgS8CscM9794D4hw20bscDZb8YuGknc2cs/lCDqWFEA+4tpZVQsxEaJ9Y A7L5+gHujWDx3FiMRwGC9Ou32mRn0jrY+2HLW8jCICYMiU0LBORMDKdQpu62oNEI BtukCN8+uVHDYYivkOdmH9Lsm6lF8RAuVIiCOdwf1HqcIO/lKGE7fkt/w8hVEZec HA2+oS/DF8BMFgWd3xZhabTr0Y4NmQ18T/SgQ2gdVd8EZYT1+sB6Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=A3qZo+ 37XpcjgxJwxSYHz3yMntDpo5kSQKJ8kldOlHc=; b=hKAtftW7+H0A3AkAhoSNNk x+aKLNTSCxgylMNy/wLGJavwUSfAC73DUwYIKS0ga+ZlYAsqAL8yfbGfoL+i9h+e 8Mt0hoDYB/33PFY456b/9kuixD2Cw9vtTQr/yrD7MJdXqXgdcmKaLU64IEv/I2L/ abB4mG+zIhljvwD27YqJ4fXDI1jOko9q7SZNTi6YZEfEC0LnL6DTxuUkNYLp9OAJ 25WTfF2U59MfhE30fbEYp3V7L8cMVh7/rY/xIEqeEqMNxnOoV1JaMb1LW/JLIT8c COOj2jhkA/lrZ9uW/ubt6PVsXPXiprEaKXeNt6qjfmhApUNTBsL+dRveMSchMI/w == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id E3869BA43B; Wed, 21 Mar 2018 11:45:24 -0400 (EDT) Message-Id: <1521647124.356565.1311125216.5A32B3F3@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_15216471243565655" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Thu, 22 Mar 2018 02:45:24 +1100 In-Reply-To: References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 15:45:28 -0000 This is a multi-part message in MIME format. --_----------=_15216471243565655 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Thu, 22 Mar 2018, at 01:43, Chris Newman wrote: > We already have a protocol element called "unique identifer" in > base-spec IMAP. Adding a new protocol element called "UNIQUEID" with > different semantics from "unique identifier" is confusing. I suggest > FOLDERID or MAILBOXID as alternatives that are less confusing. FYI, > we've implemented this protocol element (right now it's called > VENDOR.ORACLE-FOLDERID and the argument is an integer). I'm happy with MAILBOXID to be compatible with JMAP. In Cyrus it's a UUID. > Adding a new IMAP protocol element called "MSGID" with different > semantics from the existing RFC 5322 protocol element "message id" is> confusing. I suggest EID or EMAILID as an alternative. Let's go with EMAILID to be compatible. > I'm not sure THRID is a good name. It looks a lot like a > misspelling of> THIRD which may make the protocol harder to read. I suggest either TID> or THREADID as alternatives. Likewise THREADID. > The specification needs ABNF. Yes, I'll get there! > The specification does not follow the syntax model in RFC 4466 for > STATUS. You would have to make the folder id an integer or put > an extra> layer of () around the folderid string to follow that syntax > model. I'm> not convinced it's important to follow the RFC 4466 syntax model for > STATUS, but I thought I'd point out the issue so it can be discussed. I'm happy to get guidance from the group on this. Probably depends what deployed parsers are doing. > Other than those issues, I support this proposal and am interested in> implementing the parts of it we have not already implemented (EID & > THRID). > > Our implementation also has a VENDOR.ORACLE-FOLDERMODSEQ status item.> This is updated when mailbox metadata (RFC 5464) changes. Please > consider if that feature would be a useful part of this feature > bundle.> The two status items (folder id & folder modseq) make it easier > to build> a stateless activesync gateway to IMAP. Tell me more about this and how it's semantically different from HIGHESTMODSEQ. We have something similar in cyrus (mbentry->modseq) which isn't used for anything yet, but is planned to be used for replication. And of course we'll probably be using it for JMAP to know that only counts have changed. However - I wouldn't include that in THIS specification. This specification is about things which don't change! Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_15216471243565655 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"

On Thu, 22 Mar 2018, at 01:43, Chris Newman wrote:
We already have a protocol element called "unique identifer" in
base-spec IMAP. Adding a new protocol element called "UNIQUEID" with
different semantics from "unique identifier" is confusing. I suggest
FOLDERID or MAILBOXID as alternatives that are less confusing. FYI,
we've implemented this protocol element (right now it's called
VENDOR.ORACLE-FOLDERID and the argument is an integer).

I'm happy with MAILBOXID to be compatible with JMAP.  In Cyrus it's a UUID.

Adding a new IMAP protocol element called "MSGID" with different
semantics from the existing RFC 5322 protocol element "message id" is
confusing. I suggest EID or EMAILID as an alternative.

Let's go with EMAILID to be compatible.

I'm not sure THRID is a good name. It looks a lot like a misspelling of
THIRD which may make the protocol harder to read. I suggest either TID
or THREADID as alternatives.

Likewise THREADID.

The specification needs ABNF.

Yes, I'll get there! 

The specification does not follow the syntax model in RFC 4466 for
STATUS. You would have to make the folder id an integer or put an extra
layer of () around the folderid string to follow that syntax model. I'm
not convinced it's important to follow the RFC 4466 syntax model for
STATUS, but I thought I'd point out the issue so it can be discussed.

I'm happy to get guidance from the group on this.  Probably depends what deployed parsers are doing.

Other than those issues, I support this proposal and am interested in
implementing the parts of it we have not already implemented (EID &
THRID).

Our implementation also has a VENDOR.ORACLE-FOLDERMODSEQ status item.
This is updated when mailbox metadata (RFC 5464) changes. Please
consider if that feature would be a useful part of this feature bundle.
The two status items (folder id & folder modseq) make it easier to build
a stateless activesync gateway to IMAP.

Tell me more about this and how it's semantically different from HIGHESTMODSEQ.  We have something similar in cyrus (mbentry->modseq) which isn't used for anything yet, but is planned to be used for replication.  And of course we'll probably be using it for JMAP to know that only counts have changed.

However - I wouldn't include that in THIS specification.  This specification is about things which don't change!

Bron.

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


--_----------=_15216471243565655-- From nobody Wed Mar 21 09:03: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 6D93E12E043 for ; Wed, 21 Mar 2018 09:03:39 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=t+LgA9VY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iZIzImFo 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 8qHCtTYkDJjl for ; Wed, 21 Mar 2018 09:03:37 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59FD12E041 for ; Wed, 21 Mar 2018 09:03:37 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 061B221180 for ; Wed, 21 Mar 2018 12:03:37 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Wed, 21 Mar 2018 12:03:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=akmT7Lfhe8xkUdGQ0tECKE1FhYjRuX1P0P95d+guj XI=; b=t+LgA9VYAtBN147hILVgM+o0tg8gvOtC8wm6vJAkZ5SGHXpkSG7BE/y+I VhIkX73Q2iKnj1JfDnSAIeGoWRsPCoz3NuxXXR/517IseRabFuMFh4OcJGs4gYN4 hIkIowPddqiiBgneZ9aaVJWCNlyfnagm3uw223JnV0NNaR8JfecU08Zzgkaz9gZR UPsY7v6MdPpuu9UZ/e5HNpmPyqePdv9nPl3rqrUKyE5cMAyybcFynt21earD4AZa zifmTG15ag7l85dg/hts2yVL202IzhzMXP3BaAfa6sdzSJdSEehHZ8clcTy/7YQQ jD/bXv7uZtV2UNq5Pr/ENH/XSEz5g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=akmT7Lfhe8xkUdGQ0tECKE1FhYjRu X1P0P95d+gujXI=; b=iZIzImFo0fci7hZypEsMRVSNUqCmjkrMBu5KkR9YTxQet ZYg1gK7vMdEpyXJYqg4Q8K7KPZmvYb7iiFBl2uRaGOf1vXbB7NCY9OHs7H188/kj YlLuFZfCR+kF6hF4xcLBreU9ytlXzhzJj82ukhe1me0T0f7ZJyhFzY3PDnHfr4Wg +SbaTLb6RXyB8cpM8hqb+fhkUcS01ricipYteQcABSr6668sIoom9UXletHTj5Zc SbeNHAUqbMDrVpc5y/Q6kPgnA8i7Iw63fcnx4GMmbFn2ULyshb1eSODE4uDXN2+R RUO1sL/+Ox8sc9s0qwQD8fc4RTdMI+trl1L4DsTdA== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id CD482BA43B; Wed, 21 Mar 2018 12:03:36 -0400 (EDT) Message-Id: <1521648216.1301135.1311149960.55AFE3E8@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152164821613011352" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Thu, 22 Mar 2018 03:03:36 +1100 Archived-At: Subject: [Extra] UNIQUEID -01 uploaded X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 16:03:39 -0000 This is a multi-part message in MIME format. --_----------=_152164821613011352 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Taking into account Chris's feedback (mostly incorporated) and Arnt's feedback (taken on board, but we'll discuss between both EXTRA and JMAP tomorrow and come to an agreement on ID format for both). https://datatracker.ietf.org/doc/draft-gondwana-imap-uniqueid/ Still TODO ABNF (but there's no point until we decide what the ID format is) Still maybe TODO: STATUS response 4466 format compatibility. Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152164821613011352 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
Taking into account Chris's feedback (mostly incorporated) and Arnt's feedback (taken on board, but we'll discuss between both EXTRA and JMAP tomorrow and come to an agreement on ID format for both).

Still TODO ABNF (but there's no point until we decide what the ID format is)

Still maybe TODO: STATUS response 4466 format compatibility.

Bron.

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


--_----------=_152164821613011352-- From nobody Wed Mar 21 09:35:01 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 1D7AC12E041 for ; Wed, 21 Mar 2018 09:35:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 m5_Qs1PAhUb7 for ; Wed, 21 Mar 2018 09:34:58 -0700 (PDT) Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id D0D1312E046 for ; Wed, 21 Mar 2018 09:34:57 -0700 (PDT) Received: from meili (josefsipek.net [71.174.113.7]) by mail.dovecot.fi (Postfix) with ESMTPSA id 7A3752A6900; Wed, 21 Mar 2018 18:34:55 +0200 (EET) Date: Wed, 21 Mar 2018 12:34:52 -0400 From: Josef 'Jeff' Sipek To: Chris Newman Cc: Bron Gondwana , extra@ietf.org Message-ID: <20180321163451.GB13569@meili> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 16:35:00 -0000 On Wed, Mar 21, 2018 at 14:43:01 +0000, Chris Newman wrote: > We already have a protocol element called "unique identifer" in base-spec > IMAP. Adding a new protocol element called "UNIQUEID" with different > semantics from "unique identifier" is confusing. I suggest FOLDERID or > MAILBOXID as alternatives that are less confusing. 100% agreed. > FYI, we've implemented > this protocol element (right now it's called VENDOR.ORACLE-FOLDERID and the > argument is an integer). FWIW, we have X-GUID in Dovecot: a status inbox (uidvalidity x-guid) * STATUS inbox (UIDVALIDITY 1521206682 X-GUID 704283249ac5ab5ac7190000807e0fe7) a fetch 1 (uid x-guid) * 1 FETCH (UID 1749 X-GUID 90a39608dec8ab5aea330000807e0fe7) I don't think there is a way to get an email's thread-id right now. > Adding a new IMAP protocol element called "MSGID" with different semantics > from the existing RFC 5322 protocol element "message id" is confusing. I > suggest EID or EMAILID as an alternative. > > I'm not sure THRID is a good name. It looks a lot like a misspelling of > THIRD which may make the protocol harder to read. I suggest either TID or > THREADID as alternatives. It took me 4 passes over one of the emails in this thread to notices that it doesn't say THIRD. I think I like EMAILID & THREADID more than the EID/TID. All 3 items (mailbox, mail, and thread ids) are useful, and it's good to see this codified. Jeff. > The specification needs ABNF. > > The specification does not follow the syntax model in RFC 4466 for STATUS. > You would have to make the folder id an integer or put an extra layer of () > around the folderid string to follow that syntax model. I'm not convinced > it's important to follow the RFC 4466 syntax model for STATUS, but I thought > I'd point out the issue so it can be discussed. > > Other than those issues, I support this proposal and am interested in > implementing the parts of it we have not already implemented (EID & THRID). > > Our implementation also has a VENDOR.ORACLE-FOLDERMODSEQ status item. This > is updated when mailbox metadata (RFC 5464) changes. Please consider if that > feature would be a useful part of this feature bundle. The two status items > (folder id & folder modseq) make it easier to build a stateless activesync > gateway to IMAP. > > - Chris > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. - Bjarne Stroustrup From nobody Wed Mar 21 10:19:35 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 7102612E049 for ; Wed, 21 Mar 2018 10:19:33 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=wLuPSAhN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BOjQgbJJ 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 Gawnz695C2Sh for ; Wed, 21 Mar 2018 10:19:30 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B3412751F for ; Wed, 21 Mar 2018 10:19:30 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D1CB2211F4 for ; Wed, 21 Mar 2018 13:19:29 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Wed, 21 Mar 2018 13:19:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UdMSJz9mQLZRU0b50 rUQCEZP/kyN4Sm0q8QZPUftxFo=; b=wLuPSAhNB5SPZV+RrbHKWjI9Nq2Oehh3j AoXP+5ewsH6asn5emec3DhWgKOOPlkdMP0fYkXaF3TCrn3P7pISBP2URXH0epyi1 4uyw8y7EPHw+ZJQOaMxTlvKgf6zUY/hTx4/B6exxkY3xS079pzlhgBH2FYozsjMj B3/SbuT9FlENT2CdIF3fr3mPhGC2RlNLHXO99ATTTacaOhugMN+Trb1N19yDdJ/i C2fUaLEOOdxM7jQpXk2zVM2m0RB5jYNchdHqeIXEFcbX1C39Gm4FopyAZmWZsZ8f iOMz1y4gMr2/4PmgFCX0gtVhd88cKuvfLr5L3jBdBoRD6JEeUePlw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UdMSJz 9mQLZRU0b50rUQCEZP/kyN4Sm0q8QZPUftxFo=; b=BOjQgbJJhGSdLyyHIgyizy cLT4uMVRoZ28/Qa2AKrSuHfmdU2ooBBvOyII8rkLZAYXZhS9dTzXUL+zo2M8wgXh Ex/TEYQt8fwa0LXgikyILpAphhAiPq8e3LCIdhJ8hXAI48UCyz12LCTG9iVkjImk mbXJBIESe1ccv/rvjVFQlrwTAzEwYNsyzWYlO+wImtnOCHgXLE5cVYfJfSd90QLk 8TWLB34kP2bLFlMKcGGigPbyTLSum1spJTZTdrZ2uBQ5a4fVnfRDtwDifiF1DIUp Kz8EUgRpH1in7X65mIKZBC5SsE8RNMQlr+cHpMTj89bJEYfFDDCJoRuDCqUsSlSA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9DC3DBA43B; Wed, 21 Mar 2018 13:19:29 -0400 (EDT) Message-Id: <1521652769.1345216.1311246712.3D76EA26@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152165276913452162" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Thu, 22 Mar 2018 04:19:29 +1100 References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <20180321163451.GB13569@meili> In-Reply-To: <20180321163451.GB13569@meili> Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 17:19:33 -0000 This is a multi-part message in MIME format. --_----------=_152165276913452162 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Thu, 22 Mar 2018, at 03:34, Josef 'Jeff' Sipek wrote: > a status inbox (uidvalidity x-guid) > * STATUS inbox (UIDVALIDITY 1521206682 X-GUID > 704283249ac5ab5ac7190000807e0fe7) Thanks Josef - does this look like an argument in favour of ignoring 4466's grammar? I think maybe it does! You've clearly taken the same path I did of not requiring the STATUS value to be a number or a list... > a fetch 1 (uid x-guid) > * 1 FETCH (UID 1749 X-GUID 90a39608dec8ab5aea330000807e0fe7) Definitely looks like another reason that the choice of string rather than number is right for EMAILID and THREADID (I've already updated the draft) > I don't think there is a way to get an email's thread-id right now. Are you storing some kind of thread correlation key? I only have a pretty old version of the dovecot source lying around on my laptop (from last time I build imaptest from source!) and it looks at a glance like maybe it's building threads from first principles each time. Mostly I'm interested in "if you are, will this spec work for it?". Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152165276913452162 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Thu, 22 Mar 2018, at 03:34, Josef 'Jeff' Sipek wrote:
a status inbox (uidvalidity x-guid)
* STATUS inbox (UIDVALIDITY 1521206682 X-GUID 704283249ac5ab5ac7190000807e0fe7)

Thanks Josef - does this look like an argument in favour of ignoring 4466's grammar?  I think maybe it does!  You've clearly taken the same path I did of not requiring the STATUS value to be a number or a list...

a fetch 1 (uid x-guid)
* 1 FETCH (UID 1749 X-GUID 90a39608dec8ab5aea330000807e0fe7)

Definitely looks like another reason that the choice of string rather than number is right for EMAILID and THREADID (I've already updated the draft)

I don't think there is a way to get an email's thread-id right now.

Are you storing some kind of thread correlation key?  I only have a pretty old version of the dovecot source lying around on my laptop (from last time I build imaptest from source!) and it looks at a glance like maybe it's building threads from first principles each time.

Mostly I'm interested in "if you are, will this spec work for it?".

Cheers,

Bron.

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


--_----------=_152165276913452162-- From nobody Wed Mar 21 13:34:53 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 C345512895E for ; Wed, 21 Mar 2018 13:34:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 jvpdGdD2vX2B for ; Wed, 21 Mar 2018 13:34:50 -0700 (PDT) Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (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 6034C128896 for ; Wed, 21 Mar 2018 13:34:50 -0700 (PDT) Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2LKYedo179215; Wed, 21 Mar 2018 20:34:47 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=y+ZWxqG95gC3WFpSJSIUsWrtIep8xLedLYaP9CtylWg=; b=EL5uN5T3F2q1LxqU1dcxr/giCXzjn+hDTIZbGuX9unCjVlWYZvHl7SOhzRygm2xpUGGs MqKVNAptbzuVUgET5wBUjzgYtc4e6dzq+dOo2a1ckQbn2ZDdq5K5pmTIRaGJ1YVJlgsW 4OwJjbmH5ugkNfs1op62BV5ieOq9fMgp3veUtiLXxFU55fH/AWcI8Xp6u7mr2RE6y7/c Ss2MmmmD3Gd0XbhUd8bxGHeo0Yiyl1bwfz7xKzrVB120Z11V8NNUD+sKCLiPywhd/SiX VG4QY0Y44rFChbqrrrIKIUFNnUKTgtA5GZd55fZHEQpVCg1xW/PvL7eKwCefkfqFlCGs Dw== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2130.oracle.com with ESMTP id 2guxj7800j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 20:34:47 +0000 Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2LKYkCg008219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 20:34:46 GMT Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2LKYjer008845; Wed, 21 Mar 2018 20:34:45 GMT Received: from [10.175.34.34] (/10.175.34.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 21 Mar 2018 13:34:45 -0700 From: "Chris Newman" To: "Bron Gondwana" Cc: extra@ietf.org Date: Wed, 21 Mar 2018 20:34:42 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: <8ADE3C4C-2B3E-40F5-A761-363EE3FCB671@oracle.com> In-Reply-To: <1521652769.1345216.1311246712.3D76EA26@webmail.messagingengine.com> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <20180321163451.GB13569@meili> <1521652769.1345216.1311246712.3D76EA26@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8839 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=855 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 20:34:52 -0000 On 21 Mar 2018, at 17:19, Bron Gondwana wrote: > On Thu, 22 Mar 2018, at 03:34, Josef 'Jeff' Sipek wrote: >> a status inbox (uidvalidity x-guid) >> * STATUS inbox (UIDVALIDITY 1521206682 X-GUID >> 704283249ac5ab5ac7190000807e0fe7) > Thanks Josef - does this look like an argument in favour of ignoring > 4466's grammar? I think maybe it does! You've clearly taken the same > path I did of not requiring the STATUS value to be a number or a > list... One of the authors of RFC 4466 will be at the meeting (and is on this list). Perhaps he recalls why the STATUS grammar was restricted to a number or a list? - Chris From nobody Wed Mar 21 13:46:21 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 2F08D127342 for ; Wed, 21 Mar 2018 13:46:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 wjABtia8SGyZ for ; Wed, 21 Mar 2018 13:46:18 -0700 (PDT) Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 F0AE3124B0A for ; Wed, 21 Mar 2018 13:46:17 -0700 (PDT) Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2LKYbhP052238; Wed, 21 Mar 2018 20:46:14 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=NYGUZYE8VID1YYXDZraIh0aGYM3vxgb+PJX35WYzKZs=; b=EuE2UScuOsX9sibzHdEGBJP+i4tXJ5peNCy5wxkhqAKfFt/dcKl/TzCOtQASRIMVGaRp i7h5f0QLuLXPhprmJFEZTxhz7LtRFnIcNXDbWbRcQBylxztl9fp/I3wy+zr5eQuai0R1 z365tGIgQ5mqZchcNDnVtJPgycWgcAnqTSOlDwrkUKxM6fmRgDxsofh+qCpUMwlp0DFN WMn0wBgFa1QkONxUU6jrYBxvhhNWDOiZQXtt0bpnaZdCYdGqwbdmH/TkreIkqOrthFzp dju0mx1HUFDjo5s7cIjWVtUCCqYwWxJUiRGXmufyXfudtmAmxNhp14U31ScVGiedgg/p KQ== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2120.oracle.com with ESMTP id 2guxj5g1fp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 20:46:14 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2LKkCSL016633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 Mar 2018 20:46:13 GMT Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w2LKkCIV005130; Wed, 21 Mar 2018 20:46:12 GMT Received: from [10.175.34.34] (/10.175.34.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 21 Mar 2018 13:46:12 -0700 From: "Chris Newman" To: "Bron Gondwana" Cc: extra@ietf.org Date: Wed, 21 Mar 2018 20:46:09 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: <9B7D333A-47DA-4D34-ADB5-21C56B4BD135@oracle.com> In-Reply-To: <1521648216.1301135.1311149960.55AFE3E8@webmail.messagingengine.com> References: <1521648216.1301135.1311149960.55AFE3E8@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8839 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=538 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] UNIQUEID -01 uploaded X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 21 Mar 2018 20:46:19 -0000 On 21 Mar 2018, at 16:03, Bron Gondwana wrote: > Still TODO ABNF (but there's no point until we decide what the ID > format is) > Still maybe TODO: STATUS response 4466 format compatibility. Another suggested improvement, show an example of MAILBOXID with LIST-STATUS (RFC 5819). That's a desirable use case. - Chris From nobody Wed Mar 21 17:05:59 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 158DC12D7EA for ; Wed, 21 Mar 2018 17:05:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yY8Lxp6tyk4j for ; Wed, 21 Mar 2018 17:05:56 -0700 (PDT) Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id 4B60E12D72F for ; Wed, 21 Mar 2018 17:05:56 -0700 (PDT) Received: from meili (josefsipek.net [71.174.113.7]) by mail.dovecot.fi (Postfix) with ESMTPSA id C9F522AEF53; Thu, 22 Mar 2018 02:05:53 +0200 (EET) Date: Wed, 21 Mar 2018 20:05:51 -0400 From: Josef 'Jeff' Sipek To: Bron Gondwana Cc: extra@ietf.org Message-ID: <20180322000551.GD13569@meili> References: <1521483054.4007654.1308572672.7A826AE8@webmail.messagingengine.com> <20180321163451.GB13569@meili> <1521652769.1345216.1311246712.3D76EA26@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1521652769.1345216.1311246712.3D76EA26@webmail.messagingengine.com> User-Agent: Mutt/1.8.3 (2017-05-23) Archived-At: Subject: Re: [Extra] New draft: IMAP UNIQUEID X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 00:05:58 -0000 On Thu, Mar 22, 2018 at 04:19:29 +1100, Bron Gondwana wrote: > On Thu, 22 Mar 2018, at 03:34, Josef 'Jeff' Sipek wrote: > > a status inbox (uidvalidity x-guid) > > * STATUS inbox (UIDVALIDITY 1521206682 X-GUID > > 704283249ac5ab5ac7190000807e0fe7) > > Thanks Josef - does this look like an argument in favour of ignoring > 4466's grammar? I think maybe it does! You've clearly taken the same > path I did of not requiring the STATUS value to be a number or a list... Both FETCH X-GUID and STATUS X-GUID have been in Dovecot for almost 10 years, so I suspect that the reasoning behind why it was done this way is long lost. It looks like STATUS X-GUID is the only non-integer STATUS we return. About 4466: I don't really think that's an argument either way. We'll have to add the new names anyway and it is easy enough to add them either way. (At least in Dovecot, for STATUS is it literally a format string change and for FETCH it is only marginally harder.) > > a fetch 1 (uid x-guid) > > * 1 FETCH (UID 1749 X-GUID 90a39608dec8ab5aea330000807e0fe7) > > Definitely looks like another reason that the choice of string rather > than number is right for EMAILID and THREADID (I've already updated > the draft) Yeah, I think a string is less constraining on the implementation. I agree with Arnt that allowing any bytes could lead to ugly escaping issues (especially for IMAP/JMAP gateways), and so I think it would be worth it to restrict the string to something sane - printable ASCII? Obviously, Dovecot would be ok with 0-9 and a-f, but I think that'd be unnecessarily over-constrained. > > I don't think there is a way to get an email's thread-id right now. > > Are you storing some kind of thread correlation key? I only have a > pretty old version of the dovecot source lying around on my laptop (from > last time I build imaptest from source!) and it looks at a glance like > maybe it's building threads from first principles each time. Dovecot keeps a per-mailbox index file (dovecot.index.thread) which maintains a list of CRC32s (or at least that's what the field is called) and indexes into the main index file. Together, I think the two index files contain enough info construct THREAD responses. It isn't always clear how the values flow between the in-memory structures and the index & cache files on disk in Dovecot. It is also possible that there are opportunities to optimize this in Dovecot, most clients seem to ignore THREAD and just build their own threading info. We'll want to revisit threading in Dovecot anyway to figure out how to exactly handle jmap's mailbox-less approach to threads. > Mostly I'm interested in "if you are, will this spec work for it?". I haven't really had a need to understand that code, so I'm not sure how exactly it works. I should look into it more to see what we do about supporting multiple THREAD algos and how that fits the proposed THREADID. Naively, it would seem to be that THREADIDs depend on the threading algo one selects - but in IMAP the threading algo is per THREAD command and not a server config. All I meant by my previous comment was that we don't have an existing X-FOO to FETCH this thread-id. Jeff. -- Ready; T=0.01/0.01 16:31:03 From nobody Thu Mar 22 04:41:26 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 C834612D947 for ; Thu, 22 Mar 2018 04:41:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 DgOxVc9_t7Ro for ; Thu, 22 Mar 2018 04:41:21 -0700 (PDT) Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (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 9080512420B for ; Thu, 22 Mar 2018 04:41:21 -0700 (PDT) Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2MBYecT172647 for ; Thu, 22 Mar 2018 11:41:20 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : subject : date : message-id : mime-version : content-type; s=corp-2017-10-26; bh=e3wMR3XOqMcT3Oqx2rUwwAr7ZKSk2q595uMbDn2Y99k=; b=od/V+daWQsmbEEjjpnI13Lm34VKjARtn/H0ySzTvGEBPKvEJefoK6DGq0t4KkXIkDzm4 OujRJtFoQA9qTMHCP+sOlIv5utPvrl0yRHrLdGhg5hhvZP9MB3oPQdEnV50ple3M/7RN DkQeN9yZWYGdnIQjQVpPtfbY22tpWiczUarvCtKiEuEGOO4M0xiqp2bCuS+9tUmDapTm zHSZQFgtVwwXADMnrPS0k1FP/7kgtzaWAbhZTYIadOL8LolRBb1RcwRcULJvlZpcmAER 1QzmRYpDcNsiJRirHIdbaLJazMTF0yyG+/JxK+qE+my/K/Nrd94G40dgr5GurSh+RLqu UQ== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp2130.oracle.com with ESMTP id 2gvbr3g0xb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Mar 2018 11:41:20 +0000 Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w2MBeqix030056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Mar 2018 11:40:52 GMT Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2MBeqxZ001560 for ; Thu, 22 Mar 2018 11:40:52 GMT Received: from [31.133.142.0] (/31.133.142.0) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Mar 2018 04:40:52 -0700 From: "Chris Newman" To: extra@ietf.org Date: Thu, 22 Mar 2018 11:40:50 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8839 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=558 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 11:41:24 -0000 I've posted revision 2 of UNAUTHENTICATE: https://www.ietf.org/id/draft-newman-imap-unauth-02.txt This has no changes from revision 1. During the EXTRA face to face meeting, I asked for this to be adopted by the WG and there were no objections in the room. Two independent server implementations were noted in the room. I'm not presently aware of any open issues with the proposal. - Chris From nobody Thu Mar 22 05:23:26 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 9EA451242F7 for ; Thu, 22 Mar 2018 05:23:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] 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 3pXtG6Jk_In1 for ; Thu, 22 Mar 2018 05:23:23 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 BB032127873 for ; Thu, 22 Mar 2018 05:23:21 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQFDE3314W00H3V5@mauve.mrochek.com> for extra@ietf.org; Thu, 22 Mar 2018 05:18:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1521721095; bh=1MLfxi8kz+kLmGpleotdfIArUmYQkwWkxVMkKPYHKCQ=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=Zq+RlKhu7ItKAe5OSGMiUGT44jivbw0A0f4SpH89GMGSOuF4TPO90gQ+kH7jwXZmz bsjsaO71gmbZVrbB/nUUE0bIYjspyBU/L61ziOGNKQqn142ndbz5IXr8MMhPMOr5/S EP7XRFVPDrdEYOWD2WeZ70Ps1RgYPFBslsXwaSqk= MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: TEXT/PLAIN; CHARSET=us-ascii; Format=flowed Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQ1J13T4YO00CZTT@mauve.mrochek.com> for extra@ietf.org; Thu, 22 Mar 2018 05:18:11 -0700 (PDT) Cc: extra@ietf.org Message-id: <01QQFDE0M3KC00CZTT@mauve.mrochek.com> Date: Thu, 22 Mar 2018 05:14:19 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Thu, 22 Mar 2018 11:40:50 +0000" <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> To: Chris Newman Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 12:23:25 -0000 Do we want to specify a comparable extension for SUBMIT? I can whip up a draft if we do. Ned > I've posted revision 2 of UNAUTHENTICATE: > https://www.ietf.org/id/draft-newman-imap-unauth-02.txt > This has no changes from revision 1. During the EXTRA face to face > meeting, I asked for this to be adopted by the WG and there were no > objections in the room. Two independent server implementations were > noted in the room. > I'm not presently aware of any open issues with the proposal. > - Chris > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra From nobody Thu Mar 22 05:31:03 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 28D64126CD8 for ; Thu, 22 Mar 2018 05:31:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Nc2nnmbqeD3W for ; Thu, 22 Mar 2018 05:31:00 -0700 (PDT) Received: from smtp-out-2.mxes.net (smtp-out-2.mxes.net [67.222.241.249]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 754261200F1 for ; Thu, 22 Mar 2018 05:31:00 -0700 (PDT) Received: from [192.168.122.118] (ip174-65-80-226.sd.sd.cox.net [174.65.80.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F0BBB27559; Thu, 22 Mar 2018 08:30:58 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) From: Sean Leonard In-Reply-To: <01QQFDE0M3KC00CZTT@mauve.mrochek.com> Date: Thu, 22 Mar 2018 05:30:57 -0700 Cc: Chris Newman , extra@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <9D530A17-23A3-4CE7-8B31-F8C28C7301A2@seantek.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> To: Ned Freed X-Mailer: Apple Mail (2.3445.4.7) Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 12:31:02 -0000 Ned, Sorry but I am not sure what SUBMIT you are referring to. Is this = related to IMAP BURL (RFC 4468)? I also found = draft-kundrat-imap-submit-02 and draft-ietf-lemonade-submit-01 but they = appear to be long-expired. Sean > On Mar 22, 2018, at 5:14 AM, Ned Freed wrote: >=20 > Do we want to specify a comparable extension for SUBMIT? I can whip up = a draft > if we do. >=20 > Ned >=20 >=20 >> I've posted revision 2 of UNAUTHENTICATE: >=20 >> https://www.ietf.org/id/draft-newman-imap-unauth-02.txt >=20 >> This has no changes from revision 1. During the EXTRA face to face >> meeting, I asked for this to be adopted by the WG and there were no >> objections in the room. Two independent server implementations were >> noted in the room. >=20 >> I'm not presently aware of any open issues with the proposal. >=20 >> - Chris >=20 >> _______________________________________________ >> Extra mailing list >> Extra@ietf.org >> https://www.ietf.org/mailman/listinfo/extra >=20 > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra From nobody Thu Mar 22 06:39:49 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 DC3B91272E1 for ; Thu, 22 Mar 2018 06:39:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=hQSspw9T; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cAa6Bi1l 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 F3CPFH69boFZ for ; Thu, 22 Mar 2018 06:39:46 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49B071200C5 for ; Thu, 22 Mar 2018 06:39:46 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B901D20FE0 for ; Thu, 22 Mar 2018 09:39:45 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 09:39:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=JdxsWHSci5Zn0lwrv3trhsP4hPKlfDTVGOZ/v/JLL EQ=; b=hQSspw9TFMouGPUPFHx8HvBhSbQSrUdRWXm72jb7i52aIh5bmoyw76Clk //P5Xeq2lIqWZHOtzD3ZecvP/KftQI9S3ziIRbb8G5DFi/CoRK+uUHlDgzAUAtd0 48g8y0o3J8JxufImTSZ0gdUmpFhwRPQvCmW1k+ftfK9mgbxizAPA+xXfCceOIJVy tBeVARHa6Cyb6OYFvnIJMGuxPlhsF1qZvOCNAIk4X0SHA6Bzm8RubA9gCZ/2vRH6 qKbEeOPBKgNtHIUsIVLMPO9U0mCRkT7iIZWmZIxukzQOrt8w7XfNGXz+4dqQTV+T Zkc1Xb2Eb/vAFVJjoqWIP2qu38uhA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=JdxsWHSci5Zn0lwrv3trhsP4hPKlf DTVGOZ/v/JLLEQ=; b=cAa6Bi1lJ9TAJmR+Mm2We5jCIWxckxWZ/LQfHiKSiAYqA jeHs1PWJd+bk7+/uWKTS2Xxe43uCUhDvy2eLB9c0XZa5lUdbOIADvyqfDnZBgAXZ G1enw/PxQllsPnjlJSKQKQG7bJwmWAmXR/hK6uzeSlcLuyOV5b8z4+3mLLuli5Jq PGcPQNPEsKs8rlfa//M/rC/ZoALPkB5OCYPyGuVX91jGupUVwUYMrc7GE5L/V6Ba mmF8hZVA382kjbGOrZfYblwqgqSc3LhL6DplL4hy+wBFvcsdHQO2429FvXh6DtDT PlEepSGooSJdgyeHBnWrP0I3ByMnZS3YF6yGjx4GQ== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 92B64BA43B; Thu, 22 Mar 2018 09:39:45 -0400 (EDT) Message-Id: <1521725985.1533042.1312286088.4E09BD03@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152172598515330424" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 00:39:45 +1100 Archived-At: Subject: [Extra] Call for adoption: draft-leiba-extra-specialuse-important X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 13:39:48 -0000 This is a multi-part message in MIME format. --_----------=_152172598515330424 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" We had consensus in the meeting at IETF101 to adopt this document, and we expect to take it to WGLC almost immediately (with a small edit regarding registry structure) https://datatracker.ietf.org/doc/draft-leiba-extra-specialuse-important/ If you have any objections, speak before Monday 26th! Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152172598515330424 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
We had consensus in the meeting at IETF101 to adopt this document, and we expect to take it to WGLC almost immediately (with a small edit regarding registry structure)


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

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


--_----------=_152172598515330424-- From nobody Thu Mar 22 06:41:03 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 445B51272E1 for ; Thu, 22 Mar 2018 06:41:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=NiaLKNyr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KVmVDbUH 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 y3o1xHGSRZ7H for ; Thu, 22 Mar 2018 06:40:55 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F53F1200C5 for ; Thu, 22 Mar 2018 06:40:55 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6754F212A3 for ; Thu, 22 Mar 2018 09:40:54 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 09:40:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=72aZnGZygkPeizklaxLlJRb64scWgQ55VS0fTxy1h lc=; b=NiaLKNyrlJl4uzI1gMtB+9QkDZkTU2Wt6q7ZpjJakqK3WNxhFD+wvoOck LVAFV9e5cLB/ptH1jWNM/FIcS/IwChOkojkyfAlbejOew/PmYVjWLVRx0eLzHu+C ANv8BrkyjyhA2drnKvOXFWw5RlsKAJTpcv1c6pE9ARQCx2EvWyC/OnhDXsJMPBsj gglyTQz2d/fPnMyI0G+vyKkvGFkmaGB7s37Sh3OrU14vHrueKqkpEywQtnVlJJxE 75l10QR5oEdVZgijqttdg6nxzoB0Ed6MwmiqsE+i+FThmnXwfmvsOOBjZsAfZ+fW X9Yy00FFRtrA8lMHI0vcH+VsUCjhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=72aZnGZygkPeizklaxLlJRb64scWg Q55VS0fTxy1hlc=; b=KVmVDbUHt31MjWX8s6iOvhW6fHnzagPJZEK9OttX8WeAx ysLPMm8mPmYRdK3ykTN2VYgQ9Q2hDfqet2KxyL1kwGTq6nBHYCvDjjOFv2miWuh8 bq2bDBH3w2gcEdT2y/vbMMybytkvb6Dz8qjP+HCvYl0KZZ1JmfAXsxIv7mNkV5Wq lFoDwmHrydbaYRoiSxifB40gdIRgK2sgqVVFPby4M79MFvWGdRcFyEuwikMMymGd jAqqLZ8tjzAPoZB6V+O/M+7WioLqZmsAvGC7CvhRrXFQr1wgLwzHs1C3q85rqRDu 5FdPYqHJU3+IqsR5prVYHQcJsuE/2lPWw5TYf6+ug== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4420BBA1AE; Thu, 22 Mar 2018 09:40:54 -0400 (EDT) Message-Id: <1521726054.1533925.1312291816.1BEF34C4@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152172605415339250" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 00:40:54 +1100 Archived-At: Subject: [Extra] Call for adoption: draft-gondwana-imap-uniqueid X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 13:41:01 -0000 This is a multi-part message in MIME format. --_----------=_152172605415339250 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" We had consensus in the meeting at IETF101 to adopt this document. There are multiple edits still to be made (see the minutes) but we expect it to progress quite quickly. https://datatracker.ietf.org/doc/draft-gondwana-imap-uniqueid/ If you have any objections, speak before Monday 26th! Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152172605415339250 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
We had consensus in the meeting at IETF101 to adopt this document.  There are multiple edits still to be made (see the minutes) but we expect it to progress quite quickly.


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

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


--_----------=_152172605415339250-- From nobody Thu Mar 22 06:42:29 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 2E94012DA15 for ; Thu, 22 Mar 2018 06:42:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 Mc_xSB8FT-fq for ; Thu, 22 Mar 2018 06:42:20 -0700 (PDT) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 9CA3E12E89D for ; Thu, 22 Mar 2018 06:42:20 -0700 (PDT) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2MDO81U019241 for ; Thu, 22 Mar 2018 13:42:19 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=34LI6BdEsr9RLvwgxJRS3IOQmTFFmPWeimKn6WX4CFw=; b=NZmjpCIp/0YpgkTXnbvNwQ7WIE6uJeNACMCG5YlaJIrUlPlGdf7SJsri38zceVWjttoc bgQg5IBaYK/iS1rQXVxHqdDCtsoo+B0XQ4lKW8u2xQxe/AjpeMSpVE7EI9q7bWranL4+ U+Jx4evcGSDjmWUrgmAQLjUBZyx1or5o5+RMI1yWKow4+SfvO2A62kf7A80innDewfmS Q2wuENoIAQCVfoeY1RoSo29SvYE08QpJQtYKgHQrVgLo0gbr/+byCs+1e6LxNAMaK6AQ w4mER0LWHWKRxCnPHjxSVqTOaewZxnOIVVOg/OfD0ZdZPS4vznRX96neCTye7pCCJISZ 3Q== Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp2130.oracle.com with ESMTP id 2gvdbb839h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Mar 2018 13:42:19 +0000 Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2MDgJCk013767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 22 Mar 2018 13:42:19 GMT Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2MDgJc5010341 for ; Thu, 22 Mar 2018 13:42:19 GMT Received: from [31.133.142.0] (/31.133.142.0) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Mar 2018 06:42:18 -0700 From: "Chris Newman" To: "Ned Freed" Cc: extra@ietf.org Date: Thu, 22 Mar 2018 13:42:13 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: In-Reply-To: <01QQFDE0M3KC00CZTT@mauve.mrochek.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8839 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 13:42:28 -0000 For SMTP Submission, I think it would be more useful to standardize XCLIENT which should include UNAUTHENTICATE functionality. - Chris On 22 Mar 2018, at 12:14, Ned Freed wrote: > Do we want to specify a comparable extension for SUBMIT? I can whip up > a draft > if we do. > > Ned > > >> I've posted revision 2 of UNAUTHENTICATE: > >> https://www.ietf.org/id/draft-newman-imap-unauth-02.txt > >> This has no changes from revision 1. During the EXTRA face to face >> meeting, I asked for this to be adopted by the WG and there were no >> objections in the room. Two independent server implementations were >> noted in the room. > >> I'm not presently aware of any open issues with the proposal. > >> - Chris > >> _______________________________________________ >> Extra mailing list >> Extra@ietf.org >> https://www.ietf.org/mailman/listinfo/extra From nobody Thu Mar 22 06:43:37 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 BFB7F12D86B for ; Thu, 22 Mar 2018 06:43:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=MtjvlW2S; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Md/NIn5G 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 PAYhjj1INg1I for ; Thu, 22 Mar 2018 06:43:35 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BF441200C5 for ; Thu, 22 Mar 2018 06:43:35 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1D34B20FF8 for ; Thu, 22 Mar 2018 09:43:33 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 09:43:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=BJVbGJx1rsJkKWtRkSdTUs6N7GV/khGb/PbgtK+Bh ho=; b=MtjvlW2S2WSmlG5EIxyfRcYTvwCef852KnG/KysPEc/2MQ22wHIsXu4v2 ubgUMbRNV77am/c7b6w4eaW0TnUxjWVW+DmRuUuMoz9BMC9+o6kGa6P3lFFz13f7 bmfFfmZtCujqEpiYWfl7qjk9lPYWLyIAktZ3PF24bTDtObCxr2djLrjUNzlTMkWd xQy3n3VcAQOryqN8w4C+at/3hx7YQ+185Av2BhKv4j3XaEN+YTAiMApO8EK/YGU/ xxFVjEU8H4c2aA+R4F3KwrY223ku5nPQCks/v7DBdFxQM+hqdp5ChTiqZ+fbjCG0 w0bcojQyAXNy0H13r0/TYbjkMlPkg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=BJVbGJx1rsJkKWtRkSdTUs6N7GV/k hGb/PbgtK+Bhho=; b=Md/NIn5GW+aGSfO2cZwE+ar/Bi/fi0qg6aiWs6pvYm0RM soN6BoXzyAfTvYB4exjT8x2QDjvNr7B0qkwlRopE2TSRoOQ8UCS1WsKksFAsfJhC CHizUJZTjEVJbXLEpLnurD9KW16FgLnKSN6UxX3Khsc6KIPfVHbVAu5lVR8E5U3A 3Yfs69RISihMDaFios23JpnL2NavODXuDcs7xUKy+oC1X5OcTyYyryUuN2stHtwK nCoOCElegLw+1ihjald01G1rLUtEo9FZdDnlqlLYEdsYNLixOEb1XaLv04APW5WT QaA4ASUCLjMNvZ1ZEiUU3Gm/O0hguOIY9JvcykCHg== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id E7B56BA43B; Thu, 22 Mar 2018 09:43:32 -0400 (EDT) Message-Id: <1521726212.1534780.1312293528.5114E8E7@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152172621215347800" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 00:43:32 +1100 Archived-At: Subject: [Extra] Call for adoption: draft-melnikov-imap4rev2 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 13:43:37 -0000 This is a multi-part message in MIME format. --_----------=_152172621215347800 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" We had consensus in the meeting at IETF101 to adopt this large amount of work! Barry has volunteered to work with Alexey on the document. We expect much more discussion on the mailing list, and a slow burn for a while as we clear our decks. https://datatracker.ietf.org/doc/draft-melnikov-imap4rev2/ If you have any objections, speak before Monday 26th! Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152172621215347800 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
We had consensus in the meeting at IETF101 to adopt this large amount of work!  Barry has volunteered to work with Alexey on the document.  We expect much more discussion on the mailing list, and a slow burn for a while as we clear our decks.


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

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


--_----------=_152172621215347800-- From nobody Thu Mar 22 06:48:32 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 6A6AB12D86B for ; Thu, 22 Mar 2018 06:48:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=Qg3q8WCO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nFcM9x0r 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 DrFsBzRkIWdc for ; Thu, 22 Mar 2018 06:48:30 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40869124234 for ; Thu, 22 Mar 2018 06:48:30 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A833321402 for ; Thu, 22 Mar 2018 09:48:29 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 09:48:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=sow1kqOgZwO4u+26Q6VZaFmhGkDEYU0ss3WlXzuh1 og=; b=Qg3q8WCOENhFH0ZiugifdVuG49v/VzBCjfhIvwKSsDbyFxVNZDtDAptAX 4jLM62Ka1tfhVYX/uTXgTfSPxuYK7H+Kn4Y33bhn7u7tDguv7labVnIQ7uY4AHoG /n/io1z6eLp69GrQrFuziuOT1t+uNLHYHtvEWedOwT/gNTatBoti9JA/527PJb31 BHgjkcEyUJKczGwqPYiIwRbbMWm17N0+BmP8R6TFlihYCNXVLhgpdfbz5fRDJKQp coDfr73VM7o5AG+lCmHuvE7OgChBTGQc4RL4qvNBtgrSNld0RnpIyFRuqur/0b7s qSFC4eLGoOWfbfHDjQHjKzRJgMItA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=sow1kqOgZwO4u+26Q6VZaFmhGkDEY U0ss3WlXzuh1og=; b=nFcM9x0r02nGnokON4GiMM/3w81yL/iPJsWIMV92QcshD jNHl3GipSZI4FW92yL3n7XfkrTJga9eCPSPogVh0M/jgeNAjRD4tLXkbLkX3hdyH /JPn64MmgGm7Y9+nNw2YwuddWaO+ph1ygGf7KsFaXKenaDXbZn6jXT09LAjiUDRm ARxO+A0suWJfwEn7HNvgvuN10eY/tXflVrUyWVIe2E8Keg93ek4gjvKcmqEcpYvc ILMCtoZ+Cyb1da7z1u0DRMfU5zFheceua76Jo4rj3CrxcXJ4pi8EyYWKuLxiEnc0 3hi9xjm7byqZmnmLFihPMqt8CsIk48k/GhanSVc9w== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 88E45BA43B; Thu, 22 Mar 2018 09:48:29 -0400 (EDT) Message-Id: <1521726509.1536559.1312298792.1D9668DC@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152172650915365596" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 00:48:29 +1100 Archived-At: Subject: [Extra] Call for adoption: draft-newman-imap-unauth X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 13:48:31 -0000 This is a multi-part message in MIME format. --_----------=_152172650915365596 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" We had consensus in the meeting at IETF101 to adopt this draft. We expect it to go immediately to WGLC if accepted, as it's basically complete. https://datatracker.ietf.org/doc/draft-newman-imap-unauth/ If you have any objections, speak before Monday 26th! Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152172650915365596 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
We had consensus in the meeting at IETF101 to adopt this draft.  We expect it to go immediately to WGLC if accepted, as it's basically complete.


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

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


--_----------=_152172650915365596-- From nobody Thu Mar 22 08:04:50 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 E1AD912D890 for ; Thu, 22 Mar 2018 08:04:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=KHOFOhXI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gSriILN2 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 4sauZ9CRMLYN for ; Thu, 22 Mar 2018 08:04:46 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFED1271FD for ; Thu, 22 Mar 2018 08:04:46 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A69E7211F4 for ; Thu, 22 Mar 2018 11:04:45 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 11:04:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=RCU9xDBoUj89P224J 4220bHvwqWPg/SofNxDne/Gjus=; b=KHOFOhXIpnm0YMVGa7lvBEbky+aMJKDun u8Tylj7xmao7yR0Y6Gkn4nQcsgKtZqVLjVExw5dijnJpqpSdBnMyLJGrHthhJ2eE Pv/XMjHbZmUXI6Y3ZfZ+GyJYc3uMNAOjfQg4B3FxukKF6VpgyrqCTzE1mNEqKJFG 0tFU7kytT3C/XRqoUQ2qt8iMRp1SUmN9FOeL1xQTAiOws0FDHbB6BB7/j0/vxawQ 4xqX4rGW0kR0kLevKJjOT34WT1VzR9Pam+uYQss5FuYmSfqnbx+H6nXejBfRtjtu fZa+vANCgNKqfC9bu829GU13ZztCi3STUpOA2cGjdFg+xvmx/JDRw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=RCU9xD BoUj89P224J4220bHvwqWPg/SofNxDne/Gjus=; b=gSriILN2YD39YfqxziOW7m TIDn/iAHNsEwGTfmwxrRxv9jCJe5IDdhh+E74tRXftItTdTpzDhaFuf1G7j9R6BR fAjRceD8OzNVm6PcVMUyPrsWhaZEA5uD47WBM9VtsOsLO8zO33NMF8t3jIAZfa6T Oxj7gO+XmrZHcYv8H+xkVIXJknMJO6zx0K0lRtukZFqVQ8+/cY3dKeq1x3pF+imc wpFHar3hbRi4l3KgP5Vt7pZT+GXoVI+6idNflO7NvezJr2L/txKfAhKRdWFqUXFp fjsEMaPgjl0N35BSa7P1VCNJmmqaDJi0PIDgZmzRO/gbvYizxwPilk+PZuaHXpKA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 79629BA43B; Thu, 22 Mar 2018 11:04:45 -0400 (EDT) Message-Id: <1521731085.1568313.1312401904.067B2AC8@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152173108515683130" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba In-Reply-To: <01QQFDE0M3KC00CZTT@mauve.mrochek.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> Date: Fri, 23 Mar 2018 02:04:45 +1100 Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 15:04:48 -0000 This is a multi-part message in MIME format. --_----------=_152173108515683130 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" I've also worked on a standard for SUBMIT, but I didn't want to open that can of worms just yet! Bron. On Thu, 22 Mar 2018, at 23:14, Ned Freed wrote: > Do we want to specify a comparable extension for SUBMIT? I can whip > up a draft> if we do. > > Ned > > >> I've posted revision 2 of UNAUTHENTICATE: > >> https://www.ietf.org/id/draft-newman-imap-unauth-02.txt > >> This has no changes from revision 1. During the EXTRA face to face >> meeting, I asked for this to be adopted by the WG and there were no >> objections in the room. Two independent server implementations were >> noted in the room. > >> I'm not presently aware of any open issues with the proposal. > >> - Chris > >> _________________________________________________ >> 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 -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152173108515683130 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
I've also worked on a standard for SUBMIT, but I didn't want to open that can of worms just yet!

Bron.


On Thu, 22 Mar 2018, at 23:14, Ned Freed wrote:
Do we want to specify a comparable extension for SUBMIT? I can whip up a draft
if we do.

Ned


I've posted revision 2 of UNAUTHENTICATE:


This has no changes from revision 1. During the EXTRA face to face
meeting, I asked for this to be adopted by the WG and there were no
objections in the room. Two independent server implementations were
noted in the room.

I'm not presently aware of any open issues with the proposal.

- Chris

_______________________________________________
Extra mailing list

_______________________________________________
Extra mailing list

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


--_----------=_152173108515683130-- From nobody Thu Mar 22 08:40:10 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 2E0D5127076 for ; Thu, 22 Mar 2018 08:40:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 xaFG9TMoxEGA for ; Thu, 22 Mar 2018 08:40:08 -0700 (PDT) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 B60A012D943 for ; Thu, 22 Mar 2018 08:39:56 -0700 (PDT) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2MFWhPZ128282; Thu, 22 Mar 2018 15:39:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=HQ7LkkL9wnJ7tvA7RHLowduHKr1s1qvMoewEEPJDrio=; b=njf2MU5TVIDYw61x7wWohJwq3PuS+eAlMZzRjT/dgarE/mEKBKP0N1fr0tgOT53C/xdi PHznWrSaaz+DIs9geTHvetJRZV7pxL1O+t1EZpqZzJEgSanvgIFXPMVfFCZBahrHYpBd Hpz8XBVAPrgdZojuLeWvp9jD7qFa90069KgkweSyt608MCRVX/8Jq0VUm7re3wd4b/Hl Cf0CJBagpCXifT6WxpDJQt4H5sQ45NWUzkJ/PgmdSE6Gw+bMdTGmDSyCYJq+roiJR8TJ gBhJRyaGU54m950ed3D5++KQrfWzCpvVR9O36VrTUu17G+AsDN4HVpG+JL21DLQwoDtc RQ== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2130.oracle.com with ESMTP id 2gvf7p01es-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 22 Mar 2018 15:39:52 +0000 Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2MFdp7w019905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 22 Mar 2018 15:39:51 GMT Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w2MFdpsR007607; Thu, 22 Mar 2018 15:39:51 GMT Received: from [10.175.19.51] (/10.175.19.51) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Mar 2018 08:39:51 -0700 From: "Chris Newman" To: "Bron Gondwana" Cc: extra@ietf.org Date: Thu, 22 Mar 2018 15:39:49 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: <7483414C-F11E-4D14-AD90-D0B63081B303@oracle.com> In-Reply-To: <1521731085.1568313.1312401904.067B2AC8@webmail.messagingengine.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> <1521731085.1568313.1312401904.067B2AC8@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8839 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=710 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 15:40:09 -0000 On 22 Mar 2018, at 15:04, Bron Gondwana wrote: > I've also worked on a standard for SUBMIT, but I didn't want to open > that can of worms just yet! Ned was probably talking about SMTP Submission (RFC 6409). Now there's a mature JMAP submission model to copy, an IMAP submission extension may be less of a can of worms than you think. Of course it does beg the question if JMAP does it do we really need IMAP to do it? - Chris From nobody Thu Mar 22 08:45:46 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 F3D30127076 for ; Thu, 22 Mar 2018 08:45:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=LrKxZ0eE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jadvq+r2 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 PDDqdOBrFWxO for ; Thu, 22 Mar 2018 08:45:43 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 802B7126D05 for ; Thu, 22 Mar 2018 08:45:43 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BD2822133A for ; Thu, 22 Mar 2018 11:45:40 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 11:45:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=X54a/3hjfoitak9CJ Dkm7iFnljFOdibYsZRpodwNwEw=; b=LrKxZ0eENoQDe44nRLGUcKCrT9ZYxd5zN IyZ8V91L4HimMvm1l8Jv+uLwfmBldsWV93j8//3MdsTpZqYbzD07711BdVOJ5ujX B6x6rkYCECRdyjxJdMLj06W3Rrt9NYSVaJHxy1GCyTJCM+bgRAdLYBzg0nmO6E61 V5iYmrdU/vdacswMwGtM83Bi00AH2E9x2NU7ADc9bO4eRt7XZNydFHUVzVXEqmHX EHA+hrrPvmQyskzJjsPtMrxEYLTWVc9nfBFt55WmecuzpYbPCaF+pVyyNYWI4JGK kYk6x7iT9PwrZot3hbpAALoz3y0y3KI3xKRque++9dkrSyWhzVegQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=X54a/3 hjfoitak9CJDkm7iFnljFOdibYsZRpodwNwEw=; b=jadvq+r27BkC9B/cPjPdFJ gYLeSrdmzVnExXMmlJ8XBI3sPV4S0AWW+hcXBeh1mT0b+wnyG8GgkWm7k9a90ZK3 UdnWwt44v0+A74lLiPrxCeICNwImxk9XOMcq0JzaqdCPDZbgUAcolgPU2hUXebFz EARPj+wBDZFfvl8GDD2gLxC1RGbNmukxxWooSJwgHxdopViHkT71hgdOPh01ulxF oq1D6whWQMqUXu2pWdf6p03CkKNKeAS4SRlV/xkReqPNWCAaBC/mdxHJqRcU5r7I M3rcQCRxldXm81yd4UCKkN8douQ+36BQ1/KBe+cK9U/PsEF//kDPLXB2NBRu85OQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 96A4DBA43C; Thu, 22 Mar 2018 11:45:40 -0400 (EDT) Message-Id: <1521733540.1584518.1312458752.0FE733A8@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152173354015845180" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> <1521731085.1568313.1312401904.067B2AC8@webmail.messagingengine.com> <7483414C-F11E-4D14-AD90-D0B63081B303@oracle.com> In-Reply-To: <7483414C-F11E-4D14-AD90-D0B63081B303@oracle.com> Date: Fri, 23 Mar 2018 02:45:40 +1100 Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 15:45:45 -0000 This is a multi-part message in MIME format. --_----------=_152173354015845180 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Fri, 23 Mar 2018, at 02:39, Chris Newman wrote: > On 22 Mar 2018, at 15:04, Bron Gondwana wrote: >> I've also worked on a standard for SUBMIT, but I didn't want to open>> that can of worms just yet! > > Ned was probably talking about SMTP Submission (RFC 6409). > > Now there's a mature JMAP submission model to copy, an IMAP submission> extension may be less of a can of worms than you think. Of course it > does beg the question if JMAP does it do we really need IMAP to do it? Yep, hence my happiness to avoid opening that wormfarm right now! -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152173354015845180 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Fri, 23 Mar 2018, at 02:39, Chris Newman wrote:
On 22 Mar 2018, at 15:04, Bron Gondwana wrote:
I've also worked on a standard for SUBMIT, but I didn't want to open
that can of worms just yet!

Ned was probably talking about SMTP Submission (RFC 6409).

Now there's a mature JMAP submission model to copy, an IMAP submission
extension may be less of a can of worms than you think. Of course it
does beg the question if JMAP does it do we really need IMAP to do it?

Yep, hence my happiness to avoid opening that wormfarm right now!

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


--_----------=_152173354015845180-- From nobody Thu Mar 22 09:14:30 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 1948312D95F for ; Thu, 22 Mar 2018 09:14:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] 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 Qgwn27wh6noS for ; Thu, 22 Mar 2018 09:14:21 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 897BD12DA28 for ; Thu, 22 Mar 2018 09:14:00 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQFLJC4AOG00GYVZ@mauve.mrochek.com> for extra@ietf.org; Thu, 22 Mar 2018 09:11:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1521735092; bh=zMmS2K+N8B/s5g82e33/uJ43RcVWn3LarEKo5FDdDN0=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=hPm3RbCefmQ6a/njRqeEmYkXEsoQbL5zFrweyd65QWiu+lvaLARjyvEIjILGD5DNH qsnRqYsZqST3XvBfGQWAfJwWQYBPcw/0d5Twdce38nCYu/XQbT+wsqhJq1nH948dGD HuFooVNm2jvPffqZlMIbdy8n1Gx5vd3e1IODaE6g= 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 <01QQ1J13T4YO00CZTT@mauve.mrochek.com>; Thu, 22 Mar 2018 09:11:29 -0700 (PDT) Cc: Ned Freed , extra@ietf.org, Chris Newman Message-id: <01QQFLJ9788Y00CZTT@mauve.mrochek.com> Date: Thu, 22 Mar 2018 09:10:08 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Thu, 22 Mar 2018 05:30:57 -0700" <9D530A17-23A3-4CE7-8B31-F8C28C7301A2@seantek.com> References: <9E064A05-598F-40BD-A49B-4723C9EE6937@oracle.com> <01QQFDE0M3KC00CZTT@mauve.mrochek.com> <9D530A17-23A3-4CE7-8B31-F8C28C7301A2@seantek.com> To: Sean Leonard Archived-At: Subject: Re: [Extra] Revised draft: UNAUTHENTICATE X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 16:14:28 -0000 > Sorry but I am not sure what SUBMIT you are referring to. Is this related to > IMAP BURL (RFC 4468)? I also found draft-kundrat-imap-submit-02 and > draft-ietf-lemonade-submit-01 but they appear to be long-expired. RFC 6409, STD 72. Ned > Sean > > On Mar 22, 2018, at 5:14 AM, Ned Freed wrote: > > > > Do we want to specify a comparable extension for SUBMIT? I can whip up a draft > > if we do. > > > > Ned > > > > > >> I've posted revision 2 of UNAUTHENTICATE: > > > >> https://www.ietf.org/id/draft-newman-imap-unauth-02.txt > > > >> This has no changes from revision 1. During the EXTRA face to face > >> meeting, I asked for this to be adopted by the WG and there were no > >> objections in the room. Two independent server implementations were > >> noted in the room. > > > >> I'm not presently aware of any open issues with the proposal. > > > >> - Chris > > > >> _______________________________________________ > >> 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 > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra From nobody Thu Mar 22 11:05:25 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 D801A12711B; Thu, 22 Mar 2018 11:05:22 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , , X-Test-IDTracker: no X-IETF-IDTracker: 6.76.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152174192287.4213.4952442359969998475.idtracker@ietfa.amsl.com> Date: Thu, 22 Mar 2018 11:05:22 -0700 Archived-At: Subject: [Extra] The EXTRA WG has placed draft-leiba-extra-specialuse-important in state "Adopted by a WG" X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 22 Mar 2018 18:05:23 -0000 The EXTRA WG has placed draft-leiba-extra-specialuse-important in state Adopted by a WG (entered by Bron Gondwana) The document is available at https://datatracker.ietf.org/doc/draft-leiba-extra-specialuse-important/ Comment: As discussed on the list earlier and agreed at IETF101. From nobody Thu Mar 22 11:55: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 AAB8D126DC2; Thu, 22 Mar 2018 11:55:58 -0700 (PDT) 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.76.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152174495862.4246.16378556871135130329@ietfa.amsl.com> Date: Thu, 22 Mar 2018 11:55:58 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-list-myrights-02.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 22 Mar 2018 18:55:59 -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 : IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST Authors : Kenneth Murchison Bron Gondwana Filename : draft-ietf-extra-imap-list-myrights-02.txt Pages : 7 Date : 2018-03-22 Abstract: This document defines an extension to the to IMAP LIST command that allows the client to request the set of rights that the logged-in user has been granted on mailboxes, along with other information typically returned by the LIST command. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-list-myrights/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-list-myrights-02 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-list-myrights-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap-list-myrights-02 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 Thu Mar 22 12:11:59 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 32B80126E64 for ; Thu, 22 Mar 2018 12:11:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=bxvAkb5Z; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Zzf6tvSz 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 cRErOG5S2hCL for ; Thu, 22 Mar 2018 12:11:56 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4506126E01 for ; Thu, 22 Mar 2018 12:11:55 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CE52821343 for ; Thu, 22 Mar 2018 15:11:54 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 15:11:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=l7EdtvoamWjbeyth3QuqUgIhQuhEo7WKFoGPnplem qY=; b=bxvAkb5Z4VRsl2h9VDp2USGzFcRjzxkrqxX8wqGNY8hcnHqdSji1gudbo iNu+dHfrjEuCF4BzQzG5fYxCSuT6n84Jha0jQ0hLxnUd4L00f+hmMFsZz0w9/H2T XZNXk3HLFo1nwFF26DbXZxgmgcWa/4qXeo6mo74rj2DVRWKEjIrCjFhJvKJffzcV /ICumzDvGsgqi4efjTOkoMihfPKo5ZddWvVptnzs5FK2uTXY0ExjVo9s6JJGeutz +gtr2Exn2dUQL/+71fSq7lv91OK5cbaK9ifwjvOd9LLwQV2eZgxPNHqadUyqGNKB bZpN8X3z3bBCcBoNlHF4nMZ53d0+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=l7EdtvoamWjbeyth3QuqUgIhQuhEo 7WKFoGPnplemqY=; b=Zzf6tvSzySaDW++toKiJKjlPpdFUc6p0oixrR48WgrkAC fISI+iqQY6uh5VCOqKwYHqYNMlGLX3BhHEujw5R58iQkDMM/NxtkvJf/DimqSODA aWnHlsJ/j4urjKuVOkMA9zQYjIIu1SXgU9S/VQ6+1E0iQMy+cPDo0/gREtczmzDy +HovXnKkuhbmMiXzqxQf7pviwQfaIPLtuRw+5sGYXpfjop+zdE9A+kadZYEpitaT 4mklM94HLwKXnj3+Oif98PGDlsWCu3gOgWOwKpj6fw62yPMhj/YGWYgD7M5kdYhG jfnXBV13b1swjo9sogj2FsZiYLJ2+2sJn2nIx3Cdw== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id AE067BA43B; Thu, 22 Mar 2018 15:11:54 -0400 (EDT) Message-Id: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152174591428430132" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 06:11:54 +1100 Archived-At: Subject: [Extra] Call for opinions: decision about what to do with 64bit X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 19:11:58 -0000 This is a multi-part message in MIME format. --_----------=_152174591428430132 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" This is the thread for discussing what to do with with the 64bit proposed extension. The strongest opinion in the room was to park the document for now. So I'm calling here to see if there's any objections to parking, with a side note that anyone objecting to parking needs to convince people to work on it, and we're pretty busy right now! Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152174591428430132 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
This is the thread for discussing what to do with with the 64bit proposed extension.  The strongest opinion in the room was to park the document for now.

So I'm calling here to see if there's any objections to parking, with a side note that anyone objecting to parking needs to convince people to work on it, and we're pretty busy right now!

Bron.

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


--_----------=_152174591428430132-- From nobody Thu Mar 22 12:56:53 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 361F0124207 for ; Thu, 22 Mar 2018 12:56:51 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 gvfkco3wvfgy for ; Thu, 22 Mar 2018 12:56:49 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A399120726 for ; Thu, 22 Mar 2018 12:56:49 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 0F61BFA00F0; Thu, 22 Mar 2018 19:56:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521748607; bh=cTK2nNJNjGTNRnxGJnL9XcuY+dp7Ip2wYiLKzuFe830=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qZ/DsfTkR5nN2HCaMDxLf5dg7EpDQDJvqMkrDiydFSw2svCQbAAOcaff0rGSDQm4h y0LvnjfuWId0uBN7Dq80HLMg0vIdlxHY63iFqMTiFQ6fHH5Qk1IGGlB+wXsEOQCnYv vjsb8M0K0jfpSdmiugY9rwY6ex2TTvkc0mTzpDp0= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521748606-12902-31493/11/17; Thu, 22 Mar 2018 19:56:46 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Thu, 22 Mar 2018 19:56:46 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: In-Reply-To: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> References: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] Call for opinions: decision about what to do with 64bit X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 19:56:51 -0000 Bron Gondwana writes: > So I'm calling here to see if there's any objections to > parking, with a side note that anyone objecting to parking needs > to convince people to work on it, and we're pretty busy right > now! IMO, larger message sizes are either important enough to include in imap4rev2 or unimportant enough to ignore altogether. Extensions are harmful by default, and need justification for their very existence. I don't bother to argue the point. Arnt From nobody Thu Mar 22 13:48: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 64C8312426E for ; Thu, 22 Mar 2018 13:48:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fiction.net 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 8AdA_asT66Et for ; Thu, 22 Mar 2018 13:48:11 -0700 (PDT) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57383127076 for ; Thu, 22 Mar 2018 13:48:11 -0700 (PDT) Received: by mail-io0-x22e.google.com with SMTP id y128so12619326iod.4 for ; Thu, 22 Mar 2018 13:48:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fiction.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ttJXex2BbQak19o3Mrucs/7QigKwFEnSZAn5Tf70Q8o=; b=A46Tagf1x7HgDHXOWooAEhNdBS71aBrUe1hCsHLxaR7Uc8wUz1l7kxbXRgRG2AiKHi ItIze2JDJIt7mRtq/YRiiF0RUYb1k1RvRdqKICmEUS8za0/75zxzmhtjUV4ZGUD4RW+n AoLG2SLLiGSiO9xF/V1CgHk4kx92WmeClUpWmPJDJJHK8B+2HrQ4jVWARjYNVfVCFU2J mSvTN2jTXbm/oB1NfLROnvuU1G95jaiadf7jCu2IYjXLYnxEsfIlqdRjH5QEjF/GCP76 HlvrFUiKi6uDjnnZzYMMqUA5ILZLJJGgvgNMyhHBur7dp2WxACX2FcyTeK2T3ceSxLNF 221g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ttJXex2BbQak19o3Mrucs/7QigKwFEnSZAn5Tf70Q8o=; b=kYeBtL/JRsu0JYCtD2V7oARyNd76DCYxjmAbVVfMtmPGSXCrugqEWDFjpBnfK4j0X+ 3gsuiFhpk8NSnH08yNoI5AHFhcpG9S0ymye6MHBn7Is2Jjc77H8ykC9sajXt89Ug9v1X zoZA7eYUvWcLwF//aeo2KgGOn5RI6Z1nPRo87J9xyhqLibP8j7TzBzZp6X9Y7H+wXt0L p5ZNVFgX6iRgp0R/X9Jrn4RpO52G6MHsaVObh4dCiWmdU5bB4jU28AlYcIEcBm0fNEDy veYpPIloxAGv3e0XaBGDo79Uvh5l+Q/hNlqPD+ilPkhZAuwssLPxJ/NocQkJ5l1n8reJ V4hA== X-Gm-Message-State: AElRT7H41nvANGsOubGaN5GB2poEax+eLVim2r/g+PNNJU3ggP9g4Eme PC+wIYxXs9aPAyIFAAp6Bag0Oiom X-Google-Smtp-Source: AG47ELv7kaVej9SiqJFX1ig8nK+KfG2VfP3oFugqkme+Tx6EB8NaY5s2FmdO2ByS1OU9/DaK/O3vmQ== X-Received: by 10.107.30.81 with SMTP id e78mr17015099ioe.57.1521751690500; Thu, 22 Mar 2018 13:48:10 -0700 (PDT) Received: from mail-it0-f42.google.com (mail-it0-f42.google.com. [209.85.214.42]) by smtp.gmail.com with ESMTPSA id t127sm3809502iod.48.2018.03.22.13.48.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 13:48:08 -0700 (PDT) Received: by mail-it0-f42.google.com with SMTP id v194-v6so13467itb.0 for ; Thu, 22 Mar 2018 13:48:08 -0700 (PDT) X-Received: by 2002:a24:2b89:: with SMTP id h131-v6mr10823409ita.97.1521751688150; Thu, 22 Mar 2018 13:48:08 -0700 (PDT) MIME-Version: 1.0 References: <1521726212.1534780.1312293528.5114E8E7@webmail.messagingengine.com> In-Reply-To: <1521726212.1534780.1312293528.5114E8E7@webmail.messagingengine.com> From: Brandon Long Date: Thu, 22 Mar 2018 20:47:53 +0000 X-Gmail-Original-Message-ID: Message-ID: To: Bron Gondwana Cc: extra@ietf.org Content-Type: multipart/alternative; boundary="000000000000cfb8d50568066c5a" Archived-At: Subject: Re: [Extra] Call for adoption: draft-melnikov-imap4rev2 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 20:48:14 -0000 --000000000000cfb8d50568066c5a Content-Type: text/plain; charset="UTF-8" A note on a quick review of the changes of that draft, it wants to incorporate LITERAL+... I'd recommend LITERAL- instead for the reasons we added that. Brandon On Thu, Mar 22, 2018 at 6:43 AM Bron Gondwana wrote: > We had consensus in the meeting at IETF101 to adopt this large amount of > work! Barry has volunteered to work with Alexey on the document. We > expect much more discussion on the mailing list, and a slow burn for a > while as we clear our decks. > > https://datatracker.ietf.org/doc/draft-melnikov-imap4rev2/ > > If you have any objections, speak before Monday 26th! > > Cheers, > > Bron. > > -- > Bron Gondwana, CEO, FastMail Pty Ltd > brong@fastmailteam.com > > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > --000000000000cfb8d50568066c5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
A note on a quick review of the changes of that draft, it = wants to incorporate LITERAL+... I'd recommend LITERAL- instead for the= reasons we
added that.

Brandon

On Thu, Mar 22, 2018 at 6:= 43 AM Bron Gondwana <brong@fas= tmailteam.com> wrote:
We had consensus in the meeting at IE= TF101 to adopt this large amount of work!=C2=A0 Barry has volunteered to wo= rk with Alexey on the document.=C2=A0 We expect much more discussion on the= mailing list, and a slow burn for a while as we clear our decks.


If you have any objections, speak before M= onday 26th!

Cheers,

Bron.

--
=C2=A0 Bron Gondwana, CEO, FastMail Pty Ltd


_______________________________________________
Extra mailing list
Extra@ietf.org
https://www.ietf.org/mailman/listinfo/extra
--000000000000cfb8d50568066c5a-- From nobody Thu Mar 22 13:53:21 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 8C0F2126FB3 for ; Thu, 22 Mar 2018 13:53:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=pgFyEX+z; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=im3CZPGc 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 0E_a_6J30cqt for ; Thu, 22 Mar 2018 13:53:15 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9774512426E for ; Thu, 22 Mar 2018 13:53:15 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D564F214C5; Thu, 22 Mar 2018 16:53:14 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute6.internal (MEProxy); Thu, 22 Mar 2018 16:53:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=BxFfib AmU5N5xfoXMRVgidBySIeKnkV4RkrREXj8VZs=; b=pgFyEX+zFjFgPN5+kUpvDp VcAenOvZBZEmMZx5nCBgn2rxNNyjfEFu3l8F4IQPNa7yPjYTz5Wivfm8kXls+R9F j/NCb9g87YBZ7NmibaDIUHwv2N0WtcwDWNLl+YG5/Rd2PpyOx4W3NMTKAazd8DWY 6L88hrdF7fOKkXgrI9wia6/zx2ZxmMe3znVgADI360m+1sMNXX3RO/4TrGMbBOWw VJv4T+zlXSiRCnNQhl9Moyypbt/xWOs2IwnG6QAp6IJ/gx0697cynBXoiQtvs94i ggO8GAD8SlDpv1jeffPng5xATli9v0mcobONoruYE7g5eO65tD/PlgOVlOlJ563g == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=BxFfib AmU5N5xfoXMRVgidBySIeKnkV4RkrREXj8VZs=; b=im3CZPGcTXzxTgtxvD39QL kgZu5mj5PkopAHYqVt89myS6dtfwbb4K/sBSwb1FiDqUww5EoVycRaJThWaUYZSo PNKFPH44/yOY2UrtP3FAiT3/Dlqj3rJOfGGV1qJkoWUfjt3C3RadnI4VipVHd5ex 3B3R/S8XzllHBUqw4eTvJr1FbT97NB+GW0rDPJ9e7sg1aimdZrsW0kKiWMKSxKi5 J8hrwQOnawKk9WeTAOtLFB53/yWcPmacfiSlRY14QTEwlHPNy4xiQK/rlnzhITZ4 1dJ8GYIEtZuoDeIjD9Gve+g+xIeO6vbDl1T/wcssxuvueRvDWMAJ/qfs5uMk2Giw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id B1D9A9E09C; Thu, 22 Mar 2018 16:53:14 -0400 (EDT) Message-Id: <1521751994.3262203.1312821720.2F23D196@webmail.messagingengine.com> From: Bron Gondwana To: Brandon Long Cc: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152175199432622030" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Fri, 23 Mar 2018 07:53:14 +1100 In-Reply-To: References: <1521726212.1534780.1312293528.5114E8E7@webmail.messagingengine.com> Archived-At: Subject: Re: [Extra] Call for adoption: draft-melnikov-imap4rev2 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 20:53:20 -0000 This is a multi-part message in MIME format. --_----------=_152175199432622030 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" My apologies, I was so busy taking I forgot to minute that, but I also suggested literal- in the meeting. 100% agree. On Fri, 23 Mar 2018, at 07:47, Brandon Long wrote: > A note on a quick review of the changes of that draft, it wants to > incorporate LITERAL+... I'd recommend LITERAL- instead for the > reasons we> added that. > > Brandon > > > On Thu, Mar 22, 2018 at 6:43 AM Bron Gondwana > wrote:>> __ >> We had consensus in the meeting at IETF101 to adopt this large amount >> of work! Barry has volunteered to work with Alexey on the document. >> We expect much more discussion on the mailing list, and a slow burn >> for a while as we clear our decks.>> >> https://datatracker.ietf.org/doc/draft-melnikov-imap4rev2/ >> >> If you have any objections, speak before Monday 26th! >> >> Cheers, >> >> Bron. >> >> -- >> Bron Gondwana, CEO, FastMail Pty Ltd >> brong@fastmailteam.com >> >> >> _______________________________________________ >> 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 -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152175199432622030 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
My apologies, I was so busy taking I forgot to minute that, but I also suggested literal- in the meeting. 100% agree.


On Fri, 23 Mar 2018, at 07:47, Brandon Long wrote:
A note on a quick review of the changes of that draft, it wants to incorporate LITERAL+... I'd recommend LITERAL- instead for the reasons we
added that.

Brandon


On Thu, Mar 22, 2018 at 6:43 AM Bron Gondwana <brong@fastmailteam.com> wrote:

We had consensus in the meeting at IETF101 to adopt this large amount of work!  Barry has volunteered to work with Alexey on the document.  We expect much more discussion on the mailing list, and a slow burn for a while as we clear our decks.


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

--
  Bron Gondwana, CEO, FastMail Pty Ltd


_______________________________________________
Extra mailing list
_______________________________________________
Extra mailing list

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

--_----------=_152175199432622030-- From nobody Thu Mar 22 14:58:51 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 02A8D126DEE for ; Thu, 22 Mar 2018 14:58:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 1hXV64SW9Zps for ; Thu, 22 Mar 2018 14:58:48 -0700 (PDT) Received: from smtp-out-2.mxes.net (smtp-out-2.mxes.net [67.222.241.249]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB424124B0A for ; Thu, 22 Mar 2018 14:58:48 -0700 (PDT) Received: from [192.168.122.118] (ip174-65-80-226.sd.sd.cox.net [174.65.80.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9FA7127559; Thu, 22 Mar 2018 17:58:46 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) From: Sean Leonard In-Reply-To: Date: Thu, 22 Mar 2018 14:58:45 -0700 Cc: extra@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <9CC9F0EC-1427-4C6C-AFFD-188FE8789A40@seantek.com> References: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> To: Arnt Gulbrandsen X-Mailer: Apple Mail (2.3445.4.7) Archived-At: Subject: Re: [Extra] Call for opinions: decision about what to do with 64bit X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 21:58:50 -0000 > On Mar 22, 2018, at 12:56 PM, Arnt Gulbrandsen = wrote: >=20 > Bron Gondwana writes: >> So I'm calling here to see if there's any objections to parking, with = a side note that anyone objecting to parking needs to convince people to = work on it, and we're pretty busy right now! >=20 > IMO, larger message sizes are either important enough to include in = imap4rev2 or unimportant enough to ignore altogether. Extensions are = harmful by default, and need justification for their very existence. I = don't bother to argue the point. With these brief alternatives outlined, I am in favor of including it in = IMAP4rev2. Storage needs are only increasing over time, not decreasing. = Looking at the evolution of hard drive/SSD interfaces, for example, one = can see numerous points in the industry where someone increased the bit = width, only to find another barrier at the next generation. Nobody is = going to go beyond 64-bit and it is the next step up by 32 orders of = binary magnitude, so let=E2=80=99s just do it as a CAPABILITY in = IMAP4rev2. I also would like to suggest updating the ABNF in = draft-ietf-extra-imap-64bit from: number64 =3D 1*DIGIT to: number64 =3D 1*19DIGIT as that would help with abnfgen and other tools not to go hog wild with = the numbers. (Writing the ABNF to limit to exactly = 9,223,372,036,854,775,807 is possible, but not so practical.) Sean From nobody Thu Mar 22 16:03:48 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 E8EF41270A0 for ; Thu, 22 Mar 2018 16:03:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 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, T_RP_MATCHES_RCVD=-0.01] 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 abCAiVZCovdY for ; Thu, 22 Mar 2018 16:03:44 -0700 (PDT) Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF13124D6C for ; Thu, 22 Mar 2018 16:03:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1521759823; d=isode.com; s=june2016; i=@isode.com; bh=lzoWYxztQP28f6F6e7t2y2nQaBhi2GFARc4LWqnQK40=; 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=K+6L+TyX6e0nfUAUO1tQJkMrpYtGyxW4Di5pN3FW4f8cdbIgnxxoW4Z3Ik5uJiEXzKAT5W txlGF3k07TESNdeLLJjyFC4itI/GWTYUkkbllT36JuxO3vSgn9IZCp6oCq0r4XBcuOIpSW ZGKcpfSBw2vSJjWqOECgtq0XTo8K95E=; Received: from [10.236.55.171] ((unknown) [85.255.232.70]) by statler.isode.com (submission channel) via TCP with ESMTPSA id ; Thu, 22 Mar 2018 23:03:42 +0000 X-SMTP-Protocol-Errors: NORDNS From: Alexey Melnikov X-Mailer: iPhone Mail (15C202) In-Reply-To: <1521751994.3262203.1312821720.2F23D196@webmail.messagingengine.com> Date: Thu, 22 Mar 2018 23:03:40 +0000 Cc: Brandon Long , extra@ietf.org Message-Id: <052956D5-B4C1-4D87-B765-D0882B7708F2@isode.com> References: <1521726212.1534780.1312293528.5114E8E7@webmail.messagingengine.com> <1521751994.3262203.1312821720.2F23D196@webmail.messagingengine.com> To: Bron Gondwana MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=Apple-Mail-60A5D300-EAE3-4E84-A543-0BBF1EE51F9D Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Extra] Call for adoption: draft-melnikov-imap4rev2 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 22 Mar 2018 23:03:46 -0000 --Apple-Mail-60A5D300-EAE3-4E84-A543-0BBF1EE51F9D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On 22 Mar 2018, at 20:53, Bron Gondwana wrote: >=20 > My apologies, I was so busy taking I forgot to minute that, but I also sug= gested literal- in the meeting. 100% agree. That would be a straightforward change to make. So no objections from me. >> On Fri, 23 Mar 2018, at 07:47, Brandon Long wrote: >> A note on a quick review of the changes of that draft, it wants to incorp= orate LITERAL+... I'd recommend LITERAL- instead for the reasons we >> added that. >>=20 >> Brandon >>=20 >>=20 >> On Thu, Mar 22, 2018 at 6:43 AM Bron Gondwana wr= ote: >>=20 >> We had consensus in the meeting at IETF101 to adopt this large amount of w= ork! Barry has volunteered to work with Alexey on the document. We expect m= uch more discussion on the mailing list, and a slow burn for a while as we c= lear our decks. >>=20 >> https://datatracker.ietf.org/doc/draft-melnikov-imap4rev2/ >>=20 >> If you have any objections, speak before Monday 26th! >>=20 >> Cheers, >>=20 >> Bron. >>=20 >> -- >> Bron Gondwana, CEO, FastMail Pty Ltd >> brong@fastmailteam.com >>=20 >>=20 >> _______________________________________________ >> 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 >=20 > -- > Bron Gondwana, CEO, FastMail Pty Ltd > brong@fastmailteam.com >=20 > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra --Apple-Mail-60A5D300-EAE3-4E84-A543-0BBF1EE51F9D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 22 Mar 2018, at 20:53, Bron Gondwana <brong@fastmailteam.com> wrote:

My apologies, I was so busy taking I forgot to minute that, but I also suggested literal- in the meeting. 100% agree.

That would be a straightforward change to make. So no objections from me.

On Fri, 23 Mar 2018, at 07:47, Brandon Long wrote:
A note on a quick review of the changes of that draft, it wants to incorporate LITERAL+... I'd recommend LITERAL- instead for the reasons we
added that.

Brandon


On Thu, Mar 22, 2018 at 6:43 AM Bron Gondwana <brong@fastmailteam.com> wrote:

We had consensus in the meeting at IETF101 to adopt this large amount of work!  Barry has volunteered to work with Alexey on the document.  We expect much more discussion on the mailing list, and a slow burn for a while as we clear our decks.


If you have any objections, speak before Monday 26th!

Cheers,

Bron.

--
  Bron Gondwana, CEO, FastMail Pty Ltd


_______________________________________________
Extra mailing list
_______________________________________________
Extra mailing list

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

_______________________________________________
Extra mailing list
Extra@ietf.org
https://www.ietf.org/mailman/listinfo/extra
--Apple-Mail-60A5D300-EAE3-4E84-A543-0BBF1EE51F9D-- From nobody Thu Mar 22 17:21:52 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 864D5127058 for ; Thu, 22 Mar 2018 17:21:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 QFMzruchoNtg for ; Thu, 22 Mar 2018 17:21:49 -0700 (PDT) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 42F91120047 for ; Thu, 22 Mar 2018 17:21:49 -0700 (PDT) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2N0CUMl111835; Fri, 23 Mar 2018 00:21:43 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=yAGECLbUXVZ97xDnCxCO2RlLnqXkJNKxtbtTbOnccq4=; b=HIMT7Tbl1X7NA0of+Bo35KkhsPhYmQ7E7uFgbWuqsqvyaHjGrDFK7Ox6iYVrZzGNMP2w qrGZ/bSmJeobuOmlCv6uRb6VUR9nwkJNGHVtYc9h4c/0372npxtOgK6NNK95ENk0nibL aXjBtkvSJnpOZs1syiDo/B5cUasWgT/eff8hQeBpfii9UzYwC1JNIk4K0iX6/iTdtard VIoxfscFYTx9VYded5wgyAuOLRMc6jp4C8MdQbYC5uI7zLkZB7BuCquBHepjGWTvj0Ss RJRDh46DdoQmCblj+7Puy/gC+yEfNa1TPMlc/etYXHMkp3tciSoGPOcp1JHCt+fK9erI 6g== Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp2130.oracle.com with ESMTP id 2gvpu3r0gu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 23 Mar 2018 00:21:43 +0000 Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2N0Lgbo024154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 23 Mar 2018 00:21:42 GMT Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w2N0LgG0028879; Fri, 23 Mar 2018 00:21:42 GMT Received: from [31.133.145.111] (/31.133.145.111) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Mar 2018 17:21:42 -0700 From: "Chris Newman" To: "Arnt Gulbrandsen" Cc: extra@ietf.org Date: Fri, 23 Mar 2018 00:21:34 +0000 X-Mailer: MailMate (1.11r5462) Message-ID: In-Reply-To: References: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8840 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Archived-At: Subject: Re: [Extra] Call for opinions: decision about what to do with 64bit X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 00:21:50 -0000 On 22 Mar 2018, at 19:56, Arnt Gulbrandsen wrote: > Bron Gondwana writes: >> So I'm calling here to see if there's any objections to parking, with >> a side note that anyone objecting to parking needs to convince people >> to work on it, and we're pretty busy right now! > > IMO, larger message sizes are either important enough to include in > imap4rev2 or unimportant enough to ignore altogether. I agree with this point. By itself I think larger size is unimportant enough to ignore. However, the suggestion was made to make "ENABLE IMAP4rev2" subsume "ENABLE UTF8=ACCEPT". There are a number of reasons that may be compelling enough to include in IMAP4rev2. In the event we do that in IMAP4rev2, then the incremental cost of supporting larger message sizes becomes negligible (because a mailbox format change and dealing with messages incompatible with IMAP4rev1 is necessary anyway) and I'd have no objection to it hitching a ride. I do not believe it's a good idea to subsume "ENABLE UTF8=ACCEPT" into IMAP4rev2 until we have detailed feedback from at least one implementation. As one of the co-editors of RFC 6855, I believe it is a solid spec but know it's complex and there will be unexpected subtleties. We need implementation feedback on those subtleties before letting it become part of the IMAP4rev2 baseline. For example, the fact that we did not define a way to represent an MUTF-7-encoded hierarchy delimiter in RFC 6855 is a detail I did not realize until the issue was mentioned in EXTRA today (I don't think that's a big deal, but advice for that scenario may be appropriate). That's the sort of thing implementation experience uncovers. - Chris From nobody Fri Mar 23 00:35:07 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 5B236129502 for ; Fri, 23 Mar 2018 00:35:06 -0700 (PDT) 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 7bf8b3TznhSj for ; Fri, 23 Mar 2018 00:35:04 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3B0A124239 for ; Fri, 23 Mar 2018 00:35:04 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 18A93FA00AF; Fri, 23 Mar 2018 07:35:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521790502; bh=eriLUDjN6xOQSESDVcNChdG7++nh//7cxi4Sz0ZKFtE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=L5z31mJ9R3nCVcgMDVkcmcSeUHGS10VGHGm72ZxN+rcMa8L6eou9pS11+ig2CWT4b pz9GKX1DN0nFEBUQU5uBRNGzlsn75uucJcLgEU+4VNAzaLaFoiVzJLeqDRpCj8hCuS NmlToALr+B9teEn8KFlndvyAHT8OfgxE3G2sDyi4= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521790501-12902-31493/11/18; Fri, 23 Mar 2018 07:35:01 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Fri, 23 Mar 2018 07:35:01 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: <4ed31760-7d54-4c16-8bb7-502b5b6f1a8d@gulbrandsen.priv.no> In-Reply-To: References: <1521745914.2843013.1312706760.3F160E36@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] Call for opinions: decision about what to do with 64bit X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 07:35:06 -0000 Chris Newman writes: > I do not believe it's a good idea to subsume "ENABLE > UTF8=ACCEPT" into IMAP4rev2 until we have detailed feedback from > at least one implementation. Do you remember the jabber session during last call? You, Barry, I and perhaps one or two more people. Last call had been issued, I did an implementation, found a plurality of issues, raised them, and they were all fixed, that same week. I was overwhelmed. What is the separator issue? I didn't notice, but then I'm the the kind of nogoodnik that just treats mailbox names as strings and issues LIST * "" instead of pondering hierarchies. By my count there have been two major and five minor implementations so far. Four different servers are telnettable on the open net. You can find three implementations on github if you look hard enough. Arnt From nobody Fri Mar 23 06:09:10 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 647FE12D88C for ; Fri, 23 Mar 2018 06:09:09 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=d1QI5On8; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MQhhlcZR 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 vT-mee_ByJNM for ; Fri, 23 Mar 2018 06:09:08 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F200012D86D for ; Fri, 23 Mar 2018 06:09:07 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 46A6A210CB for ; Fri, 23 Mar 2018 09:09:07 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Fri, 23 Mar 2018 09:09:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=HFEkMhysUXKCWlSEJeMY88GnGeZMiwedQpsU1VIrK bo=; b=d1QI5On8HOZtQ2Fp0rvIMrKSiDgtpC8rpodwUwlisLzrc7o/w36seHtot 5qa96en9sxSwWWRkBBSssLPXr3imc5EEMZSe0AYHLLM6MYzXFbieQ3NrYr2KC/aP 08SxAAm1HwYTrA2l3AjDRAzeElyNkBq3qcad51Gfav/cjLNzLXXw1xcKesXAr1Ae 2fMu3nvKWkRFM+DhfqgqppgaZy/M+hywLjYy3tJRZpg0eUW1l8cq17Hbv2fR5lrT xdAAoLvSKpMOdPtx3EtFSRSsxlRP/+85w5+Jf8H/vJ4y8+XbDE5HOjgzpwr+Ot8B TirCAQBWwVD11xJqlijOGoC6fS/Mg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=HFEkMhysUXKCWlSEJeMY88GnGeZMi wedQpsU1VIrKbo=; b=MQhhlcZRbT7e2UQQGpxvwUu98kfpS2WsqjPBq6ifYSfyd oBzlwS8WA4metv855DS1p8/4/wbzfyGBUZrC+ApiN6/x86mQ54/pErLIWIvVC2F2 HBDRLZUHXlEvCs4yVfzsbyGekSrMzOuI85BSlPvk0QmYVaCkivW631BSfsxTSOQ4 QO9Y7LgIRVYaRUrM5LvXulnneJviKEgArb23JeJ0zDEhYovjf/8mTJBnxOEUwHQO bZhVG6JXRyy6yUspPSXQ12C11fjFTNuh1GbncHabyw6VhTzF2HJvEP8vu7tdqsIi gdhsLPqeNAgo9nPL5z3A0nRXUktURfzE9aBC6KUsw== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 214B2BA43B; Fri, 23 Mar 2018 09:09:07 -0400 (EDT) Message-Id: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152181054733015445" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Sat, 24 Mar 2018 00:09:07 +1100 Archived-At: Subject: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 13:09:09 -0000 This is a multi-part message in MIME format. --_----------=_152181054733015445 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" This looks pretty nice: C: 3 create user.cassandane S: 3 OK [MAILBOXID 87nn6m5t8azrrrywp4qfxkez] Completed This looks a little more weird for a basic append: S: 5 OK [APPENDUID 1521809303 1] [EMAILID (M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)] Completed I'm not sure that the syntax is strictly right there. And it gets particularly messy when you do multiappend: S: 30 OK [APPENDUID 1521810470 4:5] [EMAILID (Mdeafec675369c08d9b50da49 M1fb935aca6bc7afce76f6016)] [THREADID (T4f5c35865800cb9f T8e4aec4dadd571ee)] Completed But - it's pretty valuable to have that data at append time, in exactly the same way that UIDPLUS was good. Can anyone think of a better way? Thanks, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152181054733015445 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
This looks pretty nice:

C: 3 create user.cassandane
S: 3 OK [MAILBOXID 87nn6m5t8azrrrywp4qfxkez] Completed

This looks a little more weird for a basic append:

S: 5 OK [APPENDUID 1521809303 1] [EMAILID (M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)] Completed

I'm not sure that the syntax is strictly right there.  And it gets particularly messy when you do multiappend:

S: 30 OK [APPENDUID 1521810470 4:5] [EMAILID (Mdeafec675369c08d9b50da49 M1fb935aca6bc7afce76f6016)] [THREADID (T4f5c35865800cb9f T8e4aec4dadd571ee)] Completed


But - it's pretty valuable to have that data at append time, in exactly the same way that UIDPLUS was good.  Can anyone think of a better way?

Thanks,

Bron.

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


--_----------=_152181054733015445-- From nobody Fri Mar 23 06:13:47 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 4A3EC12D88C for ; Fri, 23 Mar 2018 06:13:45 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 NpF2utWNrGsx for ; Fri, 23 Mar 2018 06:13:44 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7A48127873 for ; Fri, 23 Mar 2018 06:13:43 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4CE28FA00AF; Fri, 23 Mar 2018 13:13:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521810822; bh=ysvaftov/KJKOtzxTreiBlQqlJxsQ+tXjY1veXeGzwk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FLzpTinFYeA5JVsycqZ3mgP4ogfkI+7W947mm5EHVohvuoPmqAnso7d5TBTekeKnP tt0Nwv2mDEpUurLGDMEBYWo36jZuHWAwB53JJT0z5jX86r504eY444VzF40l4tEJZn k+RquyO93atIZgfh2ZV6MYW6EUNY6GuYai7Z4mq0= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521810821-12902-31493/11/20; Fri, 23 Mar 2018 13:13:41 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Fri, 23 Mar 2018 13:13:40 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> In-Reply-To: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> References: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 13:13:45 -0000 Bron Gondwana writes: > S: 5 OK [APPENDUID 1521809303 1] [EMAILID > (M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)] > Completed > > I'm not sure that the syntax is strictly right there. And it > gets particularly messy when you do multiappend: Can you even send several of those? Doesn't the syntax restrict you to one resp-text? You can achieve the same with an unsolicited FETCH though. Arnt From nobody Fri Mar 23 06:17: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 DB549127873 for ; Fri, 23 Mar 2018 06:17:13 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=HIl6fGvI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RDQPB0Ws 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 flCrnxJEbg1O for ; Fri, 23 Mar 2018 06:17:12 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 952F012D945 for ; Fri, 23 Mar 2018 06:17:12 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 079C121627 for ; Fri, 23 Mar 2018 09:17:12 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Fri, 23 Mar 2018 09:17:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=JQuW4FotTKwJqKb6J 0ApnPB8ZX6bHvGwuHYvhWi6pZY=; b=HIl6fGvI8Hv/jfgR2PpKPz3r4Cp2TTe/f pLFUPT3Y25TnnPr4tCo/V1OvVNbkdvGnsNjBthwC6HjNEncXDmhAjlYNPviImF6U YtUDC+5F7cDzYkRvSV/tOTCyZX7qw+l9y3IzX0W6XGHcHlAuGwXmaywwzL5lBgWC fCO1N2zcSU0U+iGvFHx+qWBvheB8D14TYOTje19qyWBSlHAviQpUKkvFhphnBcuV BWaZ2vqpgVzggPpePzAlxOUqaE0HQTuaJ60y0xNGLUFLU3HkRZ1V8ZcOVzxb0z8y +lBIhpM1KbNJu9brOMsZkNotKCRbLns+usjOKVOsCqNGlD3yHNkxw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=JQuW4F otTKwJqKb6J0ApnPB8ZX6bHvGwuHYvhWi6pZY=; b=RDQPB0Ws1LzyJlLd6FUMqL hj/mv4iH4zwJoscOUyQ38G4nQpfKCd++rBZ48qaKNi+OiMyatSqz8TA9i4uoTVhd L8q6H6/qnxWzrDE91fDrHMPckZedyRHSiV8SOY6YsksIfk9AMv9XJ+mc4NVXKZW8 atjqI0bMN0FTq0VO6MFdmy7N5sdtRQHKqNU8UApnj8DbJ2y5qoRRynJ4RMqP1M5i UD/Kb78eNv1x+VL5yXx0q4nHJ04FpPpFH5jZjwKvgJCbkbtIF6z8y47FGy13e6nM lI2PFB300Sxsxym/1nisL2tpmzMxnH//SQ93eU5rM4SOUr+JOJyfUv+Di2VyF7SA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id CEA6DBA43B; Fri, 23 Mar 2018 09:17:11 -0400 (EDT) Message-Id: <1521811031.3306267.1313545704.1A5F1E97@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152181103133062673" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> Date: Sat, 24 Mar 2018 00:17:11 +1100 In-Reply-To: <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> Archived-At: Subject: Re: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 13:17:14 -0000 This is a multi-part message in MIME format. --_----------=_152181103133062673 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Sat, 24 Mar 2018, at 00:13, Arnt Gulbrandsen wrote: > Bron Gondwana writes: >> S: 5 OK [APPENDUID 1521809303 1] [EMAILID >> (M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)] >> Completed >> >> I'm not sure that the syntax is strictly right there. And it >> gets particularly messy when you do multiappend: > > Can you even send several of those? Doesn't the syntax restrict > you to one> resp-text? > > You can achieve the same with an unsolicited FETCH though. That's exactly what I was looking for :) Of course, an unsolicited FETCH is going to require an ENABLE, and I'd hoped to avoid one of those. But it's obvious that I need it. Our server doesn't even add UID to unsolicited FETCHes unless QRESYNC/CONDSTORE is enabled due to the fact that some clients can't (or at least couldn't once) handle anything but FLAGS in the unsolicited data. Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152181103133062673 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Sat, 24 Mar 2018, at 00:13, Arnt Gulbrandsen wrote:
Bron Gondwana writes:
S: 5 OK [APPENDUID 1521809303 1] [EMAILID
(M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)]
Completed

I'm not sure that the syntax is strictly right there.  And it
gets particularly messy when you do multiappend:

Can you even send several of those? Doesn't the syntax restrict you to one
resp-text?

You can achieve the same with an unsolicited FETCH though.

That's exactly what I was looking for :)

Of course, an unsolicited FETCH is going to require an ENABLE, and I'd hoped to avoid one of those.  But it's obvious that I need it.  Our server doesn't even add UID to unsolicited FETCHes unless QRESYNC/CONDSTORE is enabled due to the fact that some clients can't (or at least couldn't once) handle anything but FLAGS in the unsolicited data.

Bron.


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


--_----------=_152181103133062673-- From nobody Fri Mar 23 06:34:39 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 7AC60126D0C for ; Fri, 23 Mar 2018 06:34:38 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=o/4hWNSA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=l+zLF7Ey 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 UMQChFKNTBnK for ; Fri, 23 Mar 2018 06:34:37 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1093E1200F1 for ; Fri, 23 Mar 2018 06:34:37 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id ADDA120A92 for ; Fri, 23 Mar 2018 09:34:33 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Fri, 23 Mar 2018 09:34:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=xCpsE0zUyj3iHskik nqI9DFY5pJGyd85Eh6Nxj7Y0Ew=; b=o/4hWNSAekAYgVARk0MmQ8jHY+dIJMBvv vu7ftZREo0OULy8Vy1gFYZTO8lpfmW6qMC6Ec8KSqbQZRAyYQu19qiWOx4H+gZzI lhcsRPa0sBYlphoi0JwJNZfjqy7OlJrmVGO7Y0N5tuAXcHOt4ROgPsq9NZaerQyY v9luHIXLmI2czRQOlzDQcMMYX2bWnvznRHAj/rxnqIlM9hCyJ2a8QKOTsPgXB55e GE/wEGbPwX4cKAfRddnsOTOHheVTTRtueQQR/Rl3XAzmb5sIGCDNcHsXivN4epnn 8Y64j8D/9M04cn0ouO7ICtKHooRt+hFmZFeH3gMEYTvyys++f4jgg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=xCpsE0 zUyj3iHskiknqI9DFY5pJGyd85Eh6Nxj7Y0Ew=; b=l+zLF7EyFLj7Rp63m0ShJP zA9b92+222dnzbG3N0EA4WqXMcjevrqESSXzvC40qGip7i/5OQP80Q6EfrhFil3+ B+ns/W65avr8yl8sZgO9+FdyP5NM+Z3SS2gSeZ87qnkIWOvK1NuPikliDKzLbbyJ OS8dal0AnMvMaITDKWzBuVk0Ldu7MCsu9GXQtK2IzhOjSFLz8dc8MqFDyiQ0hZSm QMI5Gz+K8UU5bRm8MZqXqvXRl0KbR/QbnAKS5x40FmUbTrYeN1Yglf3N+c32v6Pp Nog3AuDfuM7wa94GjXNbM3wRMHUzmFdzaWg9p+OAA7C1qSZeIuOohlISdCCHMXhw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 882F7BA43B; Fri, 23 Mar 2018 09:34:33 -0400 (EDT) Message-Id: <1521812073.3316344.1313565888.5F108D87@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152181207333163440" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Sat, 24 Mar 2018 00:34:33 +1100 In-Reply-To: <1521811031.3306267.1313545704.1A5F1E97@webmail.messagingengine.com> References: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> <1521811031.3306267.1313545704.1A5F1E97@webmail.messagingengine.com> Archived-At: Subject: Re: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 13:34:38 -0000 This is a multi-part message in MIME format. --_----------=_152181207333163440 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Sat, 24 Mar 2018, at 00:17, Bron Gondwana wrote: > On Sat, 24 Mar 2018, at 00:13, Arnt Gulbrandsen wrote: >> Bron Gondwana writes: >>> S: 5 OK [APPENDUID 1521809303 1] [EMAILID >>> (M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)] >>> Completed >>> >>> I'm not sure that the syntax is strictly right there. And it >>> gets particularly messy when you do multiappend: >> >> Can you even send several of those? Doesn't the syntax restrict >> you to one>> resp-text? >> >> You can achieve the same with an unsolicited FETCH though. > > That's exactly what I was looking for :) > > Of course, an unsolicited FETCH is going to require an ENABLE, and I'd > hoped to avoid one of those. But it's obvious that I need it. Our > server doesn't even add UID to unsolicited FETCHes unless > QRESYNC/CONDSTORE is enabled due to the fact that some clients can't > (or at least couldn't once) handle anything but FLAGS in the > unsolicited data. Dammit, no it isn't :( You can't do an unsolicited FETCH response to an APPEND because you're not in SELECTED state. *sigh*. So it's either a new unsolicited response, or it's a response tag, or it's "sorry, you'll just have to fetch it yourself based on the UIDs". Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152181207333163440 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
On Sat, 24 Mar 2018, at 00:17, Bron Gondwana wrote:
On Sat, 24 Mar 2018, at 00:13, Arnt Gulbrandsen wrote:
Bron Gondwana writes:
S: 5 OK [APPENDUID 1521809303 1] [EMAILID
(M0685889f69dc2ecf04a0abbe)] [THREADID (T9776517e62b525dd)]
Completed

I'm not sure that the syntax is strictly right there.  And it
gets particularly messy when you do multiappend:

Can you even send several of those? Doesn't the syntax restrict you to one
resp-text?

You can achieve the same with an unsolicited FETCH though.

That's exactly what I was looking for :)

Of course, an unsolicited FETCH is going to require an ENABLE, and I'd hoped to avoid one of those.  But it's obvious that I need it.  Our server doesn't even add UID to unsolicited FETCHes unless QRESYNC/CONDSTORE is enabled due to the fact that some clients can't (or at least couldn't once) handle anything but FLAGS in the unsolicited data.

Dammit, no it isn't :(

You can't do an unsolicited FETCH response to an APPEND because you're not in SELECTED state.  *sigh*.

So it's either a new unsolicited response, or it's a response tag, or it's "sorry, you'll just have to fetch it yourself based on the UIDs".

Bron.

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


--_----------=_152181207333163440-- From nobody Fri Mar 23 06:53:40 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 6973712D869 for ; Fri, 23 Mar 2018 06:53:39 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 AaJH8FtlaOtV for ; Fri, 23 Mar 2018 06:53:38 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F6B712D868 for ; Fri, 23 Mar 2018 06:53:38 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 63519FA00AF; Fri, 23 Mar 2018 13:53:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1521813216; bh=j1lOv3VYAWV6IxtVdlbZI3H/sc/XLIM6BK5XHosXL80=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aGpMlsOscXrwJn99wkS9UeBAQ/j2WtF1ttxg+dKW4JYmPoc5Dkdr49SfTDG/xtKcq tpvSWgtv1SEbK5oxw69sA/eCm8iqauiCy8BcsIqdgWJd4keNLzESmUWOK3YvMJkpew rpTzZ514V6OcsQSiWAWdP4fbc1ILrdH7qSCe8OKQ= Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1521813215-12902-31493/11/21; Fri, 23 Mar 2018 13:53:35 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Fri, 23 Mar 2018 13:53:34 +0000 User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie) Mime-Version: 1.0 Message-Id: <5b5efc67-9fab-4bd8-ba21-a9c63b2a0e51@gulbrandsen.priv.no> In-Reply-To: <1521812073.3316344.1313565888.5F108D87@webmail.messagingengine.com> References: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> <1521811031.3306267.1313545704.1A5F1E97@webmail.messagingengine.com> <1521812073.3316344.1313565888.5F108D87@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 13:53:39 -0000 Bron Gondwana writes: > Dammit, no it isn't :( > > You can't do an unsolicited FETCH response to an APPEND because=20 > you're not in SELECTED state. *sigh*. > > So it's either a new unsolicited response, or it's a response=20 > tag, or it's "sorry, you'll just have to fetch it yourself based=20 > on the UIDs". Why aren't you in selected state? Append in selected state isn't = forbidden? I think you may assume that that all clients that care about thread-IDs = and=20 so on are able to a) select a mailbox and b) parse FETCH =E2=80=A6THREADI= D, and=20 another solution can hardly be as simple. As a wise old colleague of = mine=20 once said, you don't always have to make those people happy who choose = to=20 stay off the happy path. Arnt From nobody Fri Mar 23 07:55:21 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 009ED12D7FC for ; Fri, 23 Mar 2018 07:55:20 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=lMAVyixE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=d/WfHIWx 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 JrhdTb1vvk_g for ; Fri, 23 Mar 2018 07:55:18 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1CAD129C53 for ; Fri, 23 Mar 2018 07:55:17 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2E23220D3C; Fri, 23 Mar 2018 10:55:17 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Fri, 23 Mar 2018 10:55:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=5dxgBnjczbcYUlVmf w1tfwdDNYTGW/bHIEULTzgKSCQ=; b=lMAVyixEhcoDZm5sEC3yIWwvs6sTNz2qc ylBMkmcFEMP3NBZD7ygvT06zlYBjtaNKKEy3UTe0rL5jfayGCnHfRtXMlXrkzS2K nAWMUAdgnLdETkGqvTrnZLBF92z12AyQTNmgoX0rOc8nrs3jYBPYl5KDSo6pqMoZ Y7IttRUe/1aC6lm4TpknvMw3Z0QuV9xRzUjnrZhTR2/7kkXX1i46sVC/M47M9/FG C7HrIy+fKCeqH67NyhB9MvuRDW3GmVdmCn0N1JdaY/zdugA2ukt61rJfD+j0O4BN 2636O92j9NfFTXMMXFSmIPr33V6gfmB0Wre/KQDbtNre7MeMFmBQw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=5dxgBn jczbcYUlVmfw1tfwdDNYTGW/bHIEULTzgKSCQ=; b=d/WfHIWxFCpivuC00+uvnT xXYqiRws0RbFDO3RHW5cBbMcZH/1EcrQZTCHyyG0kPm/GuB6SVvUaDtRojQ8iaMY 0yq68XWgamv8adquUaqWaF8Sv+Lh+BjfC0B7BBld2qO/HqQjwTL4MjLGxm0FzGhE MUCfHgB11oE4BXB+obda946c6ECe0ygrBYs5dsYJU26U4SOmqrGTYW34+/4Q1Ekf PQo/lz/i8NJfK4ps7xRIgPmFXkTOGBeH5easr3MWP7Sc0ZuVX/WDwExvjJdV80R3 1XJyKGS7lzB2iuHKPlgDOsQn5RUG3NQihH2pR69EONKFdErAT9hRSrwWOkUpwJIQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id EAED99E0F6; Fri, 23 Mar 2018 10:55:16 -0400 (EDT) Message-Id: <1521816916.3640525.1313662016.3E4069AB@webmail.messagingengine.com> From: Bron Gondwana To: Arnt Gulbrandsen , extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152181691636405250" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <1521810547.3301544.1313525824.20D3DBD2@webmail.messagingengine.com> <550b535b-1bf4-4146-9f5d-d85c590693e1@gulbrandsen.priv.no> <1521811031.3306267.1313545704.1A5F1E97@webmail.messagingengine.com> <1521812073.3316344.1313565888.5F108D87@webmail.messagingengine.com> <5b5efc67-9fab-4bd8-ba21-a9c63b2a0e51@gulbrandsen.priv.no> Date: Sat, 24 Mar 2018 01:55:16 +1100 In-Reply-To: <5b5efc67-9fab-4bd8-ba21-a9c63b2a0e51@gulbrandsen.priv.no> Archived-At: Subject: Re: [Extra] imap-uniqueid and response codes X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 23 Mar 2018 14:55:20 -0000 This is a multi-part message in MIME format. --_----------=_152181691636405250 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Sat, 24 Mar 2018, at 00:53, Arnt Gulbrandsen wrote: > Bron Gondwana writes: >> Dammit, no it isn't :( >>=20 >> You can't do an unsolicited FETCH response to an APPEND because >> you're not in SELECTED state. **sigh**. >>=20 >> So it's either a new unsolicited response, or it's a response >> tag, or it's "sorry, you'll just have to fetch it yourself based >> on the UIDs". >=20 > Why aren't you in selected state? Append in selected state isn't > forbidden? True. It's more in our implementation at least, the selected state is very much not required for APPEND and hence the codepath is parallel and doesn't know anything about the index state, which means if you start doing unsolicited FETCH responses you aren't updating the toldmodseq and other interesting bits. Alternatively, the index code could always send EMAILID and THREADID as part of the unsolicited update, but it would want to make sure it doesn't keep sending them if there are further keyword updates, because that's wasteful. Bron. > I think you may assume that that all clients that care about > thread-IDs and> so on are able to a) select a mailbox and b) parse FETCH > =E2=80=A6THREADID, and> another solution can hardly be as simple. As a wi= se old > colleague of mine> once said, you don't always have to make those people = happy who > choose to> stay off the happy path. >=20 > Arnt >=20 > _________________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152181691636405250 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
On Sat, 24 Mar 2018, at 00:53, Arnt= Gulbrandsen wrote:
Bron Gondwana writes:
Dammit, no it isn't :(

You can't do an unsolicited FETCH response to an APPEND because
you're not in SELECTED state.  *sigh*.

So it's either a new unsolicited response, or it's a response
tag, or it's "sorry, you'll just have to fetch it yourself based
on the UIDs".

Why aren't you in selected state? Append in selected state isn't forbi= dden?

True.  It's more in our implementati= on at least, the selected state is very much not required for APPEND and he= nce the codepath is parallel and doesn't know anything about the index stat= e, which means if you start doing unsolicited FETCH responses you aren't up= dating the toldmodseq and other interesting bits.

Alternatively, the index code could alway= s send EMAILID and THREADID as part of the unsolicited update, but it would= want to make sure it doesn't keep sending them if there are further keywor= d updates, because that's wasteful.

Bron.

I think you may assume that that all clients= that care about thread-IDs and
so on are able to a) select a mailbox and b) parse FETCH =E2=80=A6THRE= ADID, and
another solution can hardly be as simple. As a wise old colleague of m= ine
once said, you don't always have to make those people happy who choose= to
stay off the happy path.

Arnt

_______________________________________________
Extra mailing list

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


--_----------=_152181691636405250-- From nobody Sat Mar 24 05:40:06 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 27EA0128954 for ; Sat, 24 Mar 2018 05:40:05 -0700 (PDT) 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=lSZZOAkF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CmB53AJZ 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 kgQkX771SAlW for ; Sat, 24 Mar 2018 05:40:02 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68400127AD4 for ; Sat, 24 Mar 2018 05:40:02 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 921F120BF1 for ; Sat, 24 Mar 2018 08:40:01 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Sat, 24 Mar 2018 08:40:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bDZtw9vJ3vjTEcV2O lGTFYgYgUVSmJTXrEiPaNN8kyE=; b=lSZZOAkFXJKJwCCydiSj2zC6HCCCUGt2W LylVbsfLzvLegUTyEiuSYkRECpMFtLmoed6v3Ykv4nPGg/RQmfcb9iUXxz9eAzUP z5/itVbWfRsatCBF+Vi29KH1lb1jFgI77rxDhdCaWvKaCGsOnQT+T0z+sKQ+yTVq SLjsOyc77Szf35hpVeANpw0UD9JxtIYy4G2TcE8Htd5jr/p9yXn8mw7nuvOHQ8Jy 7AJnhYuwfggH+i+/N+SheO16r7q+oq7T4Zy2NXerf/Q6k8mRIwaYYqiBkYjNeMe3 4tn9DU7fMalp5aeAOVxqtKdkrvhxoqwRjDIvQcu9KX4ImHHeTzRmg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=bDZtw9vJ3vjTEcV2OlGTFYgYgUVSmJTXrEiPaNN8kyE=; b=CmB53AJZ X2tfDlLDM7l0Dzby0KwA9Fyrx+I7+9mHrtiiujnLeynPb9b0DiBG5lUgotaJ94iz c/hU0FziPUc4gpvhtyCu2e/dXYDpDqnXAxLxHJBNhuDowe8OsGhv6MDN99yjxBaR aNuR8DXRnHPi7mvxvKpVMnQh5pw2a6HqS0SOPMbRE+cdcgKlkEWpaqNYDzkHq7Mi Gbs6RDgQI6SNRyyqcYyNVdZxUnlN1oQi1vLlotj4aHnD3LnBvmBmbMY2qf+XdEZw 6K8GHrnmQbtGLC2kK0SiHL+kYNf2RL32hTMZi8Ki+Ch+OQA/9oaZ9dvfIPoJPdiL jn9nZOpAd4o/RA== X-ME-Sender: 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 4709424141 for ; Sat, 24 Mar 2018 08:40:01 -0400 (EDT) To: extra@ietf.org From: Ken Murchison Organization: FastMail US LLC Message-ID: <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> Date: Sat, 24 Mar 2018 08:40:00 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------037F09170011941F3C563D00" Content-Language: en-US Archived-At: Subject: [Extra] draft-ietf-extra-sieve-fcc X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 12:40:05 -0000 This is a multi-part message in MIME format. --------------037F09170011941F3C563D00 Content-Type: multipart/alternative; boundary="------------947603D0886AEB0C5E40D41C" --------------947603D0886AEB0C5E40D41C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit At the EXTRA session this week, Alexey questioned whether the way I integrated fileinto tagged arguments with :fcc was legal.  It turns out that Alexey is correct, and the current implementation breaks a SHOULD NOT in Section 2.6.2 of RFC5228: "Tagged arguments SHOULD NOT take tagged arguments as arguments." So, assuming we want to continue to allow options like :flags and :special-use to be used with :fcc (and I think we should if possible), we need to find another way to do this. Do we allow options like :flags to float anywhere in the command and simply ignore them if :fcc isn't included? E.g. vacation :days 7 :specialuse "\\Sent" :create :fcc "INBOX.Sent" :flags ["\\Seen"] :from "hemingway@example.com" "Gone Fishin'"; This seems messy and somewhat illogical to me. We can't use a block to encapsulate the fileinto options, as that is also prohibited by RFC5228. One other idea that comes to mind is to have :fcc accept a variable name as its argument into which a copy of the generated message will be stored.  We then extend fileinto to accept the variable name as the message to be filed. Thoughts? -- Ken Murchison Cyrus Development Team FastMail US LLC: --------------947603D0886AEB0C5E40D41C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

At the EXTRA session this week, Alexey questioned whether the way I integrated fileinto tagged arguments with :fcc was legal.  It turns out that Alexey is correct, and the current implementation breaks a SHOULD NOT in Section 2.6.2 of RFC5228:

"Tagged arguments SHOULD NOT take tagged arguments as arguments."

So, assuming we want to continue to allow options like :flags and :special-use to be used with :fcc (and I think we should if possible), we need to find another way to do this.

Do we allow options like :flags to float anywhere in the command and simply ignore them if :fcc isn't included?  E.g.

vacation :days 7 :specialuse "\\Sent" :create :fcc "INBOX.Sent" :flags ["\\Seen"] :from "hemingway@example.com" "Gone Fishin'";

This seems messy and somewhat illogical to me.  We can't use a block to encapsulate the fileinto options, as that is also prohibited by RFC5228.

One other idea that comes to mind is to have :fcc accept a variable name as its argument into which a copy of the generated message will be stored.  We then extend fileinto to accept the variable name as the message to be filed.

Thoughts?

-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC:
--------------947603D0886AEB0C5E40D41C-- --------------037F09170011941F3C563D00 Content-Type: text/x-vcard; name="murch.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="murch.vcf" bnVsbA== --------------037F09170011941F3C563D00-- From nobody Sat Mar 24 07:57:05 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 3DC611200F1 for ; Sat, 24 Mar 2018 07:57:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] 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 WWgt5-kh9IDV for ; Sat, 24 Mar 2018 07:57:02 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 3F6AC1201F2 for ; Sat, 24 Mar 2018 07:57:02 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQIBCBR09S00F6KJ@mauve.mrochek.com> for extra@ietf.org; Sat, 24 Mar 2018 07:51:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1521903116; bh=sM55GbzitmDfMpHJOlaxBQdeka2LLZl7khgACF+nXsQ=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=XRICl7Tc9Yn6/ozDxiYmIWIP9VGd6VM5V0eR+xl3oQb/zEu2C+MGThMuV3hdPnTv7 JuZ9x7JbrnSe+M7e5fkpNf17nVvBUGHqY5YO44n5jNf0cISU8GZFx22QcCIjgvhKgN nBXGYu/hAJ59nk2TgdFWcqnN6x6YtkPs5rHtQD+k= 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 <01QQ1J13T4YO00CZTT@mauve.mrochek.com>; Sat, 24 Mar 2018 07:51:52 -0700 (PDT) Cc: extra@ietf.org Message-id: <01QQIBC8Y8B600CZTT@mauve.mrochek.com> Date: Sat, 24 Mar 2018 07:43:20 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Sat, 24 Mar 2018 08:40:00 -0400" <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> References: <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> To: Ken Murchison Archived-At: Subject: Re: [Extra] draft-ietf-extra-sieve-fcc X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 14:57:03 -0000 > At the EXTRA session this week, Alexey questioned whether the way I > integrated fileinto tagged arguments with :fcc was legal.  It turns out > that Alexey is correct, and the current implementation breaks a SHOULD > NOT in Section 2.6.2 of RFC5228: > "Tagged arguments SHOULD NOT take tagged arguments as arguments." > So, assuming we want to continue to allow options like :flags and > :special-use to be used with :fcc (and I think we should if possible), > we need to find another way to do this. I missed the fact that you had made FCC-OPTIONS a positional parameter inside of :fcc. While I can certainly implement this, I agree that it's a bad idea. And more to the point, unnecessary since there are no cases where one of these arguments has a different meaning outside of this context. (And if there were such cases... ick.) > Do we allow options like :flags to float anywhere in the command and > simply ignore them if :fcc isn't included? E.g. Or better still, require :fcc to be present in order to use :flags or whatever. > vacation :days 7 :specialuse "\\Sent" :create :fcc "INBOX.Sent" :flags > ["\\Seen"] :from "hemingway@example.com" "Gone Fishin'"; > This seems messy and somewhat illogical to me. We can't use a block to > encapsulate the fileinto options, as that is also prohibited by RFC5228. I'm sorry, but I fail to see anything messy or illogical about this. > One other idea that comes to mind is to have :fcc accept a variable name > as its argument into which a copy of the generated message will be > stored.  We then extend fileinto to accept the variable name as the > message to be filed. Double ick. I really don't like abusing variables and/or fileinto this way, to the point where the chances I'd ever implement this are essentially zero. Ned From nobody Sat Mar 24 09:17:32 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 E1BE21243FE for ; Sat, 24 Mar 2018 09:17:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=sw6pHD/N; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Yngu84xy 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 y4Ivb0S9Fe25 for ; Sat, 24 Mar 2018 09:17:29 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 740321200C5 for ; Sat, 24 Mar 2018 09:17:29 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A4D192098A; Sat, 24 Mar 2018 12:17:28 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Sat, 24 Mar 2018 12:17:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=N3dCaKEgfGlt1pGJ8Oa8OoRyPxRR34jlRJ8f8nT33aY=; b=sw6pHD/N VrW1OWR1vaBGq8zrcLNhfsQGC8O1dGwT8GIqM8DfK48ea+MF/0sJYJU6Sf3e/Zl2 cwLmc9fwVxdcI/8k9PhlgJF5xR2ObQ3jqLT7OfXDFGmVLFvc2t4mkI8Nq4oB84gN x3hey5NI3sBQJe1xkjLR81cLZws6z/0xewNozdPg/IU4m/bLta+Wxtw87qwc/E5M 8oFI9azJASsTPjjmEDDCGy6rqjvBW2n3HQpOm6DX/uhzokc++qMS+vEUbBf/lq84 hWTx4rLDTtlracIIRL+BxQlk9jBYlpaYWmux/VOIoy+ejY2+rUWYXH1jfLsVs35d RbOiyvGqbLODdg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=N3dCaKEgfGlt1pGJ8Oa8OoRyPxRR3 4jlRJ8f8nT33aY=; b=Yngu84xyTSsGgVC+8GIwqERRKkXJiOYUdeEznPzwY/jBz ApgmSLVcgYmkR/f7ddp54pIlrq27B7a1Su6Qi7F8Cf+MeOnV+DrhBtJVizfT9InR y3BcHJJK2Obkp+DHRExymhqWM5FkK+7qpO6SjZ3uzixA6QN9xAxdtjHPT/3iw39i 4y5UAJzBRTxt9dPpMYaiKvYdO5XDNrNyi/lpPskjYoyqPDGTX2zgs1BYzC+AHDsw csw3R0YkJoBhzwMGaIRiiJv6rgq2EmIGKBJt3ECepxa7uvv0+mK1pHguv+b6swmW mCTqEnYMcQmQLjs3kVhyrR0yCcAA+I8T7qJ6Hv2JA== X-ME-Sender: 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 45558241D8; Sat, 24 Mar 2018 12:17:28 -0400 (EDT) To: Ned Freed Cc: extra@ietf.org References: <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> <01QQIBC8Y8B600CZTT@mauve.mrochek.com> From: Ken Murchison Organization: FastMail US LLC Message-ID: Date: Sat, 24 Mar 2018 12:17:27 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <01QQIBC8Y8B600CZTT@mauve.mrochek.com> Content-Type: multipart/mixed; boundary="------------B4BC3E2DD695E6680B1BC286" Content-Language: en-US Archived-At: Subject: Re: [Extra] draft-ietf-extra-sieve-fcc X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 16:17:31 -0000 This is a multi-part message in MIME format. --------------B4BC3E2DD695E6680B1BC286 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Ned, On 03/24/2018 10:43 AM, Ned Freed wrote: >> At the EXTRA session this week, Alexey questioned whether the way I >> integrated fileinto tagged arguments with :fcc was legal.  It turns out >> that Alexey is correct, and the current implementation breaks a SHOULD >> NOT in Section 2.6.2 of RFC5228: > >> "Tagged arguments SHOULD NOT take tagged arguments as arguments." > >> So, assuming we want to continue to allow options like :flags and >> :special-use to be used with :fcc (and I think we should if possible), >> we need to find another way to do this. > > I missed the fact that you had made FCC-OPTIONS a positional parameter > inside of :fcc. While I can certainly implement this, I agree that it's > a bad idea. And more to the point, unnecessary since there are no > cases where one of these arguments has a different meaning outside > of this context. (And if there were such cases... ick.) I only did that so that the parser would know ahead of time to expect the fileinto options.  Instead, the parser will have to expect those options to occur anywhere, possibly prior to parsing :fcc, and validate the command at the end. >> Do we allow options like :flags to float anywhere in the command and >> simply ignore them if :fcc isn't included? E.g. > > Or better still, require :fcc to be present in order to use :flags or > whatever. Right.  And if they are used without :fcc, its a parse error. I will make the necessary changes and post a new draft. -- Ken Murchison Cyrus Development Team FastMail US LLC --------------B4BC3E2DD695E6680B1BC286 Content-Type: text/x-vcard; name="murch.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="murch.vcf" bnVsbA== --------------B4BC3E2DD695E6680B1BC286-- From nobody Sat Mar 24 10:03:20 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 71C3D126D05 for ; Sat, 24 Mar 2018 10:03:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=mailforce.net header.b=FE03BXpq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RXBWAPWw 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 ALJ8TYWkWgD4 for ; Sat, 24 Mar 2018 10:03:18 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E449124BFA for ; Sat, 24 Mar 2018 10:03:18 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7EB1820D76 for ; Sat, 24 Mar 2018 13:03:17 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sat, 24 Mar 2018 13:03:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=RNxnfYBlN0lfjIUkZWiJxeyI0Pbzi hSpYC8RWpPn5is=; b=FE03BXpqCYbmX3DxhZbpDfYltUMAzMveYZK8Jyb8HCGnq t8NyKcTlFz8BTmIPvMsz1ZMNsLNBS44XRSXPpnAzYvgy4b3wi1BDDleUMVCnNsls ujEU6oOgCTzuUiNnej5ikbbVWVpxblXRxan6AZU+F4Y3ClD2QJfaqpLbenytPNV1 YddaUudo1IiRkNj6UWouIF7o4ilq0wrHijKILFUjYP1uWKL/49LYDqXuK2MhE03y XvY3Kw/O2r3rT4VvgmNBjSWxsNd6fRyjmD1Q+NjjzoblA0uTO7w64iFizBnH3RNK m5H6M+MYM7xiehRwoHpLrIwqpPDBK31talNAoZRUg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=RNxnfY BlN0lfjIUkZWiJxeyI0PbzihSpYC8RWpPn5is=; b=RXBWAPWw85QOIlYiN7q5dC JO1/P8AtXghtOYhJOug38zl8f3rrGamK3VWOuF8LyCCTiBxvkvieDnhvTjrHzF25 D2jnA4twe+YFlfsqLaWMi1GnxRHsAq6K0IIiEKUXaIzpZS6AKDwPr5yApOWQaoG0 wPvpgO7bw7VA+KpShUlTNVvT/JEvTvnWUwEC8TocudlX/H+RZo+lH0RuO+dNGhdc qFTZtY529pYm720Lx6pFW7gYlMLWTT/0gi3a3Bs4YOMC0N44EvEkpJGmMhnKQqx5 OCCcscw6/wL82/S+rDacubdjc+o6WPm1TAqz8a2Sm///++kBlG2IdAQnHSQyuzgw == X-ME-Sender: Received: from [192.168.1.71] (108-84-31-27.lightspeed.tukrga.sbcglobal.net [108.84.31.27]) by mail.messagingengine.com (Postfix) with ESMTPA id 377FD7E168 for ; Sat, 24 Mar 2018 13:03:17 -0400 (EDT) References: <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> <01QQIBC8Y8B600CZTT@mauve.mrochek.com> From: Stan Kalisch Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (13G36) In-Reply-To: <01QQIBC8Y8B600CZTT@mauve.mrochek.com> Message-Id: <20833435-7A0D-407B-9972-7482D5589E4E@glyphein.mailforce.net> Date: Sat, 24 Mar 2018 13:03:14 -0400 To: extra@ietf.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Archived-At: Subject: Re: [Extra] draft-ietf-extra-sieve-fcc X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 17:03:19 -0000 Hi, On Mar 24, 2018, at 10:43 AM, Ned Freed wrote: >> One other idea that comes to mind is to have :fcc accept a variable name >> as its argument into which a copy of the generated message will be >> stored. We then extend fileinto to accept the variable name as the >> message to be filed. >=20 > Double ick. I really don't like abusing variables and/or fileinto this way= , to > the point where the chances I'd ever implement this are essentially zero. +1, particularly WRT variables being employed in this manner in this or any o= ther context. Thanks, Stan= From nobody Sat Mar 24 13:03:26 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 E4FCC12D7F0; Sat, 24 Mar 2018 13:03:23 -0700 (PDT) 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.76.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152192180388.29912.16078530981701726309@ietfa.amsl.com> Date: Sat, 24 Mar 2018 13:03:23 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-status-size-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 20:03:24 -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 : Internet Message Access Protocol (IMAP) - STATUS=SIZE Extension Author : Stephan Bosch Filename : draft-ietf-extra-imap-status-size-01.txt Pages : 5 Date : 2018-03-24 Abstract: This document adds a new capability called "STATUS=SIZE" to the Internet Message Access Protocol (IMAP). It allows retrieving the total storage size of a mailbox with a single STATUS command rather than retrieving and summing the sizes of all individual messages in that mailbox. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-status-size/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-status-size-01 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-status-size-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap-status-size-01 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 Sat Mar 24 13:11:29 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 90E07126CB6 for ; Sat, 24 Mar 2018 13:11:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_FAIL=0.001] autolearn=no 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 A5Cc5T5kUBR4 for ; Sat, 24 Mar 2018 13:11:27 -0700 (PDT) Received: from mail.dovecot.fi (6416-b0ff-fec5-750d.v6.fi-hel1.host.upcloud.com [IPv6:2a04:3540:1000:310:6416:b0ff:fec5:750d]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF3D12D7EF for ; Sat, 24 Mar 2018 13:11:27 -0700 (PDT) Received: from [10.168.3.2] (klara.student.utwente.nl [130.89.162.218]) by mail.dovecot.fi (Postfix) with ESMTPSA id 05AE42AEF55 for ; Sat, 24 Mar 2018 22:11:24 +0200 (EET) To: extra@ietf.org References: <152192180388.29912.16078530981701726309@ietfa.amsl.com> From: Stephan Bosch Message-ID: Date: Sat, 24 Mar 2018 21:11:22 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <152192180388.29912.16078530981701726309@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Extra] I-D Action: draft-ietf-extra-imap-status-size-01.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 20:11:29 -0000 Op 3/24/2018 om 9:03 PM schreef internet-drafts@ietf.org: > 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 : Internet Message Access Protocol (IMAP) - STATUS=SIZE Extension > Author : Stephan Bosch > Filename : draft-ietf-extra-imap-status-size-01.txt > Pages : 5 > Date : 2018-03-24 > > Abstract: > This document adds a new capability called "STATUS=SIZE" to the > Internet Message Access Protocol (IMAP). It allows retrieving the > total storage size of a mailbox with a single STATUS command rather > than retrieving and summing the sizes of all individual messages in > that mailbox. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-extra-imap-status-size/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-extra-imap-status-size-01 > https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-status-size-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap-status-size-01 > > > 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/ The following changes were applied since ietf-draft-00 (see git for details): * Weaken the definition of the SIZE item to be greater than or equal to the total message sizes. It was defined as strictly equal before. It now also mentions that this SHOULD be equal to the value used for QUOTA enforcement. * Section 3: Remove spurious space in LIST response in LIST-STATUS example. * Remove FIXME regarding interaction with 64BIT capability. This is already handled implicitly. Regards, Stephan. -- Stephan Bosch Senior Developer Phone: +49 2761 75252 00 Fax: +49 2761 75252 30 Email: stephan.bosch@dovecot.fi ------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt Dovecot Oy, Lars Sonckin Kaari 10, 02600 Espoo, Finland Managing Director: Markku Kentta Chairman of the Board: Timo Sirainen Board Member: Carsten Dirks ------------------------------------------------------------------------------------- From nobody Sat Mar 24 14:11:09 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 7E870126BF7 for ; Sat, 24 Mar 2018 14:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] 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 45yU-cbqa3Cq for ; Sat, 24 Mar 2018 14:11:06 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 496DC1204DA for ; Sat, 24 Mar 2018 14:11:06 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQIOF20OAO00HC1B@mauve.mrochek.com> for extra@ietf.org; Sat, 24 Mar 2018 14:05:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1521925559; bh=YOvuKACobdkIaK48vkq4i6ikUPCLsCWAl0GAQVXqqxw=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=I+pw9ftGlmFOHPCagZNUIZA6c05QpLWV8lhdBxp/ArBF5QSIZ4Y9i6r4J4SxgEQmD 4IW8kDRWuJTyqA0y4C4NxYj4Eo/NE4N/PEPHqmXxoP5/WJ3DTECcs7LJwWpwITzvUF 5eiPfMLcRfJwhlmWgm0JScEwBUSXM1ygbs3+lAos= 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 <01QQ1J13T4YO00CZTT@mauve.mrochek.com>; Sat, 24 Mar 2018 14:05:54 -0700 (PDT) Cc: Ned Freed , extra@ietf.org Message-id: <01QQIOEYKZAG00CZTT@mauve.mrochek.com> Date: Sat, 24 Mar 2018 13:50:55 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Sat, 24 Mar 2018 12:17:27 -0400" References: <0de6594d-2b11-aede-7c98-0e05a585f97d@fastmail.com> <01QQIBC8Y8B600CZTT@mauve.mrochek.com> To: Ken Murchison Archived-At: Subject: Re: [Extra] draft-ietf-extra-sieve-fcc X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Sat, 24 Mar 2018 21:11:07 -0000 > Hi Ned, > On 03/24/2018 10:43 AM, Ned Freed wrote: > >> At the EXTRA session this week, Alexey questioned whether the way I > >> integrated fileinto tagged arguments with :fcc was legal.  It turns out > >> that Alexey is correct, and the current implementation breaks a SHOULD > >> NOT in Section 2.6.2 of RFC5228: > > > >> "Tagged arguments SHOULD NOT take tagged arguments as arguments." > > > >> So, assuming we want to continue to allow options like :flags and > >> :special-use to be used with :fcc (and I think we should if possible), > >> we need to find another way to do this. > > > > I missed the fact that you had made FCC-OPTIONS a positional parameter > > inside of :fcc. While I can certainly implement this, I agree that it's > > a bad idea. And more to the point, unnecessary since there are no > > cases where one of these arguments has a different meaning outside > > of this context. (And if there were such cases... ick.) > I only did that so that the parser would know ahead of time to expect > the fileinto options.  Instead, the parser will have to expect those > options to occur anywhere, possibly prior to parsing :fcc, and validate > the command at the end. Does this really differ from the present situation? For example, in the case of the imap4flags extension, you have to parse the entire parameter list in order to determine whether or not there are one or two positional parameters at the end, and if there are two check to make sure the variables extension is enabled. There are also many nonpositional parameters that are mutually exclusive so you have to check and make sure only one is specified. There's also at least one existing case where one nonpositional precludes the use of another: :list and :comparator. Ned From nobody Sun Mar 25 19:43:10 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 73AF2124217 for ; Sun, 25 Mar 2018 19:43:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 EAlh7mww_92v for ; Sun, 25 Mar 2018 19:43:06 -0700 (PDT) Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB5D1242EA for ; Sun, 25 Mar 2018 19:43:03 -0700 (PDT) Received: from healthyao-PC (unknown [159.226.7.2]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0A5QNArXrhaICjhAA--.50595S2; Mon, 26 Mar 2018 10:42:58 +0800 (CST) Date: Mon, 26 Mar 2018 10:42:59 +0800 From: "Jiankang Yao" To: extra Reply-To: yaojk X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.92[cn] Mime-Version: 1.0 Message-ID: <2018032610414401508024@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart148185173023_=----" X-CM-TRANSID: AQAAf0A5QNArXrhaICjhAA--.50595S2 X-Coremail-Antispam: 1UD129KBjvdXoWrKryUGr48tF15Gr1DWw1xXwb_yoWfZwcEya yagFWrt3yDtwsrCr4rGrWfK3sa9ayavr17Aw45JrsrCrWFyan3XFWSkFn3J3WUJF1Uua17 Jr1Sq34furyagjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUb38YjsxI4VWxJwAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVW5JVW7JwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVW8JVWxJwA2z4x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjcxK6I 8E87Iv6xkF7I0E14v26F4UJVW0owAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40E42I2 6xC2a48xMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4I kC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7xC0wCY02Av z4vE14v_Gr1l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4 xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1j6r15 MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I 0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v2 6r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_Gr1l6VACY4xI67k04243AbIYCTnIWI evJa73UjIFyTuYvjxU7CD7DUUUU X-CM-SenderInfo: x1dryyw6fq0xffof0/ Archived-At: Subject: [Extra] Fw: IETF WG state changed for draft-ietf-extra-imap-list-myrights X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 26 Mar 2018 02:43:08 -0000 This is a multi-part message in MIME format. ------=_001_NextPart148185173023_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBhbGwsDQogDQogICAgICAgR2VudGxlIHJlbWluZGVyLg0KICAgICAgIFRoaXMgZHJhZnQg d2lsbCBiZSBpbiBXRyBsYXN0IGNhbGwgZm9yIDMgd2Vla3MsIHdoaWNoIGVuZHMgaW4gMTYgQXBy aWwuDQoNCiAgICAgICBBbnkgY29tbWVudHMgYXJlIHdlbGNvbWUuDQoNCiAgICAgICBUaGFua3Mg YSBsb3QuDQoNCg0KDQpKaWFua2FuZyBZYW8NCg0KRnJvbTogSUVURiBTZWNyZXRhcmlhdA0KRGF0 ZTogMjAxOC0wMy0yNiAxMDoxNQ0KVG86IHlhb2prQGNubmljLmNuOyBkcmFmdC1pZXRmLWV4dHJh LWltYXAtbGlzdC1teXJpZ2h0c0BpZXRmLm9yZzsgZXh0cmEtY2hhaXJzQGlldGYub3JnDQpTdWJq ZWN0OiBJRVRGIFdHIHN0YXRlIGNoYW5nZWQgZm9yIGRyYWZ0LWlldGYtZXh0cmEtaW1hcC1saXN0 LW15cmlnaHRzDQoNClRoZSBJRVRGIFdHIHN0YXRlIG9mIGRyYWZ0LWlldGYtZXh0cmEtaW1hcC1s aXN0LW15cmlnaHRzIGhhcyBiZWVuIGNoYW5nZWQgdG8NCiJJbiBXRyBMYXN0IENhbGwiIGZyb20g IldHIERvY3VtZW50IiBieSBKaWFua2FuZyBZYW86DQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0 Zi5vcmcvZG9jL2RyYWZ0LWlldGYtZXh0cmEtaW1hcC1saXN0LW15cmlnaHRzLw0KDQpDb21tZW50 Og0KVGhlIEVYVFJBIFdHIG1lZXRpbmcgaW4gSUVURiAxMDEgaWRlbnRpZmllZCB0d28gaXRlbXMg dG8gYmUgZml4ZWQ6DQpodHRwczovL2dpdGh1Yi5jb20vaWV0ZmV4dHJhL3RyYWNraW5nL2lzc3Vl cy8xNw0KaHR0cHM6Ly9naXRodWIuY29tL2lldGZleHRyYS90cmFja2luZy9pc3N1ZXMvMTgNCg0K VGhlIGF1dGhvcnMgaGF2ZSBmaXhlZCBib3RoIG9mIHRoZXNlICBhbmQgdXBsb2FkZWQgYSBuZXcg dmVyc2lvbjoNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWV4dHJhLWlt YXAtbGlzdC1teXJpZ2h0cy0wMg== ------=_001_NextPart148185173023_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Dear all,
 
       Gentle reminder.
       This draft will be in WG last ca= ll for=20 3 weeks, which ends in 16 April.
 
       Any comments are welcome.
 
       Thanks a lot.
Jiankang Yao
 
Date: 2018-03-26 10:15
To: yaojk@cnnic.cn;= draft-ietf-ex= tra-imap-list-myrights@ietf.org;=20 extra-chairs@ietf.org
Subject: IETF WG state changed for=20 draft-ietf-extra-imap-list-myrights
 
The IETF WG state of draft-ietf-extra-imap-l= ist-myrights has been changed to
"In WG Last Call" from "WG Document"&nb= sp;by Jiankang Yao:
 
https://datatracker.ietf.org/doc/draft-ietf-extra-imap-list-myrights/=
 
Comment:
The EXTRA WG meeting in IETF 101 i= dentified two items to be fixed:
https://github.com/ietfextra/tracking/issues/17
https://github.com/ietfextra/tracking/issues/18
 
The authors have fixed both of these&nb= sp; and uploaded a new version:
https://tools.ietf.org/html/draft-ietf-extra-imap-list-myrights-02
------=_001_NextPart148185173023_=------ From nobody Mon Mar 26 02:42:37 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 1659B126B6E; Mon, 26 Mar 2018 02:42:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=gmail.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 Dth1HqndLSeJ; Mon, 26 Mar 2018 02:42:34 -0700 (PDT) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6658A1200B9; Mon, 26 Mar 2018 02:42:31 -0700 (PDT) Received: by mail-io0-x22c.google.com with SMTP id d7so7093403ioc.11; Mon, 26 Mar 2018 02:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=wK8OCSDzIUF5+PvyrsRs5SoluCedYRSts4zkl70RLQ0=; b=Cz+TDtVxV5AhuSHDX9LdeYTp/MGyix6w5+6p9GJWw8B5idTA/HwFD9niTADZfM3wvN z/f4oUtpjgWGp4rsoiANlJpFL4hXP0tA/UDTkVOSY7DYnTQDO+qYR8SQ5db1sTmwyUsF I/BxdI7Gz5NtYL7fatcUwuAUoo6qviv+YvAlgYCeJuf20AF25LpMJtC4A/WFRgOhxgi2 cJ6xZ8I6DXCOLEuDbB5T7G+pfQnP1Ttz3XbxUyiQVPEUajd+jyqHmc4kbgKUjUvKPii2 B3sG9+t7tI4I+Rf54SDqVJu6RVx+mlQd+7Ujwl+bSwiQnIcwO1vnUW+aV+bDmveq+jtN zvWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc:content-transfer-encoding; bh=wK8OCSDzIUF5+PvyrsRs5SoluCedYRSts4zkl70RLQ0=; b=CrshvdNHDIlnqODEOKkb/vgokk6a7xW+SIAmSczOpI18zIjit+FL165c6mMA5HepDQ Rxf72rfCoI47aMfAHMkTTFxaBGz9h76jUQOAb5t5HVKEf0uh/zSjS/OfQgVOzpSy6LAX g9p6GGMzHGlVBJiwEVpwcZhWCGCU29ty9PBI0mYGJbwZhxEnWcA6ZM/ylj9loeKEiHFQ YlO4wtkEnP2pWDmaFiqcSfCFrQYEhrkkxnzJrR135QXAqnRH24lzgD+CnCymrjmAfWRF fyxwiiNblvyjJtSTL4J5E5v+Ujkha1EBNr5ZwF46DeytY62xphwKpdr87hZUvb53FZvr q0nA== X-Gm-Message-State: AElRT7Hn0TgzuBQ9AI968P6gKQ56+/0dlkVkOKMkAOjF877EGbdnWp8P QHRqx1q7P2nKcYERyP7qmyqM8oITUYRc/onk6WYT4dfh X-Google-Smtp-Source: AG47ELtaDwhojBsfwz0IHHZufprg5QODjc0L1P/jQskmju0TFWukpPC4y2M7fwu7ivXQraxokxnVgHoXDs396tnuOuI= X-Received: by 10.107.6.163 with SMTP id f35mr33672949ioi.165.1522057350333; Mon, 26 Mar 2018 02:42:30 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba@gmail.com Received: by 10.192.142.161 with HTTP; Mon, 26 Mar 2018 02:42:29 -0700 (PDT) From: Barry Leiba Date: Mon, 26 Mar 2018 11:42:29 +0200 X-Google-Sender-Auth: UpkDIVHgX4GvEEQJBQDElH-lW1k Message-ID: To: draft-ietf-extra-imap-list-myrights.all@ietf.org Cc: extra@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 26 Mar 2018 09:42:36 -0000 The document's in very good shape and is almost ready. I have a couple of minor points below. =E2=80=94 Section 3 =E2=80=94 For each listable mailbox matching the list pattern and selection options, the server MUST return an untagged LIST response followed by an untagged MYRIGHTS response containing the set of rights granted to the logged-in user. We don=E2=80=99t usually specify any particular ordering for untagged responses, and for the most part, ordering is not significant. I presume it=E2=80=99s not significant here, and that both of the following would be equally acceptable to a client: C: A01 LIST "" % RETURN (MYRIGHTS) S: * LIST () "." "INBOX" S: * MYRIGHTS "INBOX" lrswipkxtecda S: * LIST () "." "foo" S: * MYRIGHTS "foo" lrs S: A01 OK List completed. C: A01 LIST "" % RETURN (MYRIGHTS) S: * LIST () "." "INBOX" S: * LIST () "." "foo" S: * MYRIGHTS "foo" lrs S: * MYRIGHTS "INBOX" lrswipkxtecda S: A01 OK List completed. Now, one wonders whether this would also be acceptable: C: A01 LIST "" % RETURN (MYRIGHTS) S: * MYRIGHTS "foo" lrs S: * MYRIGHTS "INBOX" lrswipkxtecda S: * LIST () "." "INBOX" S: * LIST () "." "foo" S: A01 OK List completed. =E2=80=A6as a client might not be happy seeing MYRIGHTS responses for mailboxes for which it has not yet seen a LIST response. Also, the MUST attached to the production of the MYRIGHTS response is contradicted by the MAY in the next paragraph. I think we shouldn=E2=80=99t imply that the responses have to be interleave= d, and we should point out that the MYRIGHTS response for a given mailbox can=E2=80=99t precede the LIST response for that mailbox. Maybe this?: NEW For each listable mailbox matching the list pattern and selection options, the server MUST return an untagged LIST response and SHOULD also return an untagged MYRIGHTS response containing the set of rights granted to the logged-in user. The ordering of the responses is significant only in that the server MUST NOT send a MYRIGHTS for a given mailbox before it sends that mailbox=E2=80=99s LIST response. END Now, as to the following paragraph that explains the SHOULD: If the server is unable to look up the set of rights for a given mailbox, it MAY drop the corresponding MYRIGHTS reply. What else could it do? If there are other reasonable choices, we should say what they are. If not, we shouldn=E2=80=99t imply that there ar= e. And it=E2=80=99s not really a MAY; the server has to do something reasonabl= e, so I suggest one of the following: NEW-1 If the server is unable to look up the set of rights for a given mailbox, it does not send the MYRIGHTS reply for that mailbox. END NEW-2 If the server is unable to look up the set of rights for a given mailbox, it either does not send the MYRIGHTS reply for that mailbox or <=E2=80=94fill in other possible actions here=E2=80=94>. END =E2=80=94 Section 8 =E2=80=94 It=E2=80=99s always a good idea to give IANA the full name of the registry, rather than citing where the registry is defined (this is highlighted by the fact that there are two registries =E2=80=9Cdefined in Section 9 of [RFC5258]=E2=80=9D): OLD This document defines the "LIST-MYRIGHTS" IMAP capability to be added to the registry defined in Section 12 of [RFC3501]. NEW This document defines the "LIST-MYRIGHTS" IMAP capability to be added to the =E2=80=9CIMAP Capabilities=E2=80=9D registry: END OLD This section registers the "MYRIGHTS" option to be added to the registry defined in Section 9 of [RFC5258]. NEW This section registers the "MYRIGHTS" option to be added to the =E2=80=9CLIST-EXTENDED options=E2=80=9D registry: END =E2=80=94 Section 10.2 =E2=80=94 I find it somewhat odd to have a formal reference to 5819 (implying that there=E2=80=99s something in there that the reader might find useful i= n reading this one), when it=E2=80=99s only used in the Acknowledgments. I suggest changing the Acks to just say =E2=80=9CRFC 5819=E2=80=9D (plain tex= t, not as a citation), and removing the informative reference. --=20 Barry From nobody Mon Mar 26 02:57:45 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 A8161126B6E; Mon, 26 Mar 2018 02:57:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=gmail.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 hv5SQLqbIKN8; Mon, 26 Mar 2018 02:57:41 -0700 (PDT) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C6B91200B9; Mon, 26 Mar 2018 02:57:38 -0700 (PDT) Received: by mail-io0-x22e.google.com with SMTP id q84so17043408iod.10; Mon, 26 Mar 2018 02:57:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=BP64zNHKPK5K2I+8v/9X237QDmXDfzpYJcHTPHOCEvo=; b=Hto3jel/0ri+zois3qOc3PFYebApE5Z+MWR1LtsoWuj6VxkBqsfHMXAHifxM5NuZRX nPLkn9L0ib+E9sW+3je6TYKGZ1/qH1tyExQXfxl0CcHq6DefhssravOHSq9rUifjJ4w0 4jmHwDhiBlbd8zf9WK8R7hC3EmHouNFdj0MP8s3hqzYZK+xPfm20mHENayZFHNVTwhCX k5y9oLr4zdRbQSphOcUeNNXVrejHjUEdAk/4uECJX+QK+DXXNQZaQhrWcGZLLyFYylZo 2gVgrevtH86sedfTE5X3uQM9xBjrgjYMWHvHctdZv3FCfuhIkgjktpEhEWE7zpFWj//B euRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc; bh=BP64zNHKPK5K2I+8v/9X237QDmXDfzpYJcHTPHOCEvo=; b=Q4omcbtW0FUvOGsmfkFG5Wj+heflSRe9oOQBmoAiLFHGVzW0z0XAxYpNen7B8njowW OTgjDRdCVRboiWAoYl24gpne+tVR3xwkU+RMfFv1OVENe1IfPDc38+UsZt5wSlgjnEBf qTtI1MEDDaWhHUiHCbXyiDa6Ly8cJ39ZwmzLiNN0aiIeUdHjEUB3B8gfIu6DeOUA0Bvp nUzqGJR2PdYa/EuAMAzQyx+MKh7Ug7PxSsOh9OvBoV9jUMD+9rDdk8ichMcu2FJmg8UA 8HCekZba3FYafBmapt38UvaA5BHTNGAMl++PhitoONtCgrwcFZanCeDf6DQdgDmY74qO 0zmA== X-Gm-Message-State: AElRT7F4ZqiUbVtSmZols4VwPjsmIjEU5Yd0VFhu5U1C1sd0PrG+f9wZ ZnjB0/ki2evEmPD9TqAsCP+/OLfcez8rm+j2MekEszNk X-Google-Smtp-Source: AIpwx4/PIQujQ/pWFueGdcT9TgcTvel8DC825S3aEjarf0vOXkOGuvyNBaWPgcpiPwlf/QRDSD9tSGRaargYwxw1sRg= X-Received: by 10.107.140.86 with SMTP id o83mr23672223iod.114.1522058257275; Mon, 26 Mar 2018 02:57:37 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba@gmail.com Received: by 10.192.142.161 with HTTP; Mon, 26 Mar 2018 02:57:36 -0700 (PDT) From: Barry Leiba Date: Mon, 26 Mar 2018 11:57:36 +0200 X-Google-Sender-Auth: QrS_rcuGl9wWFXkQvTc_2N91D08 Message-ID: To: draft-ietf-extra-imap-status-size.all@ietf.org Cc: extra@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Extra] WGLC review of draft-ietf-extra-imap-status-size-01 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 26 Mar 2018 09:57:43 -0000 This one's ready; I have no issues with any of the text. I do have a question, though: This is the first extension to add "STATUS" items. Should we be making a registry of them? Or is the presence of "STATUS=SIZE" in the capabilities list enough, and we shouldn't do another registry? -- Barry From nobody Mon Mar 26 05:38:22 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 543AD127201 for ; Mon, 26 Mar 2018 05:38:21 -0700 (PDT) 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=ClZn0aoh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Cb5zeOhF 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 7qDDneCxKm6j for ; Mon, 26 Mar 2018 05:38:17 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5AFD124205 for ; Mon, 26 Mar 2018 05:38:17 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E217420C2A for ; Mon, 26 Mar 2018 08:38:16 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 26 Mar 2018 08:38:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=xwzzPBtUnH5dVUURMr3nfXJzJZirmY603NhQ45WtCe4=; b=ClZn0aoh LFGGLrfH5A7WvwyO17QcWqHq7g7isQHbVmN6a5CEFEVLeQQp75HBKQqN/2/+WGtq 014l2GaU3NajEJbKotZC2L0JWfmAwVwsk4Jzjdm2GUBgJGIgvtnBkSRq4AS9+Y60 Cvd4p+7KquOLutZe29W5HWpzQz8OdiqB1hBJZUjyC4RZSEpbjOUWs4U1a4bHBojZ 80C1LHCWQBAP10WbhTUtvS5LaaIPuVob9Qx1L7Gro9rGuarCQ85T/y3wmUOal8ju cv7h8ooL3ondNyrQOTUl1ctY8ZkIPeaTkTGhV3T8b3pQLhlzgzs8E39a00A9EW3z sJTTcAEGo86/eg== 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-sender :x-me-sender:x-sasl-enc; s=fm2; bh=xwzzPBtUnH5dVUURMr3nfXJzJZirm Y603NhQ45WtCe4=; b=Cb5zeOhF0YaQIJeZhW0uMkje0FIi7rI+lWOAbHML/RF4S 3aIH2lD+3JOSGgfEPLcg5V1xDP2b473cUCklGorx8e2CZxTMYpduJumr2C9nBJrO 1nOXsuj6UB3IDqD9uRq9P9g1ZqcC55vSmqb9bMl+EdczaLqbg4IkFZe86p3GO7/J ribRIv4PZAPNvjSM1SlqtrGRsoh/fMLx9mF+WPD1gzpbJxm0/IEUpXj644NQ/98p IHERagi6PywJTVq9vb8wHWjKOKYMcv6fFgBVKdi8w/klmwVm+QQtFylBGRhERd01 4Wq065xpNn+E8x9HMs91sSdN8gY0dCPHsYjHqHxxg== X-ME-Sender: Received: from localhost.localdomain (248.sub-70-195-140.myvzw.com [70.195.140.248]) by mail.messagingengine.com (Postfix) with ESMTPA id 8227BE4488 for ; Mon, 26 Mar 2018 08:38:16 -0400 (EDT) To: extra@ietf.org References: From: Ken Murchison Organization: FastMail US LLC Message-ID: <5419ed87-0778-25d3-e6b3-7e3919a2c6e2@fastmail.com> Date: Mon, 26 Mar 2018 08:38:13 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------B33E0574DA6704E400A08990" Content-Language: en-US Archived-At: Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 26 Mar 2018 12:38:21 -0000 This is a multi-part message in MIME format. --------------B33E0574DA6704E400A08990 Content-Type: multipart/alternative; boundary="------------FFAF7E8677A8C06D4A50B934" --------------FFAF7E8677A8C06D4A50B934 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Barry, Thanks for the review.  Changes have been made in the working copy: https://github.com/ietfextra/tracking/commit/436c8e56970cdf4bef73cbd887c1ee4eaf55b85d On 03/26/2018 05:42 AM, Barry Leiba wrote: > The document's in very good shape and is almost ready. I have a > couple of minor points below. > > — Section 3 — > > For each listable mailbox matching > the list pattern and selection options, the server MUST return an > untagged LIST response followed by an untagged MYRIGHTS response > containing the set of rights granted to the logged-in user. > > We don’t usually specify any particular ordering for untagged > responses, and for the most part, ordering is not significant. I > presume it’s not significant here, and that both of the following > would be equally acceptable to a client: > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * LIST () "." "INBOX" > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: * LIST () "." "foo" > S: * MYRIGHTS "foo" lrs > S: A01 OK List completed. > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * LIST () "." "INBOX" > S: * LIST () "." "foo" > S: * MYRIGHTS "foo" lrs > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: A01 OK List completed. > > Now, one wonders whether this would also be acceptable: > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * MYRIGHTS "foo" lrs > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: * LIST () "." "INBOX" > S: * LIST () "." "foo" > S: A01 OK List completed. > > …as a client might not be happy seeing MYRIGHTS responses for > mailboxes for which it has not yet seen a LIST response. > > Also, the MUST attached to the production of the MYRIGHTS response is > contradicted by the MAY in the next paragraph. > > I think we shouldn’t imply that the responses have to be interleaved, > and we should point out that the MYRIGHTS response for a given mailbox > can’t precede the LIST response for that mailbox. Maybe this?: > > NEW > For each listable mailbox matching > the list pattern and selection options, the server MUST return an > untagged LIST response and SHOULD also return an untagged MYRIGHTS > response containing the set of rights granted to the logged-in user. > The ordering of the responses is significant only in that the server > MUST NOT send a MYRIGHTS for a given mailbox before it sends that > mailbox’s LIST response. > END > > Now, as to the following paragraph that explains the SHOULD: > > If the server is unable to look up the set of rights for a given > mailbox, it MAY drop the corresponding MYRIGHTS reply. > > What else could it do? If there are other reasonable choices, we > should say what they are. If not, we shouldn’t imply that there are. > And it’s not really a MAY; the server has to do something reasonable, > so I suggest one of the following: > > NEW-1 > If the server is unable to look up the set of rights for a given > mailbox, it does not send the MYRIGHTS reply for that mailbox. > END > > NEW-2 > If the server is unable to look up the set of rights for a given > mailbox, it either does not send the MYRIGHTS reply for that > mailbox or <—fill in other possible actions here—>. > END > > — Section 8 — > It’s always a good idea to give IANA the full name of the registry, > rather than citing where the registry is defined (this is highlighted > by the fact that there are two registries “defined in Section 9 of > [RFC5258]”): > > OLD > This document defines the "LIST-MYRIGHTS" IMAP capability to be added > to the registry defined in Section 12 of [RFC3501]. > NEW > This document defines the "LIST-MYRIGHTS" IMAP capability to be added > to the “IMAP Capabilities” registry: > > END > > OLD > This section registers the "MYRIGHTS" option to be added to the > registry defined in Section 9 of [RFC5258]. > NEW > This section registers the "MYRIGHTS" option to be added to the > “LIST-EXTENDED options” registry: > > END > > — Section 10.2 — > I find it somewhat odd to have a formal reference to 5819 (implying > that there’s something in there that the reader might find useful in > reading this one), when it’s only used in the Acknowledgments. I > suggest changing the Acks to just say “RFC 5819” (plain text, not as a > citation), and removing the informative reference. > -- Ken Murchison Cyrus Development Team FastMail US LLC --------------FFAF7E8677A8C06D4A50B934 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi Barry,

Thanks for the review.  Changes have been made in the working copy:

https://github.com/ietfextra/tracking/commit/436c8e56970cdf4bef73cbd887c1ee4eaf55b85d



On 03/26/2018 05:42 AM, Barry Leiba wrote:
The document's in very good shape and is almost ready.  I have a
couple of minor points below.

— Section 3 —

   For each listable mailbox matching
   the list pattern and selection options, the server MUST return an
   untagged LIST response followed by an untagged MYRIGHTS response
   containing the set of rights granted to the logged-in user.

We don’t usually specify any particular ordering for untagged
responses, and for the most part, ordering is not significant.  I
presume it’s not significant here, and that both of the following
would be equally acceptable to a client:

   C: A01 LIST "" % RETURN (MYRIGHTS)
   S: * LIST () "." "INBOX"
   S: * MYRIGHTS "INBOX" lrswipkxtecda
   S: * LIST () "." "foo"
   S: * MYRIGHTS "foo" lrs
   S: A01 OK List completed.

   C: A01 LIST "" % RETURN (MYRIGHTS)
   S: * LIST () "." "INBOX"
   S: * LIST () "." "foo"
   S: * MYRIGHTS "foo" lrs
   S: * MYRIGHTS "INBOX" lrswipkxtecda
   S: A01 OK List completed.

Now, one wonders whether this would also be acceptable:

   C: A01 LIST "" % RETURN (MYRIGHTS)
   S: * MYRIGHTS "foo" lrs
   S: * MYRIGHTS "INBOX" lrswipkxtecda
   S: * LIST () "." "INBOX"
   S: * LIST () "." "foo"
   S: A01 OK List completed.

…as a client might not be happy seeing MYRIGHTS responses for
mailboxes for which it has not yet seen a LIST response.

Also, the MUST attached to the production of the MYRIGHTS response is
contradicted by the MAY in the next paragraph.

I think we shouldn’t imply that the responses have to be interleaved,
and we should point out that the MYRIGHTS response for a given mailbox
can’t precede the LIST response for that mailbox.  Maybe this?:

NEW
   For each listable mailbox matching
   the list pattern and selection options, the server MUST return an
   untagged LIST response and SHOULD also return an untagged MYRIGHTS
   response containing the set of rights granted to the logged-in user.
   The ordering of the responses is significant only in that the server
   MUST NOT send a MYRIGHTS for a given mailbox before it sends that
   mailbox’s LIST response.
END

Now, as to the following paragraph that explains the SHOULD:

   If the server is unable to look up the set of rights for a given
   mailbox, it MAY drop the corresponding MYRIGHTS reply.

What else could it do?  If there are other reasonable choices, we
should say what they are.  If not, we shouldn’t imply that there are.
And it’s not really a MAY; the server has to do something reasonable,
so I suggest one of the following:

NEW-1
   If the server is unable to look up the set of rights for a given
   mailbox, it does not send the MYRIGHTS reply for that mailbox.
END

NEW-2
   If the server is unable to look up the set of rights for a given
   mailbox, it either does not send the MYRIGHTS reply for that
   mailbox or <—fill in other possible actions here—>.
END

— Section 8 —
It’s always a good idea to give IANA the full name of the registry,
rather than citing where the registry is defined (this is highlighted
by the fact that there are two registries “defined in Section 9 of
[RFC5258]”):

OLD
   This document defines the "LIST-MYRIGHTS" IMAP capability to be added
   to the registry defined in Section 12 of [RFC3501].
NEW
   This document defines the "LIST-MYRIGHTS" IMAP capability to be added
   to the “IMAP Capabilities” registry:
   <https://www.iana.org/assignments/imap-capabilities#imap-capabilities-1>
END

OLD
   This section registers the "MYRIGHTS" option to be added to the
   registry defined in Section 9 of [RFC5258].
NEW
   This section registers the "MYRIGHTS" option to be added to the
   “LIST-EXTENDED options” registry:
   <https://www.iana.org/assignments/imap-list-extended#imap-list-extended-1>
END

— Section 10.2 —
I find it somewhat odd to have a formal reference to 5819 (implying
that there’s something in there that the reader might find useful in
reading this one), when it’s only used in the Acknowledgments.  I
suggest changing the Acks to just say “RFC 5819” (plain text, not as a
citation), and removing the informative reference.



-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC
--------------FFAF7E8677A8C06D4A50B934-- --------------B33E0574DA6704E400A08990 Content-Type: text/x-vcard; name="murch.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="murch.vcf" bnVsbA== --------------B33E0574DA6704E400A08990-- From nobody Mon Mar 26 07:32:01 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 8F1921250B8 for ; Mon, 26 Mar 2018 07:31:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.4 X-Spam-Level: X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TVD_SPACE_RATIO=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 d7B-dxsk5Off for ; Mon, 26 Mar 2018 07:31:54 -0700 (PDT) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 291C612420B for ; Mon, 26 Mar 2018 07:31:54 -0700 (PDT) Received: by mail-qt0-x236.google.com with SMTP id j3so8258008qtn.9 for ; Mon, 26 Mar 2018 07:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ejmEidSJw7N/+AQdld3cDTV34AyUBFU9j3CtbJnhRWQ=; b=sbvaDVDMU0xWvp6yPOuJn0Blg2fdTqE6pzS1CxlCtq80958c02HpbXGON5wY8lGGjT zDCga6la0mx8sBAutgf7PjEHXsQK1RUBv80ToTy065B47uptjY9NPZmWbbuiyOjHB6iB DI7/jo44SVdmj6WFBqynv1z75oNVMF1tezWnKFrjWfdyrltMhRT2e7HmDSmcDsTmWv1h OgAs2Se44feUKMbHTCx+TXp9LHj9sEkAxkrm1njNib3VUYri/Uuz3wyngiIzv95oG8S/ GNfCvxh9mSviY1JXyHvzpgkClAhGoSO+pr2HD9GnLXqENmNHgcwO3sh8Iy+nTccITZw6 bHdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ejmEidSJw7N/+AQdld3cDTV34AyUBFU9j3CtbJnhRWQ=; b=tTEQMfI7SHA4f5UsBJ/NdN4jfkjCOfN/nANwQh+x/HyfANtVfSiSxUoM/tWCYmBgai QwcT7XIF+SEBtAJ7xObqJoLK8r3wrFXKCoJNMJ2vvozwNS8eri4SCFAXMzBVOL1EaGV2 SLkPDBx2cxK0moRnJ/+x3MJs4C7e3eXzpfHkg70tMaLLqGrQhcOmiJ1QtZcINxx9XFB9 vF7thRzWyPVbNIZAoo8kM6FVRoVO3yw/5cNEgvt6GuWM9gpznhYQmpO6wRA3SRpp8zLW 9+npmMUvwZc37wPekx3JXAfqz16VGBI9XAzjg+0tQyJ6g81v3EdfZLPZWoqcw07u839t mzsA== X-Gm-Message-State: AElRT7FyWvII1VMzE5YNYIy9JHWOWudeSbTz6ka03e8savJPKffuOnOA VF0lo6yw5GILjyRCzcSyJMjtqsYr+a9bCnXZChs= X-Google-Smtp-Source: AG47ELt2EqNSc6rIJyy84aqU7ia8zdzwnKgDF6WZEg1IIP67bz1xxQLk8bGKX+ypojcqo8Ejzan4fO/QrhBL+iRXOC8= X-Received: by 10.237.59.253 with SMTP id s58mr56190048qte.83.1522074713219; Mon, 26 Mar 2018 07:31:53 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba.mailing.lists@gmail.com Received: by 10.237.62.122 with HTTP; Mon, 26 Mar 2018 07:31:52 -0700 (PDT) In-Reply-To: <5419ed87-0778-25d3-e6b3-7e3919a2c6e2@fastmail.com> References: <5419ed87-0778-25d3-e6b3-7e3919a2c6e2@fastmail.com> From: Barry Leiba Date: Mon, 26 Mar 2018 16:31:52 +0200 X-Google-Sender-Auth: d9WroC_rPWBM1uDWp77d2rsXv5o Message-ID: To: Ken Murchison Cc: extra@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 26 Mar 2018 14:31:55 -0000 > Thanks for the review. Changes have been made in the working copy: > https://github.com/ietfextra/tracking/commit/436c8e56970cdf4bef73cbd887c1ee4eaf55b85d Thanks! b From nobody Tue Mar 27 17:21:21 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 D25F9126C0F; Tue, 27 Mar 2018 17:21:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 Si8tx_ixILWH; Tue, 27 Mar 2018 17:21:14 -0700 (PDT) Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 9E5B2120724; Tue, 27 Mar 2018 17:21:14 -0700 (PDT) Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2S0IMjX051210; Wed, 28 Mar 2018 00:21:13 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=corp-2017-10-26; bh=kq5msgTB51sEOiWn3LV8/BKEdi6uq4ZvhBXgXYyfnwg=; b=qKo0PG9K8ZmJIWNnnw3YdOp1qlCowiXckK3EsJVireE66UVj8y7axXP9cFnSmtnqheGQ mwnY7qjoTusMalPNAkNI7JcsELle0BcD9rVERdsnDiu+VER7wAYne19Bztbz7tXOSZrX ya47o01yBRZavthCfbZV0dTuhqRD+XuVncQeGY1+urY9G6duRv7HKJPauuZIJnwxlEsU dMv5Ho9qtuig1jXrvbYWWy6swhRbI9nFM2uC08dTD/iNSApOE8od75Zagb3B/pwv6QBT qjhv/2XH2gyxV+wfFFL7QnWRpMODu0iYP9xdhaftA5YQzC/xQKzQEM7aCJS1isJmqwtb dA== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2120.oracle.com with ESMTP id 2h00csr06n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 28 Mar 2018 00:21:13 +0000 Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2S0LCWK021310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 28 Mar 2018 00:21:12 GMT Received: from abhmp0017.oracle.com (abhmp0017.oracle.com [141.146.116.23]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w2S0LBdk006259; Wed, 28 Mar 2018 00:21:12 GMT Received: from [10.145.183.96] (/10.145.183.96) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 27 Mar 2018 17:21:11 -0700 From: "Chris Newman" To: "Barry Leiba" Cc: draft-ietf-extra-imap-status-size.all@ietf.org, extra@ietf.org Date: Tue, 27 Mar 2018 17:21:08 -0700 X-Mailer: MailMate (1.11r5462) Message-ID: <057E450E-A522-4102-A040-BD7E0656404C@oracle.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8845 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=703 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803270242 Archived-At: Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-status-size-01 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 28 Mar 2018 00:21:16 -0000 I have reviewed this document and support advancement; we might implement this as it's easy to implement on our server. I think the IMAP capability registry is sufficient. - Chris On 26 Mar 2018, at 2:57, Barry Leiba wrote: > This one's ready; I have no issues with any of the text. > > I do have a question, though: > This is the first extension to add "STATUS" items. Should we be > making a registry of them? Or is the presence of "STATUS=SIZE" in the > capabilities list enough, and we shouldn't do another registry? From nobody Tue Mar 27 17:28:46 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 CD0DE126D45 for ; Tue, 27 Mar 2018 17:28:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 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, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 d4emf0l4_c42 for ; Tue, 27 Mar 2018 17:28:42 -0700 (PDT) Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (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 47E16126D3F for ; Tue, 27 Mar 2018 17:28:42 -0700 (PDT) Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2S0Hpqb070604 for ; Wed, 28 Mar 2018 00:28:41 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type : content-transfer-encoding; s=corp-2017-10-26; bh=MGriaozZuAODe0NFLyAt8zriPMzrEVgnxyoNWKPekOE=; b=Wl79FlOsjXSaLBE6BsmYKp0wYRgwa8gKYayHlY4J9Cy8g0mhqaJqLPZz5Eq05ypN8Csz wURgNiv+Akw2E7ULXCDBGcJqJWNR/FHI9AlQd8A9y8A7rFD1bgM/mFAFywChoghmwVUR wfaYtFnsE3Xt98om1AdUaEkJVj0+iao7f5DOVAZ3q6+t8U0l0/F4zPOM6DhTibe/SgsO eCTcClP4A8Bej+wRupc4HcqzcyCWxPi3C1pV/pSRDDM7KFg5VQFbvwtQ7Uzw5uTDIdow QFaIP63UuVPE1I+FY8PvWGVBTm5gsc6jU2h9RtxcnifH7rjiVcL55ibZYLTZ/hzYWiEn 8A== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp2130.oracle.com with ESMTP id 2h00csr0q1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 28 Mar 2018 00:28:41 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w2S0SelY031675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 28 Mar 2018 00:28:40 GMT Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w2S0SeH4018942 for ; Wed, 28 Mar 2018 00:28:40 GMT Received: from [10.145.183.96] (/10.145.183.96) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 27 Mar 2018 17:28:40 -0700 From: "Chris Newman" To: extra@ietf.org Date: Tue, 27 Mar 2018 17:28:37 -0700 X-Mailer: MailMate (1.11r5462) Message-ID: <227925AD-CEB7-4FDF-8873-CB4A8DE040A8@oracle.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8845 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=12 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803270242 Archived-At: Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-list-myrights-02 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 28 Mar 2018 00:28:45 -0000 I've reviewed this document and have no objection to advancement (modulo = I agree with Barry's comment). At this time, we're unlikely to implement = this; I'm not seeing a good cost/benefit argument for this right now. -=C2=A0Chris On 26 Mar 2018, at 2:42, Barry Leiba wrote: > The document's in very good shape and is almost ready. I have a > couple of minor points below. > > =E2=80=94 Section 3 =E2=80=94 > > For each listable mailbox matching > the list pattern and selection options, the server MUST return an > untagged LIST response followed by an untagged MYRIGHTS response > containing the set of rights granted to the logged-in user. > > We don=E2=80=99t usually specify any particular ordering for untagged > responses, and for the most part, ordering is not significant. I > presume it=E2=80=99s not significant here, and that both of the followi= ng > would be equally acceptable to a client: > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * LIST () "." "INBOX" > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: * LIST () "." "foo" > S: * MYRIGHTS "foo" lrs > S: A01 OK List completed. > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * LIST () "." "INBOX" > S: * LIST () "." "foo" > S: * MYRIGHTS "foo" lrs > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: A01 OK List completed. > > Now, one wonders whether this would also be acceptable: > > C: A01 LIST "" % RETURN (MYRIGHTS) > S: * MYRIGHTS "foo" lrs > S: * MYRIGHTS "INBOX" lrswipkxtecda > S: * LIST () "." "INBOX" > S: * LIST () "." "foo" > S: A01 OK List completed. > > =E2=80=A6as a client might not be happy seeing MYRIGHTS responses for > mailboxes for which it has not yet seen a LIST response. > > Also, the MUST attached to the production of the MYRIGHTS response is > contradicted by the MAY in the next paragraph. > > I think we shouldn=E2=80=99t imply that the responses have to be = > interleaved, > and we should point out that the MYRIGHTS response for a given mailbox > can=E2=80=99t precede the LIST response for that mailbox. Maybe this?:= > > NEW > For each listable mailbox matching > the list pattern and selection options, the server MUST return an > untagged LIST response and SHOULD also return an untagged MYRIGHTS > response containing the set of rights granted to the logged-in = > user. > The ordering of the responses is significant only in that the = > server > MUST NOT send a MYRIGHTS for a given mailbox before it sends that > mailbox=E2=80=99s LIST response. > END > > Now, as to the following paragraph that explains the SHOULD: > > If the server is unable to look up the set of rights for a given > mailbox, it MAY drop the corresponding MYRIGHTS reply. > > What else could it do? If there are other reasonable choices, we > should say what they are. If not, we shouldn=E2=80=99t imply that ther= e = > are. > And it=E2=80=99s not really a MAY; the server has to do something = > reasonable, > so I suggest one of the following: > > NEW-1 > If the server is unable to look up the set of rights for a given > mailbox, it does not send the MYRIGHTS reply for that mailbox. > END > > NEW-2 > If the server is unable to look up the set of rights for a given > mailbox, it either does not send the MYRIGHTS reply for that > mailbox or <=E2=80=94fill in other possible actions here=E2=80=94>. > END > > =E2=80=94 Section 8 =E2=80=94 > It=E2=80=99s always a good idea to give IANA the full name of the regis= try, > rather than citing where the registry is defined (this is highlighted > by the fact that there are two registries =E2=80=9Cdefined in Section 9= of > [RFC5258]=E2=80=9D): > > OLD > This document defines the "LIST-MYRIGHTS" IMAP capability to be = > added > to the registry defined in Section 12 of [RFC3501]. > NEW > This document defines the "LIST-MYRIGHTS" IMAP capability to be = > added > to the =E2=80=9CIMAP Capabilities=E2=80=9D registry: > > END > > OLD > This section registers the "MYRIGHTS" option to be added to the > registry defined in Section 9 of [RFC5258]. > NEW > This section registers the "MYRIGHTS" option to be added to the > =E2=80=9CLIST-EXTENDED options=E2=80=9D registry: > > END > > =E2=80=94 Section 10.2 =E2=80=94 > I find it somewhat odd to have a formal reference to 5819 (implying > that there=E2=80=99s something in there that the reader might find usef= ul in > reading this one), when it=E2=80=99s only used in the Acknowledgments. = I > suggest changing the Acks to just say =E2=80=9CRFC 5819=E2=80=9D (plain= text, not = > as a > citation), and removing the informative reference. > > -- = > Barry > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mai= lman_listinfo_extra&d=3DDwIGaQ&c=3DRoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eap= I_JnE&r=3DK_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=3Dzxu1jprWa7J-LiS= 33mK4NK25q4gLF2X1XfIWfvUEX8s&s=3DCLhHcm-GWzsa1BRj2XpjBpC54_pvtE9sLYuiC_pe= tyw&e=3D From nobody Thu Mar 29 16:18:37 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 2E040126CC7 for ; Thu, 29 Mar 2018 16:18:35 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=wlTJJ8oV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FugPzP9I 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 Hx-Q7WHyI43g for ; Thu, 29 Mar 2018 16:18:31 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C95D1127775 for ; Thu, 29 Mar 2018 16:18:31 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0C2CD20FEF for ; Thu, 29 Mar 2018 19:18:31 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Thu, 29 Mar 2018 19:18:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DKHw4WGI6T5fc/QyE hAksg2cTYUUB4hcBCAYAmYbLlc=; b=wlTJJ8oVI8oLxWVCUCWx2VStVYvjqsFqr HozZ/uIYEKlabL8uQ5s4F66+EZG6RNh9v8Iq79aI6FgpvQN0FEgTmOqSDeHtm2vQ j44p6mxInwRH8gpvCnUOyuyD84VtyIrae0OMnny9dFrVJWvziRSDyWxwViaFX2rz qAmqHMhZilTYUuK+EZX0VsUidTZ2didYcYzIYzrq+isrlJNCnt+t4gRm9ukFOsiP 7t8klwOI/XBbodSQ/UTFgkj1Vp2txFV9P3H0ZUOeg4sfcc9aUuqbjLFd84amrcEk zxZTTNqR4+zbmspFIOE8hF9+Lgpln3t0Bho3emTY7H8I1z0rtyFTw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DKHw4W GI6T5fc/QyEhAksg2cTYUUB4hcBCAYAmYbLlc=; b=FugPzP9ItWlgVNB8z89kef B6JVObsWHG4vao/S60ihhfVgpuj/sUZyvsANfALayYVLn/JTDNTTBfwLzCM3/d6s PwHiQ8tUeHrOynWqZj8JRama6WlaiXgWTakFM/Kl0CS3hUsJQT3GPLyKR6Eg1dU+ jmeXzJjhtxhJUdhTbjRL9c01bFFktd8zKG+Zq1xOXn9Pm7jdG1G30n/KSVWI2Mgq H0rme7ZIsHKfaPLoftK9siga/FoS11qLd7Isi2lII/LNVCZwg0ToICABRVDdks/l ZMQ7yw+86qgMoNohI6uTMWzV3bfHTnvy5oOEddiNdrr9aYXSNLRCSvYYEm7mdqxQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id D5B96621BF; Thu, 29 Mar 2018 19:18:30 -0400 (EDT) Message-Id: <1522365510.818814.1320864104.05E10646@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_15223655108188140" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338 Date: Fri, 30 Mar 2018 10:18:30 +1100 References: <057E450E-A522-4102-A040-BD7E0656404C@oracle.com> In-Reply-To: <057E450E-A522-4102-A040-BD7E0656404C@oracle.com> Archived-At: Subject: Re: [Extra] WGLC review of draft-ietf-extra-imap-status-size-01 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Thu, 29 Mar 2018 23:18:35 -0000 This is a multi-part message in MIME format. --_----------=_15223655108188140 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" I have reviewed this document and support advancement; we have already implemented it in our server and it works well. We were already storing this value (QUOTA_MAILBOX_USED) for each mailbox, so it was trivial to add. I am also happy with the IMAP capability registry. Bron. On Wed, 28 Mar 2018, at 11:21, Chris Newman wrote: > I have reviewed this document and support advancement; we might > implement this as it's easy to implement on our server. I think > the IMAP> capability registry is sufficient. > > - Chris > > On 26 Mar 2018, at 2:57, Barry Leiba wrote: > >> This one's ready; I have no issues with any of the text. >> >> I do have a question, though: >> This is the first extension to add "STATUS" items. Should we be >> making a registry of them? Or is the presence of >> "STATUS=SIZE" in the>> capabilities list enough, and we shouldn't do another registry? > > _________________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_15223655108188140 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
I have reviewed this document and support advancement; we have already implemented it in our server and it works well.  We were already storing this value (QUOTA_MAILBOX_USED) for each mailbox, so it was trivial to add.  I am also happy with the IMAP capability registry.

Bron.


On Wed, 28 Mar 2018, at 11:21, Chris Newman wrote:
I have reviewed this document and support advancement; we might
implement this as it's easy to implement on our server. I think the IMAP
capability registry is sufficient.

- Chris

On 26 Mar 2018, at 2:57, Barry Leiba wrote:

This one's ready; I have no issues with any of the text.

I do have a question, though:
This is the first extension to add "STATUS" items.  Should we be
making a registry of them?  Or is the presence of "STATUS=SIZE" in the
capabilities list enough, and we shouldn't do another registry?

_______________________________________________
Extra mailing list

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


--_----------=_15223655108188140-- From nobody Thu Mar 29 16:40:30 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 D669C12E868; Thu, 29 Mar 2018 16:40:28 -0700 (PDT) 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.76.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152236682882.20574.13194943115059948052@ietfa.amsl.com> Date: Thu, 29 Mar 2018 16:40:28 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-specialuse-important-00.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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, 29 Mar 2018 23:40:29 -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 : IMAP $Important Keyword and \Important Special-Use Attribute Author : Barry Leiba Filename : draft-ietf-extra-specialuse-important-00.txt Pages : 9 Date : 2018-03-22 Abstract: RFC 6154 created an IMAP Special-Use LIST extension and defined an initial set of attributes. This document defines a new attribute, "\Important", and establishes a new IANA registry for IMAP folder attributes, registering the attributes defined in RFCs 3348, 3501, and 6154. This document also defines a new IMAP keyword, "$Important", and registers it in the registry defined in RFC 5788. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-specialuse-important/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-specialuse-important-00 https://datatracker.ietf.org/doc/html/draft-ietf-extra-specialuse-important-00 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 Thu Mar 29 17:03:13 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 499EB128961; Thu, 29 Mar 2018 17:03:12 -0700 (PDT) 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.76.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152236819226.20436.3486622163215088218@ietfa.amsl.com> Date: Thu, 29 Mar 2018 17:03:12 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-unauth-00.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 00:03:12 -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 : IMAP UNAUTHENTICATE for Connection Reuse Author : Chris Newman Filename : draft-ietf-extra-imap-unauth-00.txt Pages : 10 Date : 2018-03-27 Abstract: This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-unauth/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-unauth-00 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-unauth-00 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 Thu Mar 29 19:10:40 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 054C712E865; Thu, 29 Mar 2018 19:10:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.76.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152237583801.20383.2140007544077686646.idtracker@ietfa.amsl.com> Date: Thu, 29 Mar 2018 19:10:38 -0700 Archived-At: Subject: [Extra] The EXTRA WG has placed draft-melnikov-imap4rev2 in state "Adopted by a WG" X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 02:10:38 -0000 The EXTRA WG has placed draft-melnikov-imap4rev2 in state Adopted by a WG (entered by Bron Gondwana) The document is available at https://datatracker.ietf.org/doc/draft-melnikov-imap4rev2/ Comment: This was discussed at IETF101. We know it will be a big job! From nobody Thu Mar 29 19:15:40 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 E3DF412E866; Thu, 29 Mar 2018 19:15:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.76.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152237613892.20496.10847986243614763892.idtracker@ietfa.amsl.com> Date: Thu, 29 Mar 2018 19:15:38 -0700 Archived-At: Subject: [Extra] The EXTRA WG has placed draft-extra-imap-uniqueid in state "Adopted by a WG" X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 02:15:39 -0000 The EXTRA WG has placed draft-extra-imap-uniqueid in state Adopted by a WG (entered by Bron Gondwana) The document is available at https://datatracker.ietf.org/doc/draft-extra-imap-uniqueid/ From nobody Thu Mar 29 19:18:42 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 707C3128896; Thu, 29 Mar 2018 19:18:41 -0700 (PDT) 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.76.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152237632141.20368.11309022554814360241@ietfa.amsl.com> Date: Thu, 29 Mar 2018 19:18:41 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap-uniqueid-00.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 02:18:41 -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 : IMAP Extension for unique identifiers Author : Bron Gondwana Filename : draft-ietf-extra-imap-uniqueid-00.txt Pages : 10 Date : 2018-03-29 Abstract: This document adds new properties to IMAP mailboxes and messages to allow clients to more efficiently re-use cached data for resources which have changed location on the server. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap-uniqueid/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap-uniqueid-00 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap-uniqueid-00 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 Thu Mar 29 19:24: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 5621812D77D for ; Thu, 29 Mar 2018 19:24:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=fastmailteam.com header.b=YdrRmsV6; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WK/VwoBz 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 qgZh09TeQ_3Q for ; Thu, 29 Mar 2018 19:24:33 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31D6A124B18 for ; Thu, 29 Mar 2018 19:24:30 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7BD4321847 for ; Thu, 29 Mar 2018 22:24:29 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Thu, 29 Mar 2018 22:24:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:message-id:mime-version:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Jl6bGEz2DTL+bSMgvm7niehwE2dF7ZVbjq7YYGu6L Bc=; b=YdrRmsV6kxZfrC2qKozRt+MzyEWeULNzXt9XYvow85eeEoP6f9MHiLg9e 9JZzEGHsO80ugqhv39QV2dzohVGeQBBU/F9+2HqJguwEjwHjRqevMHLkl54P2+iQ r/z96DDNzYsE9ZmyWHfFjpz7eloXyKxqYKAFwtHPaDeKTQW/6DTAEeh4830N7V7N f+RL3qMup5CSUvvqroTl+vHQHIjFJ2wdfNDUvjxATKEinOxn7zcF2ATvacJW22ME lk39qL51rhnaSf1JXIYYMDVEDpk01oT77FRWHFt+Uz+mUj3vTwe2kg7CEDALqdB1 Y1B2je9Py0qDXpJg7aksNb9F4Jhaw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Jl6bGEz2DTL+bSMgvm7niehwE2dF7 ZVbjq7YYGu6LBc=; b=WK/VwoBz0FJ4Q+i/ZL/nIA1Wiy2C+QrX2JkgiSbP0yeIz M/8+q+w1SgrBeTxBew/PpRlb7/ZBgPAhwt4smF7yt/3i2FPekMt4mKQsdqD81ul4 MaSg8hbRXRJMOCUKx78ivrnpwwnMUhqmIiO3F4iobnwai7JlfO94RWHvBmieCVAj Gz0lvXGlQ7+rWaElGgdIcl8LVwnHsXb9qi/MKbpSoN6Zajdn71xIdooEKNdQKNez asAEMoYAdDNxSPcSN1DRU6qHtdXYZva3bdC5ZHOZY2tJZEDWaFW0P2TfkANwaEZu APQdVTQOsT3pk0KdFMm9QgQLZ1QQCDK/+7qHAp+Lg== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 538A8621BF; Thu, 29 Mar 2018 22:24:29 -0400 (EDT) Message-Id: <1522376669.2938455.1320856920.5A37C6DB@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338 Date: Fri, 30 Mar 2018 13:24:29 +1100 Archived-At: Subject: [Extra] Document status update X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 30 Mar 2018 02:24:35 -0000 Hi All, It's a week since our session in London.=C2=A0 I've been traveling, so have= n't updated documents as quickly as promised, so I'm going through everythi= ng now.=C2=A0 Here's my recollection/updates on everything: draft-ietf-extra-imap-64bit-03: * There's discussion about merging it into IMAP4rev2 rather than having it = be a standalone change. * next-steps: waiting to see what we do with IMAP4rev2. draft-ietf-extra-imap-list-myrights-02: * in Working Group Last Call * has had updates based on WGLC from review, so an -03 will probably be lan= ding soon * Jiankang is shepherd draft-ietf-extra-imap-savedate-00: * status from IETF101 was "more discussion needed on mailing list" * Both the github issues are about handing "when not supported" and search: - https://github.com/ietfextra/tracking/issues/13 - https://github.com/ietfextra/tracking/issues/21 * next-steps: I'll start a thread for discussion. draft-ietf-extra-imap-status-size-01: * in Working Group Last Call * has had updates based on WGLC from review, so an -02 will probably be lan= ding soon * I am shepherd=20 draft-ietf-extra-sieve-fcc-01: * status from IETF101 was "one more round on the mailing list after edits, = then WGLC" * discussion led to "yes, syntax is wrong as suspected" * discussion has not yet resolved: - one or many capabilities? - what to do for notify actions that don't have a MIME serialisation * next-steps: I'd like to get this one finished soon, so I'll start a bikes= hedding thread for it. draft-ietf-extra-sieve-special-use-02: * just needs some examples of equivalent IMAP command sequences to help imp= lementations. * I will shepherd to WGLC once those are done. We also agreed to adopt the following documents. Please note, adoption doe= sn't mean that we will accept them "as is", it just means that the group ag= rees that they are within our charter and that we will work on them. Havin= g said that, two of them are already basically finished, so go comment on t= he last calls :) draft-ietf-extra-specialuse-important-00: * document is now adopted by the working group * I will take to Working Group Last Call * I will be shepherd draft-ietf-extra-imap-unauth-00: * document is now adopted by the working group * it seems quite complete, and implementations already exist * I will take to Working Group Last Call * I will be shepherd draft-extra-imap-uniqueid-00: * document is now adopted by the working group * there are still some edits required, uploaded -00 is not the finished pro= duct * next steps: I will keep working on it. draft-melnikov-imap4rev2-07: * document is now adopted by the working group * next steps: plenty of work to do here! Alexey and Barry will co-editor. Cheers, Bron. -- =C2=A0 Bron Gondwana, CEO, FastMail Pty Ltd =C2=A0 brong@fastmailteam.com From nobody Thu Mar 29 19:46:09 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 558001241F5 for ; Thu, 29 Mar 2018 19:46:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=fastmailteam.com header.b=P1T+2kjX; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GwHTOoK6 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 FsPadfXIBmyQ for ; Thu, 29 Mar 2018 19:46:06 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5438A12E885 for ; Thu, 29 Mar 2018 19:46:05 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B5F5420FE3; Thu, 29 Mar 2018 22:46:04 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Thu, 29 Mar 2018 22:46:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=8o7aRDcV3DUajObM3dLMXPhlrobLz UUnzi7zTHxbRAs=; b=P1T+2kjXVuIyzfCHuWSsKXI7mzXWDsWCR9oJk3CRb5rui it4ExQEUfAbV7LL6ub2xMHBVxQenOQtYdYwxduArSXvWA1D3j7g/Ipu519gmAOsx 5v7kgChT//oeYfimL6l0PYznPIQRyJxj6KIXH7pQLOHhKawNVbPrjI5wLcWgRrBp XUjEDZWYNfQAcSzX1WUD/ER8wnAUiArm+5OwetcB8Sgc/4FDufQ2wXUY8fu9A5b/ oSMC2wSlRf0m/Ha0u7kw0c6OgNSylJ1wYxP3sScW8yW+SDocDRq2kVvoWKrRF3I8 WQBj6je7Ge+uK25NhKVeUxq9JwmT0hdoS6r2/O9dA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=8o7aRDcV3DUajObM3dLMXPhlrobLz UUnzi7zTHxbRAs=; b=GwHTOoK6YSUoHlE0ln8BDuz5RhmSdOLURayHtGd0kyX2e DLo19i1Yoarz9NpZQo9pdYBWTtLJDtQ4ZkTJVabxqv5zZ9GCO4sr2x2iOzCK+3lO 6eYLDuVmq/G5r9rMyhq6t3mZvcdvZujB/wNrDDzplC+/2kDnr9UpxFm+rA4DaErJ yqi7QxCt6qoT0trinfbHdhXVLpsuiTey8+rWp764DwA+CURLKEVu8KQ8tshqHMg0 SGeHfSyQ+yTLbzfB2T5y7VCfF9vb7b4MB8BSuCgbhkrA/mzIWoZm8x4Q8nVs2yko M48F0IRtq9w8Bs8n+4oz7TTPpWi5ILwK7MRx8yhmw== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 8D9CE621BF; Thu, 29 Mar 2018 22:46:04 -0400 (EDT) Message-Id: <1522377964.2946539.1320984840.43ED1AAA@webmail.messagingengine.com> From: Bron Gondwana To: extra@ietf.org Cc: stephan.bosch@dovecot.fi MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_152237796429465391" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338 Date: Fri, 30 Mar 2018 13:46:04 +1100 Archived-At: Subject: [Extra] SAVEDATE: how to handle mailboxes without support X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 30 Mar 2018 02:46:08 -0000 This is a multi-part message in MIME format. --_----------=_152237796429465391 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" This is the only outstanding issue for this draft. I quite like the idea proposed during IETF101, a boolean search key SAVEDATESUPPORTED which can be used to create search queries that work for both mailboxes that do and don't support SAVEDATE. There are two proposed ways to handle mailboxes where SAVEDATESUPPORTED is false. One option is that SAVED* searches always return false as well: e.g. 1 SEARCH OR SAVEDSINCE 01-Jan-2018 AND NOT SAVEDATESUPPORTED SINCE 01-Jan-2018-- find everything added to this mailbox since the start of the year, falling back to INTERNALDATE only if SAVEDATESUPPORTED is false. 2 SEARCH SAVEDBEFORE 01-Jan-2018 -- find everything to purge that's been in this mailbox since before this year, but only if SAVEDATE is supported so we never purge anything that may have been old, but only moved here recently. The alternative proposal is that SAVED* keys act on INTERNALDATE rather than SAVEDATE if SAVEDATESUPPORTED is false. I can also work with this, by using something like: 1 SEARCH SAVEDSINCE 01-Jan-2018 2 SEARCH SAVEDATESUPPORTED SAVEDBEFORE 01-Jan-2018 Looking at these two options, I'm actually quite OK with either! The main concern whether people will purge too much mail, or not find enough mail, depending which is which. Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --_----------=_152237796429465391 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
This is the only outstanding issue for this draft.  I quite like the idea proposed during IETF101, a boolean search key SAVEDATESUPPORTED which can be used to create search queries that work for both mailboxes that do and don't support SAVEDATE.

There are two proposed ways to handle mailboxes where SAVEDATESUPPORTED is false.  One option is that SAVED* searches always return false as well:

e.g.

1 SEARCH OR SAVEDSINCE 01-Jan-2018 AND NOT SAVEDATESUPPORTED SINCE 01-Jan-2018
-- find everything added to this mailbox since the start of the year, falling back to INTERNALDATE only if SAVEDATESUPPORTED is false.

2 SEARCH SAVEDBEFORE 01-Jan-2018
-- find everything to purge that's been in this mailbox since before this year, but only if SAVEDATE is supported so we never purge anything that may have been old, but only moved here recently.

The alternative proposal is that SAVED* keys act on INTERNALDATE rather than SAVEDATE if SAVEDATESUPPORTED is false.  I can also work with this, by using something like:

1 SEARCH SAVEDSINCE 01-Jan-2018

2 SEARCH SAVEDATESUPPORTED SAVEDBEFORE 01-Jan-2018


Looking at these two options, I'm actually quite OK with either!  The main concern whether people will purge too much mail, or not find enough mail, depending which is which.

Cheers,

Bron.

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


--_----------=_152237796429465391--