Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt
Barry Leiba <barryleiba@computer.org> Wed, 10 October 2012 20:45 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C3521F854C for <sieve@ietfa.amsl.com>; Wed, 10 Oct 2012 13:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.761
X-Spam-Level:
X-Spam-Status: No, score=-102.761 tagged_above=-999 required=5 tests=[AWL=-0.384, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSZ2apMQD8Gc for <sieve@ietfa.amsl.com>; Wed, 10 Oct 2012 13:45:30 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD9F21F852C for <sieve@ietf.org>; Wed, 10 Oct 2012 13:45:30 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so1456846vcb.31 for <sieve@ietf.org>; Wed, 10 Oct 2012 13:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8Rzh7rAVFb3Wc6tOrrss0T+ubP6+L0RiaMnFSmtDco4=; b=dAG5+XCiiCYAITo1lBzZCU7zNxcatIKADuZKi00XZmU59YcksC182I786309OHESVc 5zf15GicrKtgUoleyonZnvvmVtYZm7HOIdVj38n38AD5/RKLzVg6DtnrsBdhiBgKRgSM O1c+0QAx7TJMS129X/27upY69QVDLPK9zuWTCBOiIuwkKoNvXS2WpJnlmJqdf5RYtAg6 q5wfN6m+LsNKgZY37Onsu79jCdQXnMEbRzail7z6MI9RwH0P/nBNqDaa3FImIUvsTypr ngi9mzYwfzZYqMZKzpN+B5P1vRjiVg85ga3gJhcrlbcuqco0fkyBBIUdmm2vDwVmVXp4 NUlg==
MIME-Version: 1.0
Received: by 10.52.65.51 with SMTP id u19mr11883611vds.3.1349901929949; Wed, 10 Oct 2012 13:45:29 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.59.5.72 with HTTP; Wed, 10 Oct 2012 13:45:29 -0700 (PDT)
In-Reply-To: <CAEdAYKVtR+LvFfeYbcPeTC0HpT7DvCyFNHaQk1dJSfjDNBUFTg@mail.gmail.com>
References: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> <CAC4RtVDUxusjA-dG=-aQfpdWQ_qXKueOZF+qwzxiqLUQ7cf76A@mail.gmail.com> <5075D84B.8030007@rename-it.nl> <CAEdAYKVtR+LvFfeYbcPeTC0HpT7DvCyFNHaQk1dJSfjDNBUFTg@mail.gmail.com>
Date: Wed, 10 Oct 2012 16:45:29 -0400
X-Google-Sender-Auth: yvEH7x-Rl5rvYEUblFoddynajqo
Message-ID: <CALaySJLevN_8AHgDOmJm+-p07B=FwvYvTGRJsDksXRH_vb=0fQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Aaron Stone <aaron@serendipity.cx>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: sieve@ietf.org
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 20:45:32 -0000
>> Just a question, how are we going to handle the approval of the following >> IMAP extension? >> >> https://tools.ietf.org/html/draft-ietf-imapmove-command-01 >> >> Intuitively, I would say that adds a new imap.cause item called "MOVE" and I >> guess at some point this (or something else) would need to be documented. >> Would it still be possible for the editor to hammer it into the current >> yet-to-be-RFC imapsieve document if IMAP MOVE (somehow) makes it to RFC >> first? > > IMAP Sieve is already in the Editor's Queue, so it's surely ahead of IMAP MOVE. Right, and I've addressed this in my AD review of the MOVE extension document: http://www.ietf.org/mail-archive/web/imapext/current/msg04712.html ------------------------------ -- Section 4 -- Add a new Section: 4.5. IMAP Events in Sieve MOVE applies to IMAP events in Sieve [reference] in the same way as COPY does. Therefore, MOVE can cause a Sieve script to be invoked with the imap.cause set to "COPY". Because MOVE does not cause flags to be changed, a MOVE command will not result in a script invocation with the imap.cause set to "FLAG". The [reference] for IMAP Events in Sieve is draft-ietf-sieve-imap-sieve-09, which should be in the RFC Editor queue any day now (so it won't hold this document up). ------------------------------ ...with follow-up here: http://www.ietf.org/mail-archive/web/imapext/current/msg04714.html ------------------------------ Ned's comment: > I think this is the right thing to do, but I have to ask: Given the timing > of the Sieve in IMAP spec we could define a new "MOVE" cause in the base > specification if we wanted to. Do we want to do this? I thought about that when I wrote the above, and I can't find a good reason to distinguish MOVE from COPY in imap-sieve. It also wouldn't be as simple as just defining a new cause: we'd have to decide whether only the target-mailbox script is run, or whether the source-mailbox script is run as well. My sense is that it's not an important distinction, and we don't want to go there. ------------------------------ Barry
- [sieve] I-D Action: draft-ietf-sieve-imap-sieve-0… internet-drafts
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Barry Leiba
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Robert Sparks
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Stephan Bosch
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Aaron Stone
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Barry Leiba
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Stephan Bosch