From lemonade-bounces@ietf.org Wed Aug 01 13:37:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8A-0002Qy-TV; Wed, 01 Aug 2007 13:37:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGI8A-0002Nc-4C for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:37:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI89-0002Ll-Pr for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGI88-0004jH-Ez for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hb1V9022100; Wed, 1 Aug 2007 10:37:01 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hax2k011524; Wed, 1 Aug 2007 10:37:00 -0700 Received: from 172.24.29.60 ([172.24.29.60]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 1 Aug 2007 17:36:52 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 01 Aug 2007 11:15:32 -0500 Subject: Re: [lemonade] draft-ietf-lemonade-convert-10.txt From: Eric Burger To: Alexey Melnikov , Lyndon Nerenberg , Mark Crispin Message-ID: Thread-Topic: [lemonade] draft-ietf-lemonade-convert-10.txt Thread-Index: AcfUVy8NbcBuoEBKEdyoAwAWy4mm/w== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org I do not sense consensus, other than "you don't get it" and "yes, but you don't get it." I think Mark may have presented the root cause for the confusion. Can we work our way out of this one? On 7/31/07 11:41 AM, "Mark Crispin" wrote: > On Tue, 31 Jul 2007, Alexey Melnikov wrote: >> I actually remembered the true reason why I've used a single token - because >> of the default conversion (which is NIL). Handling silly states is worse >> (e.g. "text" NIL), etc. > > TEXT is not a valid MIME type/subtype specifier. Neither is TEXT/NIL. > > The underlying bug is that you have NIL as a default, rather than > specified defaults. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 13:37:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8A-0002Pg-NA; Wed, 01 Aug 2007 13:37:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGI89-0002Kn-Lp for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI89-0002JD-8x for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGI88-0005t7-Lv for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hb2Yk022112; Wed, 1 Aug 2007 10:37:02 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hax2m011524; Wed, 1 Aug 2007 10:37:01 -0700 Received: from 172.24.29.60 ([172.24.29.60]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 1 Aug 2007 17:36:54 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 01 Aug 2007 11:20:43 -0500 Subject: Re: [lemonade] IMAP-SIEVE From: Eric Burger To: Stephan Bosch Message-ID: Thread-Topic: [lemonade] IMAP-SIEVE Thread-Index: AcfTbWqqFKiCf9P+REaa6KdcZlzl5gA6n3C0 In-Reply-To: <46AF2964.3000106@rename-it.nl> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org As a user, I like it. On 7/31/07 5:21 AM, "Stephan Bosch" wrote: > Eric Burger wrote: >> Any comments on IMAP sieve? >> >> http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve-03 >> > I don't know whether this is the correct time and place to post this > suggestion, but I'll do it anyway. I apologize if the suggested > functionality is not within the scope of this proposed IMAP extension > (or lemonade for that matter). > > IMAPSieve currently only suggests running sieve scripts when certain > IMAP commands are executed, apart from running a sieve script upon > delivery. What I currently miss in the Sieve world is the ability for a > client to simply run a sieve script on a folder when requested by the > user (i.e. by issueing a new IMAP command). Many mail clients that > support some form of filtering also include functionality to apply the > currently defined filters on a specific folder or a set of messages. > This is especially useful when the current filterset has misdelivered a > large number of messages to a specific folter; the user can fix this by > updating the filters accordingly and applying the filters to the folder > in question. Of course the mail client could do this using a sequence of > IMAP commands, but this does not test the new Sieve script on the server. > > Just a thought... > > Regards, > > -- > Stephan Bosch > stephan@rename-it.nl > > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 13:37:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8A-0002Qy-TV; Wed, 01 Aug 2007 13:37:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGI8A-0002Nc-4C for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:37:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI89-0002Ll-Pr for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGI88-0004jH-Ez for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hb1V9022100; Wed, 1 Aug 2007 10:37:01 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hax2k011524; Wed, 1 Aug 2007 10:37:00 -0700 Received: from 172.24.29.60 ([172.24.29.60]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 1 Aug 2007 17:36:52 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 01 Aug 2007 11:15:32 -0500 Subject: Re: [lemonade] draft-ietf-lemonade-convert-10.txt From: Eric Burger To: Alexey Melnikov , Lyndon Nerenberg , Mark Crispin Message-ID: Thread-Topic: [lemonade] draft-ietf-lemonade-convert-10.txt Thread-Index: AcfUVy8NbcBuoEBKEdyoAwAWy4mm/w== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org I do not sense consensus, other than "you don't get it" and "yes, but you don't get it." I think Mark may have presented the root cause for the confusion. Can we work our way out of this one? On 7/31/07 11:41 AM, "Mark Crispin" wrote: > On Tue, 31 Jul 2007, Alexey Melnikov wrote: >> I actually remembered the true reason why I've used a single token - because >> of the default conversion (which is NIL). Handling silly states is worse >> (e.g. "text" NIL), etc. > > TEXT is not a valid MIME type/subtype specifier. Neither is TEXT/NIL. > > The underlying bug is that you have NIL as a default, rather than > specified defaults. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 13:37:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8A-0002Pg-NA; Wed, 01 Aug 2007 13:37:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGI89-0002Kn-Lp for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI89-0002JD-8x for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGI88-0005t7-Lv for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hb2Yk022112; Wed, 1 Aug 2007 10:37:02 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hax2m011524; Wed, 1 Aug 2007 10:37:01 -0700 Received: from 172.24.29.60 ([172.24.29.60]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 1 Aug 2007 17:36:54 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 01 Aug 2007 11:20:43 -0500 Subject: Re: [lemonade] IMAP-SIEVE From: Eric Burger To: Stephan Bosch Message-ID: Thread-Topic: [lemonade] IMAP-SIEVE Thread-Index: AcfTbWqqFKiCf9P+REaa6KdcZlzl5gA6n3C0 In-Reply-To: <46AF2964.3000106@rename-it.nl> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org As a user, I like it. On 7/31/07 5:21 AM, "Stephan Bosch" wrote: > Eric Burger wrote: >> Any comments on IMAP sieve? >> >> http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve-03 >> > I don't know whether this is the correct time and place to post this > suggestion, but I'll do it anyway. I apologize if the suggested > functionality is not within the scope of this proposed IMAP extension > (or lemonade for that matter). > > IMAPSieve currently only suggests running sieve scripts when certain > IMAP commands are executed, apart from running a sieve script upon > delivery. What I currently miss in the Sieve world is the ability for a > client to simply run a sieve script on a folder when requested by the > user (i.e. by issueing a new IMAP command). Many mail clients that > support some form of filtering also include functionality to apply the > currently defined filters on a specific folder or a set of messages. > This is especially useful when the current filterset has misdelivered a > large number of messages to a specific folter; the user can fix this by > updating the filters accordingly and applying the filters to the folder > in question. Of course the mail client could do this using a sequence of > IMAP commands, but this does not test the new Sieve script on the server. > > Just a thought... > > Regards, > > -- > Stephan Bosch > stephan@rename-it.nl > > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 13:37:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8D-0002av-40; Wed, 01 Aug 2007 13:37:09 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGI8B-0002a7-U1 for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:37:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGI8B-0002WV-Gj for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:07 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGI89-0004jK-V5 for lemonade@ietf.org; Wed, 01 Aug 2007 13:37:07 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hb4gS022121; Wed, 1 Aug 2007 10:37:04 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l71Hax2o011524; Wed, 1 Aug 2007 10:37:03 -0700 Received: from 172.24.29.60 ([172.24.29.60]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 1 Aug 2007 17:36:53 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 01 Aug 2007 11:20:12 -0500 Subject: Re: [lemonade] Imap-notify-07 - Mailbox Names From: Eric Burger To: Alexey Melnikov Message-ID: Thread-Topic: [lemonade] Imap-notify-07 - Mailbox Names Thread-Index: AcfUV9XyFFf2DkBLEdyoAwAWy4mm/w== In-Reply-To: <46A8F9D3.1010607@isode.com> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: "lemonade@ietf.org" , "curtis.king@isode.com" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The client inserts a mailbox name or list of mailbox names after the "mailboxes" token. The server MUST NOT do wildcard expansion. This means there is no special treatment for the LIST wildcard characters ('*' and '%') if they are present in mailbox names. On 7/26/07 2:45 PM, "Alexey Melnikov" wrote: > Eric Burger wrote: > >> What does section 6.6 mean when it says LIST wildcards are not special? >> >> Does that mean: >> (1) you can address mailboxes that contain * and %? >> (2) simply that you cannot search (in which case, do you get BAD or NO)? >> (3) something else? >> (4) all of the above? >> >> > The intent was (1). Of course any server that allows for mailboxes > containing * and % is already strange > (And any client that tryies to create them is broken) > > Do you have a suggestion how to improve the text? > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 16:11:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGKXD-0002Zv-Ja; Wed, 01 Aug 2007 16:11:07 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGKXB-0002Zn-Js for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 16:11:05 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGKXB-0002Zb-67 for lemonade@ietf.org; Wed, 01 Aug 2007 16:11:05 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGKXA-0001wu-M7 for lemonade@ietf.org; Wed, 01 Aug 2007 16:11:05 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 1 Aug 2007 21:11:02 +0100 Message-ID: <46B0E913.4020503@isode.com> Date: Wed, 01 Aug 2007 14:12:03 -0600 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] Imap-notify-07 - Mailbox Names References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: "lemonade@ietf.org" , "curtis.king@isode.com" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Eric Burger wrote: >The client inserts a mailbox name or list of mailbox names after the >"mailboxes" token. The server MUST NOT do wildcard expansion. This means >there is no special treatment for the LIST wildcard characters ('*' and '%') >if they are present in mailbox names. > > Ok, I've used the last 2 sentences. Thanks for the suggestion. >On 7/26/07 2:45 PM, "Alexey Melnikov" wrote: > > >>Eric Burger wrote: >> >> >>>What does section 6.6 mean when it says LIST wildcards are not special? >>> >>>Does that mean: >>>(1) you can address mailboxes that contain * and %? >>>(2) simply that you cannot search (in which case, do you get BAD or NO)? >>>(3) something else? >>>(4) all of the above? >>> >>> >>The intent was (1). Of course any server that allows for mailboxes >>containing * and % is already strange >>(And any client that tryies to create them is broken) >> >>Do you have a suggestion how to improve the text? >> >> _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 01 16:15:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGKbN-0005ow-Pw; Wed, 01 Aug 2007 16:15:25 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IGKbM-0005oV-L7 for lemonade-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 16:15:24 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGKbM-0005nb-0F for lemonade@ietf.org; Wed, 01 Aug 2007 16:15:24 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGKbL-00021X-EL for lemonade@ietf.org; Wed, 01 Aug 2007 16:15:23 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 1 Aug 2007 21:15:20 +0100 Message-ID: <46B0EA16.7080002@isode.com> Date: Wed, 01 Aug 2007 14:16:22 -0600 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] imap-notify-07 - NOTIFICATION OVERFLOW References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: "lemonade@ietf.org" , "curtis.king@isode.com" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Eric Burger wrote: > > >The text shows what looks like optional text for [NOTIFICATIONOVERFLOW]. > >Would any client ever use the information? > No, any human readable text can at most be presented to the user, but I don't see any reason for doing that in this case. >I would be careful with the >example, because you know server writers will use it for debugging but >client writers may depend on the server-specific strings. > >If the client would use the information, I would suggest standardizing >result codes. If the client would not use the information, I would at the >least suggest the example text be something like, "A comment can go here, >sorry". > The latter. I've updated the example. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 08 01:32:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIe7z-0007ss-5x; Wed, 08 Aug 2007 01:30:39 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IIe7y-0007mA-6S for lemonade-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 01:30:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIe7x-0007jI-O0 for lemonade@ietf.org; Wed, 08 Aug 2007 01:30:37 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIe7w-0005pY-7s for lemonade@ietf.org; Wed, 08 Aug 2007 01:30:37 -0400 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l785UYvY009131 for ; Tue, 7 Aug 2007 22:30:34 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l785TrV2012463 for ; Tue, 7 Aug 2007 22:29:53 -0700 Received: from 10.136.9.103 ([10.136.9.103]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 8 Aug 2007 05:30:33 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 08 Aug 2007 14:30:30 +0900 From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: DRAFT Minutes Thread-Index: AcfZfTvBemlq3EVwEdyMOgAWy4mm/w== Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Subject: [lemonade] DRAFT Minutes X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Are posted at Copied here for your convenience. Note there are a few consensii. Please look at the minutes here and start a new thread on the lemonade list if you do NOT agree. Lemonade Minutes, Day 1 - OMA to clarify the architecture slide: the division of boxes and marking/coloration wasn't completely clear and/or correct (mail store vs mail store behaviour) - OMA to confirm what is meant by Unicode support - if it is a reference to GB 18030, then need to make sure everyone understands the effects and complications. For example, transformation between GB 18030 <==> Unicode is not necessarily a bijection - Barry to suggest non-normative implementation note regarding binary content for CONVERT document - Cyrus to suggest text for "no access" flag to handle NOTIFY ACL issue - Alexey to register new message event types in NOTIFY - Dave to comment on slide 7 of NOTIFY slides - get next rev of NOTIFY draft - need more stuckees on doing review on the CONTEXT/NOTIFY integration - Randy to suggest text regarding automatic fetching of BODY[*] via NOTIFY - Dave to finish his document regarding IMAP URL extensions (Respectfully submitted, Philip) ======================================== Lemonade, Session 2, July 24th, 2007 Chairs: Eric Burger, Glenn Parsons Agenda as originally posted Randy Gellens presented the message events draft and review open issues. In resolution of the first open issue (anchor 11) the group present came to consensus that the existing text would be retained. For the second open issue (anchor 23): Should the mailbox admin events be on the exceptions list? The group present said that it would be added to the exceptions list because of lack of deployment. Randy will update the draft and request a new last call. Barry Leiba then reviewed the IMAP-sieve script and the discussion in the SIEVE meeting. A use case will be added to the Lemonade document. Randy reviewed the differences between the single-client and multiple clients cases for update of sieve scripts. Randy Gellens has taken an action to provide text on the multiple client mechanism in a hierarchy. He will send it to the list for review. He notes that clients are "write only" as far as a current client implementations are concerned, and his text will address. Barry discusses Issue 2, allowing transient editor header actions, to apply for the execution of the script for redirect. It was discussed, and the group present came to consensus that the text would remain as is. A later extension to handle this could be created if a compelling use case is present. The group next took up the question of whether Expunge should be an imap-sieve event? The group present came to consensus that the mailing list would be polled for additional interest, as there is currently only one interested developer. If there is no additional interest, there seems to be no objection to it as an extension. Barry then asked whether the references to sieve extensions be normative or informative? The group came to consensus that they should be normative, and he will update the text, except for the cases where the referenced extension is disallowed. The group then discussed profile bis, with Alexey presenting the issues. There have been no updates since Prague. SASL-IR will be added (it is currently in the RFC editors queue). Sort has also been added. Comparator is a dependency as is enable. Zoltan asked whether IDLE is necessary if NOTIFY is present? Alexey notes it was a dependency in Profile. Rough consensus to keep it in. In discussing streaming, the group present came to consensus that it will remain outside the profilebis document scope. For quickstart, the group present came to consensus that it will remain outside the profilebis document scope. The group discussed the placement of notifications discussion; this did not come to consensus on placement in the room. A small design team, led by Randy Gellens, will make a proposal to the list in three weeks. CMCC then discussed interoperability testing for lemonade. This would not be an IETF meeting, though data on the interoperability would be sent to the list and ADs. An invitation to this, should one be planned, will also be sent to the list. Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 08 01:35:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIeAn-0001ZZ-KT; Wed, 08 Aug 2007 01:33:33 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IIeAm-0001ZO-64 for lemonade-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 01:33:32 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIeAk-0001ZE-7H for lemonade@ietf.org; Wed, 08 Aug 2007 01:33:31 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IIeAj-0004C8-LE for lemonade@ietf.org; Wed, 08 Aug 2007 01:33:30 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l785XS9D013705; Tue, 7 Aug 2007 22:33:28 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l785XQt2029288; Tue, 7 Aug 2007 22:33:26 -0700 Received: from 10.136.9.103 ([10.136.9.103]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Wed, 8 Aug 2007 05:33:26 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 08 Aug 2007 14:33:24 +0900 Subject: Re: [lemonade] draft-ietf-lemonade-convert-10.txt From: Eric Burger To: Alexey Melnikov Message-ID: Thread-Topic: [lemonade] draft-ietf-lemonade-convert-10.txt Thread-Index: AcfUVy8NbcBuoEBKEdyoAwAWy4mm/wFJnRoI In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org And the answer is...? This is holding up publication. I *really* want to get this done... On 8/1/07 11:15 AM, "Eric Burger" wrote: > I do not sense consensus, other than "you don't get it" and "yes, but you > don't get it." > > I think Mark may have presented the root cause for the confusion. > > Can we work our way out of this one? > > On 7/31/07 11:41 AM, "Mark Crispin" wrote: > >> On Tue, 31 Jul 2007, Alexey Melnikov wrote: >>> I actually remembered the true reason why I've used a single token - because >>> of the default conversion (which is NIL). Handling silly states is worse >>> (e.g. "text" NIL), etc. >> >> TEXT is not a valid MIME type/subtype specifier. Neither is TEXT/NIL. >> >> The underlying bug is that you have NIL as a default, rather than >> specified defaults. >> >> -- Mark -- >> >> http://panda.com/mrc >> Democracy is two wolves and a sheep deciding what to eat for lunch. >> Liberty is a well-armed sheep contesting the vote. >> >> >> _______________________________________________ >> lemonade mailing list >> lemonade@ietf.org >> https://www1.ietf.org/mailman/listinfo/lemonade >> Supplemental Web Site: >> http://www.standardstrack.com/ietf/lemonade > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 08 05:15:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIhbY-0001iA-N4; Wed, 08 Aug 2007 05:13:24 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IIhbV-0001hs-E7 for lemonade-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 05:13:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIhbU-0001hj-VR for lemonade@ietf.org; Wed, 08 Aug 2007 05:13:20 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IIhbU-0001LW-EU for lemonade@ietf.org; Wed, 08 Aug 2007 05:13:20 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 8 Aug 2007 10:13:18 +0100 Message-ID: <46B98968.1050109@isode.com> Date: Wed, 08 Aug 2007 10:14:16 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] draft-ietf-lemonade-convert-10.txt References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Eric Burger wrote: >And the answer is...? > >This is holding up publication. I *really* want to get this done... > > Due to other committments I need at least 2 weeks to address issues raised by Chris. Based on private discussions with Mark I will try to address Lyndon's issue in a different way. But if Lyndon doesn't like it, oh well. >On 8/1/07 11:15 AM, "Eric Burger" wrote: > > >>I do not sense consensus, other than "you don't get it" and "yes, but you >>don't get it." >> >>I think Mark may have presented the root cause for the confusion. >> >>Can we work our way out of this one? >> >>On 7/31/07 11:41 AM, "Mark Crispin" wrote: >> >> >>>On Tue, 31 Jul 2007, Alexey Melnikov wrote: >>> >>> >>>>I actually remembered the true reason why I've used a single token - because >>>>of the default conversion (which is NIL). Handling silly states is worse >>>>(e.g. "text" NIL), etc. >>>> >>>> >>>TEXT is not a valid MIME type/subtype specifier. Neither is TEXT/NIL. >>> >>>The underlying bug is that you have NIL as a default, rather than >>>specified defaults. >>> >>> _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Aug 09 14:17:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJCXz-0006Qo-Tn; Thu, 09 Aug 2007 14:15:47 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IJCXl-0005s3-V3 for lemonade-confirm+ok@megatron.ietf.org; Thu, 09 Aug 2007 14:15:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJCXl-0005rn-Gc; Thu, 09 Aug 2007 14:15:33 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJCXk-00005E-Bd; Thu, 09 Aug 2007 14:15:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 3DBE7328DD; Thu, 9 Aug 2007 18:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IJCXG-000482-2M; Thu, 09 Aug 2007 14:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 09 Aug 2007 14:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-rfc2192bis-09.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : IMAP URL Scheme Author(s) : C. Newman, A. Melnikov Filename : draft-ietf-lemonade-rfc2192bis-09.txt Pages : 32 Date : 2007-8-9 IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mail- ing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. This document obsoletes RFC 2192. It also updates RFC 4467. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-rfc2192bis-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-rfc2192bis-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-rfc2192bis-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-8-9133402.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-rfc2192bis-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-rfc2192bis-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-8-9133402.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Mon Aug 13 16:41:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKghW-0006rQ-Mj; Mon, 13 Aug 2007 16:39:46 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IKghV-0006rI-Bt for lemonade-confirm+ok@megatron.ietf.org; Mon, 13 Aug 2007 16:39:45 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKghV-0006rA-1x for lemonade@ietf.org; Mon, 13 Aug 2007 16:39:45 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKghU-00069o-LU for lemonade@ietf.org; Mon, 13 Aug 2007 16:39:44 -0400 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l7DKdaQ9008249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2007 13:39:37 -0700 Received: from [[192.168.1.13]] (vpn-10-50-0-28.qualcomm.com [10.50.0.28]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l7DKdXId028914; Mon, 13 Aug 2007 13:39:35 -0700 (PDT) Mime-Version: 1.0 Message-Id: X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 13 Aug 2007 13:39:30 -0700 To: "lemonade@ietf.org" From: Randall Gellens Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: Alexey Melnikov , Glenn Parsons Subject: [lemonade] msgevent draft X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Per the discussion in Chicago, I've updated the msgevent draft to -05, resolving and removing the last two editor's notes. It is available as . I plan on submitting it later this week, so if anyone has a chance to read it in the next few days and send me a comment or correction, I'd appreciate it. I believe this document is now ready for WGLC. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Liberals are trusting and optimistic because they believe other people are much like themselves. Conservatives are hostile and fearful because they believe the same thing. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Aug 13 18:17:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKiCP-0000K3-E2; Mon, 13 Aug 2007 18:15:45 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IKiCO-0000Jy-Oi for lemonade-confirm+ok@megatron.ietf.org; Mon, 13 Aug 2007 18:15:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKiCO-0000Jq-FA for lemonade@ietf.org; Mon, 13 Aug 2007 18:15:44 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKiCN-0007Tw-1w for lemonade@ietf.org; Mon, 13 Aug 2007 18:15:44 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l7DMFcS9019462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2007 15:15:39 -0700 Received: from [[192.168.1.13]] (vpn-10-50-0-28.qualcomm.com [10.50.0.28]) by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l7DMFZhM017167; Mon, 13 Aug 2007 15:15:36 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: <46AF2964.3000106@rename-it.nl> References: <46AF2964.3000106@rename-it.nl> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 13 Aug 2007 15:14:40 -0700 To: Stephan Bosch , Eric Burger From: Randall Gellens Subject: Re: [lemonade] IMAP-SIEVE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org At 2:21 PM +0200 7/31/07, Stephan Bosch wrote: > IMAPSieve currently only suggests running sieve scripts when > certain IMAP commands are executed, apart from running a sieve > script upon delivery. What I currently miss in the Sieve world is > the ability for a client to simply run a sieve script on a folder > when requested by the user (i.e. by issueing a new IMAP command). > Many mail clients that support some form of filtering also include > functionality to apply the currently defined filters on a specific > folder or a set of messages. This is especially useful when the > current filterset has misdelivered a large number of messages to a > specific folter; the user can fix this by updating the filters > accordingly and applying the filters to the folder in question. Of > course the mail client could do this using a sequence of IMAP > commands, but this does not test the new Sieve script on the server. This would be useful. Perhaps the way to proceed would be to write a new draft that is an extension to IMAP and IMAPSieve that executes a specified Sieve script (specified by its metadata item) on a set of messages? -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Two things are infinite: the universe and human stupidity; and I'm not even sure about the universe. --Albert Einstein _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Aug 13 18:43:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKibP-0005Sc-P0; Mon, 13 Aug 2007 18:41:35 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IKibO-0005SX-5K for lemonade-confirm+ok@megatron.ietf.org; Mon, 13 Aug 2007 18:41:34 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKibN-0005SP-R8 for lemonade@ietf.org; Mon, 13 Aug 2007 18:41:33 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKibN-0001VU-2u for lemonade@ietf.org; Mon, 13 Aug 2007 18:41:33 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l7DMfUxE003810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2007 15:41:31 -0700 Received: from [[192.168.1.13]] (vpn-10-50-0-28.qualcomm.com [10.50.0.28]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l7DMfTgv013658; Mon, 13 Aug 2007 15:41:30 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 13 Aug 2007 15:40:11 -0700 To: "lemonade@ietf.org" From: Randall Gellens Subject: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: Barry Leiba X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org As promised (or threatened), here is a proposal for modifying the IMAP-Sieve draft to accomodate per-client scripts: In Section 2.3.1: OLD: When an applicable event occurs on an IMAP mailbox, if there is an IMAP metadata entry named "/IMAPSieve/Script" for the mailbox, that entry is used. If there is not, but there is an IMAP metadata entry named "/IMAPSieve/Script" for the server, that entry is used (providing a way to define a gobal script for all mailboxes on a server). If neither entry exists, then no script will be invoked. NEW: When an applicable event occurs on an IMAP mailbox, all IMAP metadata entries below the "/IMAPSieve/Script/client/" hierarchy for the mailbox are run. If no per-client scripts exist, the implementation checks for an IMAP metadata entry named "/IMAPSieve/Script" first on the mailbox, and second on the server. If one is found, it is used. This provides for per-client scripts on each mailbox, with a generic per-mailbox script, and a global script for all mailboxes on a server as defaults. If none exist, then no script is invoked. The entry name below ""/IMAPSieve/Script/client/" SHOULD be named .. For example, "Eudora.FC2302". ---------- OLD: Only one Sieve script may be defined per mailbox, eliminating the complexity and possible ambiguity involved with coordinating the results of multiple scripts. Any sub-filtering is done in the Sieve script. For example, if it's only necessary to deal with flag changes, but not with new messages appended or copied, the Sieve script will still be invoked for all events, and the script is responsible for checking the event type. NEW: Multiple Sieve script may be defined per mailbox, allowing each client to create a small scripts to serve the user, with freedom to modify or delete its script at any time. Any sub-filtering is done in the Sieve script. For example, if it's only necessary to deal with flag changes, but not with new messages appended or copied, the Sieve script will still be invoked for all events, and the script is responsible for checking the event type. ---------- In multiple sections, the text "The implementation MAY then expunge the original message" should be replaced with "After all Sieve scripts have run, the implementation MAY then expunge the original message". This allows each Sieve script to operate on the message. One or more of the scripts may mark the message as \deleted, and after all have run, the message MAY be expunged. ---------- I also suggest adding a new section, called something such as "Automatic Deletion of Old Scripts": Implementations MAY keep track of the modification date of each script under the "/IMAPSieve/Script/client/" hierarchy of each mailbox. Any script that is older than an implementation-defined period MAY be removed. The expiration period SHOULD be at least ninety days. This allows implementations to prune scripts created by clients no longer in use. Clients SHOULD refresh their scripts at least every eighty days. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Performance is easier to add than clarity. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Aug 13 18:52:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKik5-0003C8-GS; Mon, 13 Aug 2007 18:50:33 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IKik4-0003C3-R1 for lemonade-confirm+ok@megatron.ietf.org; Mon, 13 Aug 2007 18:50:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKik4-0003Bu-HU for lemonade@ietf.org; Mon, 13 Aug 2007 18:50:32 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKik3-0001Ry-4l for lemonade@ietf.org; Mon, 13 Aug 2007 18:50:32 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l7DMoTf9004754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2007 15:50:30 -0700 Received: from [[192.168.1.13]] (vpn-10-50-0-28.qualcomm.com [10.50.0.28]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l7DMoSC3015670; Mon, 13 Aug 2007 15:50:29 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 13 Aug 2007 15:43:21 -0700 To: "lemonade@ietf.org" From: Randall Gellens Subject: [lemonade] IMAP-SIEVE: Script Management Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Currently, the drafts says (in Section 2.3.1): This specifies the mechanism for "activating" a script for a given mailbox (or for all mailboxes), but does not specify a mechanism for creating, storing, or validating the script. Implementations MAY use [Manage] to acomplish this, using the PUTSCRIPT command to store the script without using the SETACTIVE command to activate it. In any case, the script name that is specified in the /IMAPSieve/Script metadata entry is in a form that depends upon how the server handles the storing of Sieve scripts. The problem with this is that the exact name is not specified nor standardized, so it isn't clear what clients should do, and it is also unclear how the scripts are to be managed. In Chicago there were discussions about storing the script itself in a metadata entry, rather than, or in addition to, the script name. Presumably this requires the server to validate the script on storage, and reject invalid scripts immediately. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- The fewer episodes of a TV show one has seen, the greater the chance that one has already viewed the episode one is watching. --Randall Gellens _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 15 00:15:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ILAG5-0007GH-5b; Wed, 15 Aug 2007 00:13:25 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1ILAG3-0007Fl-Sj for lemonade-confirm+ok@megatron.ietf.org; Wed, 15 Aug 2007 00:13:23 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ILAG2-0007F8-Cq; Wed, 15 Aug 2007 00:13:22 -0400 Received: from mail121.messagelabs.com ([216.82.241.195]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILAG0-000523-20; Wed, 15 Aug 2007 00:13:20 -0400 X-VirusChecked: Checked X-Env-Sender: tony@att.com X-Msg-Ref: server-7.tower-121.messagelabs.com!1187151198!22404878!1 X-StarScan-Version: 5.5.12.11; banners=-,-,- X-Originating-IP: [144.160.20.53] Received: (qmail 2919 invoked from network); 15 Aug 2007 04:13:18 -0000 Received: from sbcsmtp6.sbc.com (HELO mlph073.enaf.sfdc.sbc.com) (144.160.20.53) by server-7.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 15 Aug 2007 04:13:18 -0000 Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlph073.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l7F4DIuN004781; Wed, 15 Aug 2007 00:13:18 -0400 Received: from mlph070.sfdc.sbc.com (mlph070.sfdc.sbc.com [144.155.224.139]) by mlph073.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l7F4DEI0004472; Wed, 15 Aug 2007 00:13:15 -0400 Received: from sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlph070.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l7F4DEd2001037; Wed, 15 Aug 2007 00:13:14 -0400 Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by mlph070.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l7F4DCAU000524; Wed, 15 Aug 2007 00:13:12 -0400 Received: from [135.210.112.131] (unknown[135.210.112.131](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20070815041310gw10010gb2e> (Authid: tony); Wed, 15 Aug 2007 04:13:12 +0000 Message-ID: <46C27D22.2080103@att.com> Date: Wed, 15 Aug 2007 00:12:18 -0400 From: Tony Hansen User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: ietf-822 mailing list References: <46A82184.7030200@att.com> In-Reply-To: <46A82184.7030200@att.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: LEMONADE WG , POP3 extensions mailing list , USEFOR WG , EAI WG , IMAP extensions mailing list , SMTP Interest Group , SIMPLE WG Subject: [lemonade] Re: Mailing List Last Call for 2822 update internet-draft X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The mailing list last call for the 2822 update is now over. I believe we have mailing list consensus on the issues that have been raised during the last call. After an updated draft is posted by Pete, we'll be moving the draft forward to IETF last call. Tony Tony Hansen wrote: > There have been some comments on draft-resnick-2822upd-* but they have > dwindled down to none. > > This is a "formal" Mailing List Last Call on > draft-resnick-2822upd-02.txt. The last call will last for two weeks > time, ending on August 10, 2007. > > The document will be discussed on the 822 mailing list, > . Please send your comments there. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Aug 17 10:15:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IM2Zj-0003dD-Va; Fri, 17 Aug 2007 10:13:19 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IM2Zi-0003cg-Sa for lemonade-confirm+ok@megatron.ietf.org; Fri, 17 Aug 2007 10:13:18 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IM2Zi-0003cY-IP for lemonade@ietf.org; Fri, 17 Aug 2007 10:13:18 -0400 Received: from e33.co.us.ibm.com ([32.97.110.151]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IM2Zi-000093-6n for lemonade@ietf.org; Fri, 17 Aug 2007 10:13:18 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7HEDHVO026162 for ; Fri, 17 Aug 2007 10:13:17 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l7HEDGcK213700 for ; Fri, 17 Aug 2007 08:13:16 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l7HEDGD0027037 for ; Fri, 17 Aug 2007 08:13:16 -0600 Received: from poplar (poplar.watson.ibm.com [9.2.40.57]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l7HEDFUR026971; Fri, 17 Aug 2007 08:13:16 -0600 Received: from wecm-9-67-214-1.wecm.ibm.com ([9.67.214.1]) by poplar.watson.ibm.com (IMF.2005.07.16.1050.haw) with SMTP ID IMFd1187360000.5136; Fri, 17 Aug 2007 10:13:20 -0400 Message-ID: <46C5ACFC.2040300@watson.ibm.com> Date: Fri, 17 Aug 2007 10:13:16 -0400 From: Barry Leiba User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Stephan Bosch Subject: Re: [lemonade] IMAP-SIEVE References: <46AF2964.3000106@rename-it.nl> In-Reply-To: <46AF2964.3000106@rename-it.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org > IMAPSieve currently only suggests running sieve scripts when certain > IMAP commands are executed Actually, that's not quite true. IMAPSieve defines events that are triggered by IMAP commands. Maybe I should make the text say that more clearly. > What I currently miss in the Sieve world is the ability for a > client to simply run a sieve script on a folder when requested by the > user (i.e. by issueing a new IMAP command). I think Randy has the right answer here: write a draft that extends IMAP and IMAPSieve... it creates a new IMAP command that generates an new IMAPSieve event. Barry _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Aug 20 05:55:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN3xN-00066E-PW; Mon, 20 Aug 2007 05:53:57 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IN3xM-000669-Qf for lemonade-confirm+ok@megatron.ietf.org; Mon, 20 Aug 2007 05:53:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN3xM-000661-H9 for lemonade@ietf.org; Mon, 20 Aug 2007 05:53:56 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IN3xK-0007bG-V5 for lemonade@ietf.org; Mon, 20 Aug 2007 05:53:56 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Mon, 20 Aug 2007 10:53:51 +0100 Message-ID: <46C964E3.4030907@isode.com> Date: Mon, 20 Aug 2007 10:54:43 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Chris Newman Subject: Re: [lemonade] draft-ietf-lemonade-convert-10.txt References: <0B34875167649991F7DF9790@446E7922C82D299DB29D899F> In-Reply-To: <0B34875167649991F7DF9790@446E7922C82D299DB29D899F> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Chris Newman wrote: > As a technical contributor (not AD), some suggestions for this document: > > * I suggest removing the non-BINARY fetch items. Forcing a server to > base64-decode, convert, then base64-encode when the chance a client > needs it base64-encoded is probably nil seems like unnecessary > protocol/server complexity. Done. > * The syntax for specifying a conversion is pretty verbose > (necessarily). If it's necessary to fetch or reply with more than one > convert item for the same part (e.g. BODYPARTSTRUCTURE and BINARY), > then the client has to repeat the same conversion specifier multiple > times in the same response. A syntax that made the part specifier > only appear once would be more concise, e.g.: > > * 2 CONVERTED [3 ("text/plain" ("charset" "us-ascii" > "unknown-character-replacement" "?"))] BODYPARTSTRUCTURE (...) BODY ... > instead of > * 2 CONVERTED (BODYPARTSTRUCTURE[3 ("text/plain" ("charset" "us-ascii" > "unknown-character-replacement" "?"))] ... BODY[3 ("text/plain" > ("charset" "us-ascii" "unknown-character-replacement" "?"))] ... > > * Saying that "servers MAY disallow a request to perform multiple > different conversions of the same bodypart at once" is an interop > problem as clients that request that will get unpredictable behavior > if they issue such a command. It would be simpler to just disallow > this altogether. Both done. The target MIME type and conversion parameters are now a separate [complex] parameter to CONVERT/UID CONVERT. The second change is a side effect of the new syntax. > * This is missing a security consideration -- When the client requests > a server-side conversion of a signed body part (e.g. a part inside > multipart/signed), there is no way for the client to verify that the > converted content is authentic. The client is fully trusting the > server in this case. The alterative is for the client to download the > signed object, verify the signature and perform the conversion on the > client. This is a direct security vs. efficiency/convenience tradeoff > with both options important to a subset of the user base. I've already addressed this change earlier. > * An observation -- IMAP BODYSTRUCTURE splits MIME "type" and > "subtype" into two separate fields. The CONVERT part specifier uses > the "type/subtype" syntax. This isn't consistent. I want to verify > the inconsistency is intentional and has WG rough consensus. The new syntax of the CONVERTED untagged response includes "convert correlator" instead, so this issue is resolved. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Aug 27 14:51:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjeI-00068V-Rc; Mon, 27 Aug 2007 14:49:18 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IPjeG-000688-LS for lemonade-confirm+ok@megatron.ietf.org; Mon, 27 Aug 2007 14:49:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjeG-00067v-Bg; Mon, 27 Aug 2007 14:49:16 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPjeF-0001Ti-PX; Mon, 27 Aug 2007 14:49:16 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id A126126E3D; Mon, 27 Aug 2007 18:49:15 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IPjeF-00062o-II; Mon, 27 Aug 2007 14:49:15 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 27 Aug 2007 14:49:15 -0400 X-Spam-Score: -1.4 (-) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Cc: lemonade mailing list , lemonade chair , Internet Architecture Board , RFC Editor Subject: [lemonade] Protocol Action: 'IMAP URL Scheme' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The IESG has approved the following document: - 'IMAP URL Scheme ' as a Proposed Standard This document is the product of the Enhancements to Internet email to Support Diverse Service Environments Working Group. The IESG contact persons are Lisa Dusseault and Chris Newman. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-rfc2192bis-09.txt Technical Summary IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. This document obsoletes RFC 2192 and updates RFC 4467. Working Group Summary This document removed support for IMAP URLs for listing the contents of a mailbox. There was a clear consensus that this feature (originally described in RFC 2192) was never implemented. Some of the changes to the document were a result of the Lemonade interoperability event of October 2006 held in London, England. Protocol Quality The document received several positive reviews. In particular it is worth noting Ted Hardie and Zoltan Ordogh have done detailed reviews of the document. This document addresses all issues raised. Eric Burger shepherds this document on behalf of Lisa Dusseault, the responsible Area Director. Lisa and Eric reviewed this document and believe it is ready for forwarding to the IESG for publication. Note to RFC Editor In section 6.1.1.1, first paragraph, last sentence: OLD: The authorization token is generated from the URL, the authorized access identifer, authoriza- ^^^^^^^^^ tion mechanism name, and a mailbox access key. NEW: The authorization token is generated from the URL, the authorized access identifier, autho- ^^^^^^^^^^ rization mechanism name, and a mailbox access key. (typo in the word "identifier") In section 6.1.1.2, replace the first paragraph: OLD: The mailbox access key is a random string with at least 128 bits of entropy. It is generated by software (not by the human user), and MUST be unpredictable. NEW: The mailbox access key is an unpredictable, random string. To ensure unpredictability, the random string with at least 128 bits of entropy is generated by software or hardware (not by the human user). In section 9.1, 9th paragraph: OLD: The following edge case example demostrates that the ;UIDVALIDITY= ^^^^^^^^^^^ modifier is a part of the mailbox name as far as relative URI reso- lution is concerned: NEW: The following edge case example demonstrates that the ;UIDVALIDITY= ^^^^^^^^^^^^ modifier is a part of the mailbox name as far as relative URI reso- lution is concerned: typo: demonstrates In section 10.1, first paragraph, replace the last sentence: OLD: Use of either of these access identi- fiers makes it impossible for an attacker, spying on the session, to use the same URL, either directly or by submission to a message submission entity. NEW: Use of either of these mechanisms limits the scope of the URL. An attacker who cannot authenticate using the appropriate credentials cannot make use of the URL. In section 12.1, 13th paragraph: OLD: A widely deployed IMAP client Netscape Mail (and possibly Mozilla/ Thubderbird/Seamonkey) use a different imap: scheme inter- ^ ^ nally. NEW: A widely deployed IMAP client Netscape Mail (and possibly Mozilla/Thunderbird/Seamonkey) use a different imap: scheme inter- ^ ^ nally. (typo in Thunderbird, also remove an extra space) In Appendix D, third paragraph, add: OLD: Editors would like to thank Mark Crispin, Ken Murchison, Ted Hardie, Zoltan Ordogh, Dave Cridland, Kjetil Torgrim Homme, Lisa Dusseault, Spencer Dawkins, Filip Navara and Shawn M. Emery for the ^^^ time they devoted to reviewing of this document and/or for the com- ments received. NEW: Editors would like to thank Mark Crispin, Ken Murchison, Ted Hardie, Zoltan Ordogh, Dave Cridland, Kjetil Torgrim Homme, Lisa Dusseault, Spencer Dawkins, Filip Navara, Shawn M. Emery, Sam Hartman, ^ ^^^^^^^^^^^^^ Russ Housley and Lars Eggert for the time they devoted to ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ reviewing of this document and/or for the comments received. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Tue Aug 28 16:16:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQ7T2-0005sU-Lt; Tue, 28 Aug 2007 16:15:16 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQ7Sp-0005dn-Je for lemonade-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 16:15:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQ7Sp-0005dI-3C; Tue, 28 Aug 2007 16:15:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQ7So-0006uZ-Kr; Tue, 28 Aug 2007 16:15:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6F3AC2AC69; Tue, 28 Aug 2007 20:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IQ7So-0006w3-0D; Tue, 28 Aug 2007 16:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 28 Aug 2007 16:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-convert-11.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : IMAP CONVERT extension Author(s) : S. Maes, et al. Filename : draft-ietf-lemonade-convert-11.txt Pages : 0 Date : 2007-8-28 CONVERT defines extensions to IMAP allowing clients to request adaptation and/or transcoding of attachments. Clients can specify the conversion details or allow servers to decide based on knowledge of client capabilities, on user or administrator preferences or its settings. This document also extends IMAP URL schema defined in draft-ietf-lemonade-rfc2192bis-XX.txt with a specifier for a converted body part. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-11.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-convert-11.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-convert-11.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-8-28150415.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-convert-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-convert-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-8-28150415.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Wed Aug 29 04:31:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQIvT-0003NJ-Ni; Wed, 29 Aug 2007 04:29:23 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQIvR-0003Mg-SB for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 04:29:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQIvQ-0003MY-PN for lemonade@ietf.org; Wed, 29 Aug 2007 04:29:21 -0400 Received: from kalyani.oryx.com ([195.30.37.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQIvP-0000Nh-1T for lemonade@ietf.org; Wed, 29 Aug 2007 04:29:20 -0400 Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id DFA124AD24 for ; Wed, 29 Aug 2007 10:29:15 +0200 (CEST) Message-Id: Date: Wed, 29 Aug 2007 10:30:19 +0200 From: Arnt Gulbrandsen To: lemonade@ietf.org References: <18269.1188373437.581860@peirce.dave.cridland.net> In-Reply-To: <18269.1188373437.581860@peirce.dave.cridland.net> Content-Type: text/plain; format=flowed MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [lemonade] Re: profile-bis and ipv6 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org I wrote this to the esteemed profile-bis authors privately: >> Hi, >> >> I think you should add "must support ipv6" to lemonade profile-bis: >> >> - clients MUST understand AAAA records in DNS lookup results >> - if a client or server uses IP addresses in local configuration >> files or elsewhere then it MUST support both IPv4 and IPv6 addresses >> there >> - servers MUST be able to listen on IPv6 addresses >> - clients MUST be able to connect to IPv6 addresses >> - clients MAY prefer either IPv4 or IPv6 if both are available for a >> given server >> >> It's too late to pretend we live in an IPv4-only world. I will not be >> shocked if the IANA runs out of addresses next year, and next year >> is _soon_. (I know most people expect it to happen in 2009 or 2010, >> but I think there's >10% probability that the IANA runs out before >> Christmas 2008.) Dave agrees, but suggested that I raise it on the list. Arnt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 29 04:50:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQJDv-0000RF-Gd; Wed, 29 Aug 2007 04:48:27 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQJDt-0000OT-N1 for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 04:48:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQJDs-0000OK-Uo for lemonade@ietf.org; Wed, 29 Aug 2007 04:48:24 -0400 Received: from [2001:838:378:0:2a0:d2ff:fe1b:110f] (helo=turner.dave.cridland.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQJDr-0000hp-T8 for lemonade@ietf.org; Wed, 29 Aug 2007 04:48:24 -0400 Received: from peirce.dave.cridland.net ([217.155.137.61]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id for ; Wed, 29 Aug 2007 09:48:20 +0100 Subject: Re: [lemonade] Re: profile-bis and ipv6 References: <18269.1188373437.581860@peirce.dave.cridland.net> In-Reply-To: MIME-Version: 1.0 Message-Id: <18269.1188377299.947528@peirce.dave.cridland.net> Date: Wed, 29 Aug 2007 09:48:19 +0100 From: Dave Cridland To: Enhancements to Internet email to support diverse service enivronments Content-Type: text/plain; charset="us-ascii"; format="flowed" X-Spam-Score: -1.4 (-) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org On Wed Aug 29 09:30:19 2007, Arnt Gulbrandsen wrote: > I wrote this to the esteemed profile-bis authors privately: > >>> Hi, >>> >>> I think you should add "must support ipv6" to lemonade >>> profile-bis: >>> >>> - clients MUST understand AAAA records in DNS lookup results >>> - if a client or server uses IP addresses in local configuration >>> files or elsewhere then it MUST support both IPv4 and IPv6 >>> addresses there >>> - servers MUST be able to listen on IPv6 addresses >>> - clients MUST be able to connect to IPv6 addresses >>> - clients MAY prefer either IPv4 or IPv6 if both are available >>> for a given server >>> >>> It's too late to pretend we live in an IPv4-only world. I will >>> not be shocked if the IANA runs out of addresses next year, and >>> next year is _soon_. (I know most people expect it to happen in >>> 2009 or 2010, but I think there's >10% probability that the IANA >>> runs out before Christmas 2008.) > > Dave agrees, but suggested that I raise it on the list. For the record, I said that I agree with the sentiment, and I also noted that mobile operating systems in general appear to be IPv6 capable. (Symbian seems to have the support, for example). Something I didn't point out to Arnt was that, currently, the Profile itself doesn't mandate anything on clients - the most we have is a SHOULD. In the case where a target operating system, or simply a target device, doesn't support IPv6, a MUST will be impossible to implement, so SHOULD is quite likely to be a better level. I'm happy to mandate it for servers, bearing in mind that we're only dealing with IMAP and Submission ports here, not full IPv6 MTAs, which would be substantially more work. Speaking as an editor, I'd feel more comfortable adding this if there were visible consensus. Dave. -- Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 29 05:13:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQJaH-0002oP-9C; Wed, 29 Aug 2007 05:11:33 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQJaG-0002oI-PO for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 05:11:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQJaG-0002oA-CP for lemonade@ietf.org; Wed, 29 Aug 2007 05:11:32 -0400 Received: from kalyani.oryx.com ([195.30.37.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQJaE-00017D-VM for lemonade@ietf.org; Wed, 29 Aug 2007 05:11:32 -0400 Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 2E7DC4AD28 for ; Wed, 29 Aug 2007 11:11:30 +0200 (CEST) Message-Id: Date: Wed, 29 Aug 2007 11:12:34 +0200 From: Arnt Gulbrandsen To: lemonade@ietf.org Subject: Re: [lemonade] Re: profile-bis and ipv6 References: <18269.1188373437.581860@peirce.dave.cridland.net> <18269.1188377299.947528@peirce.dave.cridland.net> In-Reply-To: <18269.1188377299.947528@peirce.dave.cridland.net> Content-Type: text/plain; format=flowed MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Dave Cridland writes: > Something I didn't point out to Arnt was that, currently, the Profile > itself doesn't mandate anything on clients - the most we have is a > SHOULD. IMO that's because noone felt it necessary to say things like "MUST support IMAP over TCP". Perhaps SHOULD is enough. I'm not sure I care about SHOULD vs. MUST. > In the case where a target operating system, or simply a target > device, doesn't support IPv6, a MUST will be impossible to implement, > so SHOULD is quite likely to be a better level. I phrased my suggested MUSTs so that individual devices and connections don't matter (if DHCP or PPP gives you only an IPv4 address, that's OK), but target operating systems are required to support IPv6 (e.g. a mail reader cannot fail to compile, link or install merely because it uses an IPv6 API). Arnt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 29 13:00:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQQsa-0006xJ-Bv; Wed, 29 Aug 2007 12:58:56 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQQsZ-0006xD-Bx for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 12:58:55 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQQsZ-0006x5-12 for lemonade@ietf.org; Wed, 29 Aug 2007 12:58:55 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQQsY-0000VU-EZ for lemonade@ietf.org; Wed, 29 Aug 2007 12:58:54 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 29 Aug 2007 17:58:49 +0100 Message-ID: <46D5A5F8.5010009@isode.com> Date: Wed, 29 Aug 2007 17:59:36 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Dave Cridland Subject: Re: [lemonade] Re: profile-bis and ipv6 References: <18269.1188373437.581860@peirce.dave.cridland.net> <18269.1188377299.947528@peirce.dave.cridland.net> In-Reply-To: <18269.1188377299.947528@peirce.dave.cridland.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: Enhancements to Internet email to support diverse service enivronments X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Dave Cridland wrote: > On Wed Aug 29 09:30:19 2007, Arnt Gulbrandsen wrote: > >> I wrote this to the esteemed profile-bis authors privately: >> >>>> Hi, >>>> >>>> I think you should add "must support ipv6" to lemonade profile-bis: >>>> >>>> - clients MUST understand AAAA records in DNS lookup results >>>> - if a client or server uses IP addresses in local configuration >>>> files or elsewhere then it MUST support both IPv4 and IPv6 >>>> addresses there >>>> - servers MUST be able to listen on IPv6 addresses >>>> - clients MUST be able to connect to IPv6 addresses >>>> - clients MAY prefer either IPv4 or IPv6 if both are available for >>>> a given server >>>> >>>> It's too late to pretend we live in an IPv4-only world. I will not >>>> be shocked if the IANA runs out of addresses next year, and next >>>> year is _soon_. (I know most people expect it to happen in 2009 or >>>> 2010, but I think there's >10% probability that the IANA runs out >>>> before Christmas 2008.) >>> >> Dave agrees, but suggested that I raise it on the list. > > For the record, I said that I agree with the sentiment, and I also > noted that mobile operating systems in general appear to be IPv6 > capable. (Symbian seems to have the support, for example). > > Something I didn't point out to Arnt was that, currently, the Profile > itself doesn't mandate anything on clients - the most we have is a > SHOULD. In the case where a target operating system, or simply a > target device, doesn't support IPv6, a MUST will be impossible to > implement, so SHOULD is quite likely to be a better level. Historically we didn't put any requirements on clients. A client implementing IMAP IDLE can claim to be Lemonade compliant ... > I'm happy to mandate it for servers, bearing in mind that we're only > dealing with IMAP and Submission ports here, not full IPv6 MTAs, which > would be substantially more work. +1. > Speaking as an editor, I'd feel more comfortable adding this if there > were visible consensus. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 29 13:13:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQR4c-000336-N2; Wed, 29 Aug 2007 13:11:22 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQR4b-0002u8-91 for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 13:11:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQR4a-0002t2-Ta for lemonade@ietf.org; Wed, 29 Aug 2007 13:11:20 -0400 Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQR4Z-0007aw-E9 for lemonade@ietf.org; Wed, 29 Aug 2007 13:11:20 -0400 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l7THBAM0020021; Wed, 29 Aug 2007 20:11:16 +0300 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Aug 2007 20:10:31 +0300 Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Aug 2007 12:10:30 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] Re: profile-bis and ipv6 Date: Wed, 29 Aug 2007 12:10:29 -0500 Message-ID: <0AC25B27A4FD2E4B839C9FAF2C704DBA01D61192@daebe103.NOE.Nokia.com> In-Reply-To: <46D5A5F8.5010009@isode.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] Re: profile-bis and ipv6 Thread-Index: AcfqXfbyvUNN+6Z6QIa94RFm4gIBowAAKAJw References: <18269.1188373437.581860@peirce.dave.cridland.net><18269.1188377299.947528@peirce.dave.cridland.net> <46D5A5F8.5010009@isode.com> From: To: , X-OriginalArrivalTime: 29 Aug 2007 17:10:30.0081 (UTC) FILETIME=[806DA310:01C7EA5F] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Hi, The OMA has a general requirement that all enablers be IPv6 compliant. >From the OMA perspective, if its not specifically mentioned in profile-bis, we will have to include this requirement on top of profile-bis.=20 I would support adding ipv6 compliance to profile bis as described by Arnt. Thanks,=20 Dorothy > -----Original Message----- > From: ext Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20 > Sent: Wednesday, August 29, 2007 10:00 AM > To: Dave Cridland > Cc: Enhancements to Internet email to support diverse service=20 > enivronments > Subject: Re: [lemonade] Re: profile-bis and ipv6 >=20 > Dave Cridland wrote: >=20 > > On Wed Aug 29 09:30:19 2007, Arnt Gulbrandsen wrote: > > > >> I wrote this to the esteemed profile-bis authors privately: > >> > >>>> Hi, > >>>> > >>>> I think you should add "must support ipv6" to lemonade=20 > profile-bis: > >>>> > >>>> - clients MUST understand AAAA records in DNS lookup results > >>>> - if a client or server uses IP addresses in local configuration=20 > >>>> files or elsewhere then it MUST support both IPv4 and IPv6=20 > >>>> addresses there > >>>> - servers MUST be able to listen on IPv6 addresses > >>>> - clients MUST be able to connect to IPv6 addresses > >>>> - clients MAY prefer either IPv4 or IPv6 if both are=20 > available for=20 > >>>> a given server > >>>> > >>>> It's too late to pretend we live in an IPv4-only world.=20 > I will not=20 > >>>> be shocked if the IANA runs out of addresses next year, and next=20 > >>>> year is _soon_. (I know most people expect it to happen=20 > in 2009 or=20 > >>>> 2010, but I think there's >10% probability that the IANA=20 > runs out=20 > >>>> before Christmas 2008.) > >>> > >> Dave agrees, but suggested that I raise it on the list. > > > > For the record, I said that I agree with the sentiment, and I also=20 > > noted that mobile operating systems in general appear to be IPv6=20 > > capable. (Symbian seems to have the support, for example). > > > > Something I didn't point out to Arnt was that, currently,=20 > the Profile=20 > > itself doesn't mandate anything on clients - the most we have is a=20 > > SHOULD. In the case where a target operating system, or simply a=20 > > target device, doesn't support IPv6, a MUST will be impossible to=20 > > implement, so SHOULD is quite likely to be a better level. >=20 > Historically we didn't put any requirements on clients. A=20 > client implementing IMAP IDLE can claim to be Lemonade compliant ... >=20 > > I'm happy to mandate it for servers, bearing in mind that=20 > we're only=20 > > dealing with IMAP and Submission ports here, not full IPv6=20 > MTAs, which=20 > > would be substantially more work. >=20 > +1. >=20 > > Speaking as an editor, I'd feel more comfortable adding=20 > this if there=20 > > were visible consensus. >=20 >=20 >=20 >=20 > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade >=20 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Wed Aug 29 17:13:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUpA-0004vj-00; Wed, 29 Aug 2007 17:11:40 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQUp6-0004r5-Ba for lemonade-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 17:11:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUp4-0004oL-5F; Wed, 29 Aug 2007 17:11:35 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQUp2-00023u-VJ; Wed, 29 Aug 2007 17:11:34 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id 90CF4E0447; Wed, 29 Aug 2007 14:09:41 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20070829210941.90CF4E0447@bosco.isi.edu> Date: Wed, 29 Aug 2007 14:09:41 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: lemonade@ietf.org, rfc-editor@rfc-editor.org Subject: [lemonade] RFC 4978 on The IMAP COMPRESS Extension X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4978 Title: The IMAP COMPRESS Extension Author: A. Gulbrandsen Status: Standards Track Date: August 2007 Mailbox: arnt@oryx.com Pages: 9 Characters: 17554 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-compress-08.txt URL: http://www.rfc-editor.org/rfc/rfc4978.txt The COMPRESS extension allows an IMAP connection to be effectively and efficiently compressed. [STANDARDS TRACK] This document is a product of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Aug 30 04:29:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfNg-0005Ho-Nr; Thu, 30 Aug 2007 04:28:00 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQfNf-0005Hg-2A for lemonade-confirm+ok@megatron.ietf.org; Thu, 30 Aug 2007 04:27:59 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfNe-0005HX-6z for lemonade@ietf.org; Thu, 30 Aug 2007 04:27:58 -0400 Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQfNd-0007Jr-CQ for lemonade@ietf.org; Thu, 30 Aug 2007 04:27:58 -0400 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l7U8RcVG015234; Thu, 30 Aug 2007 11:27:55 +0300 Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 11:27:48 +0300 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 11:27:48 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Date: Thu, 30 Aug 2007 11:27:13 +0300 Message-ID: <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47E8@esebe199.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Thread-Index: Acfd+x9bqTzVzN/7Tr2VjiYARUlqDQM449wg References: From: To: , X-OriginalArrivalTime: 30 Aug 2007 08:27:48.0063 (UTC) FILETIME=[A59F36F0:01C7EADF] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Cc: leiba@watson.ibm.com X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Questions/comments: What is the execution order of the scripts (last modification = date/alphabetical/etc)? I am asking this because one script might move = an email while another might notify it - which one happens first... What if there are two scripts and: both want to send a notification, and = to the same/different addresses? Which will be sent? Both? The original text refers to these problems as: " complexity and possible = ambiguity involved with coordinating the results of multiple scripts". Should these problems be elaborated in more detail and - hopefully - = provide a standardized behavior? Thank You. Best regards: Zolt=E1n =D6rd=F6gh E-mail: zoltan dot ordogh at nokia dot com Phone: +358 50 386 0566 =20 >-----Original Message----- >From: ext Randall Gellens [mailto:randy@qualcomm.com]=20 >Sent: 14 August, 2007 01:40 >To: lemonade@ietf.org >Cc: Barry Leiba >Subject: [lemonade] IMAP-SIEVE: Per-Client Sieve Script > >As promised (or threatened), here is a proposal for modifying=20 >the IMAP-Sieve draft to accomodate per-client scripts: > >In Section 2.3.1: > >OLD: > When an applicable event occurs on an IMAP mailbox, if there is an > IMAP metadata entry named "/IMAPSieve/Script" for the mailbox, that > entry is used. If there is not, but there is an IMAP=20 >metadata entry > named "/IMAPSieve/Script" for the server, that entry is used > (providing a way to define a gobal script for all mailboxes on a > server). If neither entry exists, then no script will be invoked. > >NEW: > When an applicable event occurs on an IMAP mailbox, all IMAP > metadata entries below the "/IMAPSieve/Script/client/" hierarchy > for the mailbox are run. If no per-client scripts exist, the > implementation checks for an IMAP metadata entry named > "/IMAPSieve/Script" first on the mailbox, and second on the > server. If one is found, it is used. This provides for > per-client scripts on each mailbox, with a generic per-mailbox > script, and a global script for all mailboxes on a server as > defaults. If none exist, then no script is invoked. > > The entry name below ""/IMAPSieve/Script/client/" SHOULD be > named .. For example, "Eudora.FC2302". > >---------- > >OLD: > Only one Sieve script may be defined per mailbox, eliminating the > complexity and possible ambiguity involved with coordinating the > results of multiple scripts. Any sub-filtering is done in=20 >the Sieve > script. For example, if it's only necessary to deal with flag > changes, but not with new messages appended or copied, the Sieve > script will still be invoked for all events, and the script is > responsible for checking the event type. > >NEW: > Multiple Sieve script may be defined per mailbox, allowing each > client to create a small scripts to serve the user, with freedom > to modify or delete its script at any time. > > Any sub-filtering is done in the Sieve script. For example, if > it's only necessary to deal with flag changes, but not with new > messages appended or copied, the Sieve script will still be > invoked for all events, and the script is responsible for > checking the event type. > >---------- > >In multiple sections, the text "The implementation MAY then=20 >expunge the original message" should be replaced with "After=20 >all Sieve scripts have run, the implementation MAY then=20 >expunge the original message". This allows each Sieve script=20 >to operate on the message.=20 >One or more of the scripts may mark the message as \deleted,=20 >and after all have run, the message MAY be expunged. > >---------- > >I also suggest adding a new section, called something such as=20 >"Automatic Deletion of Old Scripts": > > Implementations MAY keep track of the modification date of each > script under the "/IMAPSieve/Script/client/" hierarchy of each > mailbox. Any script that is older than an implementation-defined > period MAY be removed. The expiration period SHOULD be at least > ninety days. This allows implementations to prune scripts > created by clients no longer in use. > > Clients SHOULD refresh their scripts at least every eighty days. >-- >Randall Gellens >Opinions are personal; facts are suspect; I speak for myself only >-------------- Randomly-selected tag: ---------------=20 >Performance is easier to add than clarity. > > >_______________________________________________ >lemonade mailing list >lemonade@ietf.org >https://www1.ietf.org/mailman/listinfo/lemonade >Supplemental Web Site: >http://www.standardstrack.com/ietf/lemonade > _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Aug 30 04:35:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfTG-0003Y4-Sd; Thu, 30 Aug 2007 04:33:46 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQfTG-0003Xy-Gf for lemonade-confirm+ok@megatron.ietf.org; Thu, 30 Aug 2007 04:33:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfTF-0003Xp-Ac for lemonade@ietf.org; Thu, 30 Aug 2007 04:33:45 -0400 Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQfTD-0003M7-Po for lemonade@ietf.org; Thu, 30 Aug 2007 04:33:45 -0400 Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l7U8XCAR023874; Thu, 30 Aug 2007 11:33:41 +0300 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 11:33:21 +0300 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 11:33:21 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Date: Thu, 30 Aug 2007 11:32:46 +0300 Message-ID: <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47FB@esebe199.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Thread-Index: Acfd+x9bqTzVzN/7Tr2VjiYARUlqDQM5QLxg References: From: To: , X-OriginalArrivalTime: 30 Aug 2007 08:33:21.0556 (UTC) FILETIME=[6C663540:01C7EAE0] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Cc: leiba@watson.ibm.com X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org One more question if I may: How do You identify (uniquely) which script belongs to which client? I = mean if we can't do this and clients keep overwriting each others' = scripts (because they don't know which one belongs to them), we did not = achieve anything, did we? Best regards: Zolt=E1n =D6rd=F6gh E-mail: zoltan dot ordogh at nokia dot com Phone: +358 50 386 0566 =20 >-----Original Message----- >From: ext Randall Gellens [mailto:randy@qualcomm.com]=20 >Sent: 14 August, 2007 01:40 >To: lemonade@ietf.org >Cc: Barry Leiba >Subject: [lemonade] IMAP-SIEVE: Per-Client Sieve Script > >As promised (or threatened), here is a proposal for modifying=20 >the IMAP-Sieve draft to accomodate per-client scripts: > >In Section 2.3.1: > >OLD: > When an applicable event occurs on an IMAP mailbox, if there is an > IMAP metadata entry named "/IMAPSieve/Script" for the mailbox, that > entry is used. If there is not, but there is an IMAP=20 >metadata entry > named "/IMAPSieve/Script" for the server, that entry is used > (providing a way to define a gobal script for all mailboxes on a > server). If neither entry exists, then no script will be invoked. > >NEW: > When an applicable event occurs on an IMAP mailbox, all IMAP > metadata entries below the "/IMAPSieve/Script/client/" hierarchy > for the mailbox are run. If no per-client scripts exist, the > implementation checks for an IMAP metadata entry named > "/IMAPSieve/Script" first on the mailbox, and second on the > server. If one is found, it is used. This provides for > per-client scripts on each mailbox, with a generic per-mailbox > script, and a global script for all mailboxes on a server as > defaults. If none exist, then no script is invoked. > > The entry name below ""/IMAPSieve/Script/client/" SHOULD be > named .. For example, "Eudora.FC2302". > >---------- > >OLD: > Only one Sieve script may be defined per mailbox, eliminating the > complexity and possible ambiguity involved with coordinating the > results of multiple scripts. Any sub-filtering is done in=20 >the Sieve > script. For example, if it's only necessary to deal with flag > changes, but not with new messages appended or copied, the Sieve > script will still be invoked for all events, and the script is > responsible for checking the event type. > >NEW: > Multiple Sieve script may be defined per mailbox, allowing each > client to create a small scripts to serve the user, with freedom > to modify or delete its script at any time. > > Any sub-filtering is done in the Sieve script. For example, if > it's only necessary to deal with flag changes, but not with new > messages appended or copied, the Sieve script will still be > invoked for all events, and the script is responsible for > checking the event type. > >---------- > >In multiple sections, the text "The implementation MAY then=20 >expunge the original message" should be replaced with "After=20 >all Sieve scripts have run, the implementation MAY then=20 >expunge the original message". This allows each Sieve script=20 >to operate on the message.=20 >One or more of the scripts may mark the message as \deleted,=20 >and after all have run, the message MAY be expunged. > >---------- > >I also suggest adding a new section, called something such as=20 >"Automatic Deletion of Old Scripts": > > Implementations MAY keep track of the modification date of each > script under the "/IMAPSieve/Script/client/" hierarchy of each > mailbox. Any script that is older than an implementation-defined > period MAY be removed. The expiration period SHOULD be at least > ninety days. This allows implementations to prune scripts > created by clients no longer in use. > > Clients SHOULD refresh their scripts at least every eighty days. >-- >Randall Gellens >Opinions are personal; facts are suspect; I speak for myself only >-------------- Randomly-selected tag: ---------------=20 >Performance is easier to add than clarity. > > >_______________________________________________ >lemonade mailing list >lemonade@ietf.org >https://www1.ietf.org/mailman/listinfo/lemonade >Supplemental Web Site: >http://www.standardstrack.com/ietf/lemonade > _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Aug 30 12:16:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQmfi-0005x4-S9; Thu, 30 Aug 2007 12:15:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQmff-0005iz-Mv for lemonade-confirm+ok@megatron.ietf.org; Thu, 30 Aug 2007 12:15:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQmff-0005hd-4G; Thu, 30 Aug 2007 12:15:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQmfe-0005dT-Me; Thu, 30 Aug 2007 12:15:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 847FE2AC79; Thu, 30 Aug 2007 16:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IQmfe-000516-4k; Thu, 30 Aug 2007 12:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 30 Aug 2007 12:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-imap-notify-00.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : The IMAP NOTIFY Extension Author(s) : C. King, et al. Filename : draft-ietf-lemonade-imap-notify-00.txt Pages : 18 Date : 2007-8-30 This document defines an IMAP extension which allows a client to request specific kinds of unsolicited notifications, such as messages being added to or deleted from mailboxes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-notify-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-imap-notify-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-imap-notify-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-8-30113446.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-imap-notify-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-imap-notify-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-8-30113446.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Thu Aug 30 15:24:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQpb9-0003Kt-Mz; Thu, 30 Aug 2007 15:22:35 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IQpb7-00037Q-Jv for lemonade-confirm+ok@megatron.ietf.org; Thu, 30 Aug 2007 15:22:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQpb7-00036V-9q for lemonade@ietf.org; Thu, 30 Aug 2007 15:22:33 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQpb5-00055W-PG for lemonade@ietf.org; Thu, 30 Aug 2007 15:22:33 -0400 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l7UJMUle000370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 30 Aug 2007 12:22:30 -0700 Received: from [[172.16.2.186]] (vpn-10-50-16-86.qualcomm.com [10.50.16.86]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l7UJMQcG019618; Thu, 30 Aug 2007 12:22:28 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47E8@esebe199.NOE.Nokia.com> <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47FB@esebe199.NOE.Nokia.com> References: <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47E8@esebe199.NOE.Nokia.com> <4C38DC11F6B4FF4FAEA73E30DB5AA157FE47FB@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Thu, 30 Aug 2007 12:14:51 -0700 To: , From: Randall Gellens Subject: RE: [lemonade] IMAP-SIEVE: Per-Client Sieve Script Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: -4.0 (----) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: leiba@watson.ibm.com X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org At 11:27 AM +0300 8/30/07, wrote: > Questions/comments: > > What is the execution order of the scripts (last modification > date/alphabetical/etc)? I am asking this because one script might > move an email while another might notify it - which one happens > first... My suggested text included: > After all Sieve scripts have run, the implementation MAY then > expunge the original message This way, the message will remain in the folder while all scripts run, so multiple scripts may move it, resulting in the message effectively being copied. As for modifications, existing text in the document says modifications don't show up to the script, so in effect they likewise take effect after all scripts have run. > > What if there are two scripts and: both want to send a > notification, and to the same/different addresses? Which will be > sent? Both? Yes. Each scripts needs to operate independently. Separately, as an optimization, an implementation could coalesce multiple notifications to the same address into a single notification. > > The original text refers to these problems as: " complexity and > possible ambiguity involved with coordinating the results of > multiple scripts". > Should these problems be elaborated in more detail and - hopefully > - provide a standardized behavior? I have attempted to provide a standardized behavior. If you feel more detail is needed, or that there is still ambiguity, please point out where. At 11:32 AM +0300 8/30/07, wrote: > One more question if I may: > How do You identify (uniquely) which script belongs to which > client? I mean if we can't do this and clients keep overwriting > each others' scripts (because they don't know which one belongs to > them), we did not achieve anything, did we? My suggested text included: At 3:40 PM -0700 8/13/07, Randall Gellens wrote: > The entry name below ""/IMAPSieve/Script/client/" SHOULD be > named .. For example, "Eudora.FC2302". Hence, each client is assigned a through an IANA registry, perhaps an existing one, or a new one can be created. Each client is free to choose a of its own creation. I was thinking that any identifier for the device could be used, but even a random number with a reasonable range would suffice. There was never any intention of allowing clients to "keep overwriting each others' scripts (because they don't know which one belongs to them)" -- instead, the idea is to err on the side of possible extra scripts, perhaps because a client has forgotten its identifier. Those obsolete scripts would eventually be reaped by the server, as described in my suggested text. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- The number of licorice gumballs you get out of a gumball machine increases in direct proportion to how much you hate licorice. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Aug 31 14:21:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IRB5x-0004mU-Qz; Fri, 31 Aug 2007 14:19:49 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IRB5w-0004hl-3m for lemonade-confirm+ok@megatron.ietf.org; Fri, 31 Aug 2007 14:19:48 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IRB5v-0004g8-NB; Fri, 31 Aug 2007 14:19:47 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IRB5u-0007SE-JI; Fri, 31 Aug 2007 14:19:47 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm1646d865fd; Sat, 01 Sep 2007 02:31:15 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm7446d3b4b4; Tue, 28 Aug 2007 08:30:57 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 28 Aug 2007 08:30:57 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjeK-0006BY-KU; Mon, 27 Aug 2007 14:49:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjeG-00067v-Bg; Mon, 27 Aug 2007 14:49:16 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPjeF-0001Ti-PX; Mon, 27 Aug 2007 14:49:16 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id A126126E3D; Mon, 27 Aug 2007 18:49:15 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IPjeF-00062o-II; Mon, 27 Aug 2007 14:49:15 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 27 Aug 2007 14:49:15 -0400 X-Spam-Score: -1.4 (-) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: iesg-secretary@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Cc: lemonade mailing list , lemonade chair , Internet Architecture Board , RFC Editor Subject: [lemonade] Protocol Action: 'IMAP URL Scheme' to Proposed Standard X-BeenThere: lemonade@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The IESG has approved the following document: - 'IMAP URL Scheme ' as a Proposed Standard This document is the product of the Enhancements to Internet email to Support Diverse Service Environments Working Group. The IESG contact persons are Lisa Dusseault and Chris Newman. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-rfc2192bis-09.txt Technical Summary IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. This document obsoletes RFC 2192 and updates RFC 4467. Working Group Summary This document removed support for IMAP URLs for listing the contents of a mailbox. There was a clear consensus that this feature (originally described in RFC 2192) was never implemented. Some of the changes to the document were a result of the Lemonade interoperability event of October 2006 held in London, England. Protocol Quality The document received several positive reviews. In particular it is worth noting Ted Hardie and Zoltan Ordogh have done detailed reviews of the document. This document addresses all issues raised. Eric Burger shepherds this document on behalf of Lisa Dusseault, the responsible Area Director. Lisa and Eric reviewed this document and believe it is ready for forwarding to the IESG for publication. Note to RFC Editor In section 6.1.1.1, first paragraph, last sentence: OLD: The authorization token is generated from the URL, the authorized access identifer, authoriza- ^^^^^^^^^ tion mechanism name, and a mailbox access key. NEW: The authorization token is generated from the URL, the authorized access identifier, autho- ^^^^^^^^^^ rization mechanism name, and a mailbox access key. (typo in the word "identifier") In section 6.1.1.2, replace the first paragraph: OLD: The mailbox access key is a random string with at least 128 bits of entropy. It is generated by software (not by the human user), and MUST be unpredictable. NEW: The mailbox access key is an unpredictable, random string. To ensure unpredictability, the random string with at least 128 bits of entropy is generated by software or hardware (not by the human user). In section 9.1, 9th paragraph: OLD: The following edge case example demostrates that the ;UIDVALIDITY= ^^^^^^^^^^^ modifier is a part of the mailbox name as far as relative URI reso- lution is concerned: NEW: The following edge case example demonstrates that the ;UIDVALIDITY= ^^^^^^^^^^^^ modifier is a part of the mailbox name as far as relative URI reso- lution is concerned: typo: demonstrates In section 10.1, first paragraph, replace the last sentence: OLD: Use of either of these access identi- fiers makes it impossible for an attacker, spying on the session, to use the same URL, either directly or by submission to a message submission entity. NEW: Use of either of these mechanisms limits the scope of the URL. An attacker who cannot authenticate using the appropriate credentials cannot make use of the URL. In section 12.1, 13th paragraph: OLD: A widely deployed IMAP client Netscape Mail (and possibly Mozilla/ Thubderbird/Seamonkey) use a different imap: scheme inter- ^ ^ nally. NEW: A widely deployed IMAP client Netscape Mail (and possibly Mozilla/Thunderbird/Seamonkey) use a different imap: scheme inter- ^ ^ nally. (typo in Thunderbird, also remove an extra space) In Appendix D, third paragraph, add: OLD: Editors would like to thank Mark Crispin, Ken Murchison, Ted Hardie, Zoltan Ordogh, Dave Cridland, Kjetil Torgrim Homme, Lisa Dusseault, Spencer Dawkins, Filip Navara and Shawn M. Emery for the ^^^ time they devoted to reviewing of this document and/or for the com- ments received. NEW: Editors would like to thank Mark Crispin, Ken Murchison, Ted Hardie, Zoltan Ordogh, Dave Cridland, Kjetil Torgrim Homme, Lisa Dusseault, Spencer Dawkins, Filip Navara, Shawn M. Emery, Sam Hartman, ^ ^^^^^^^^^^^^^ Russ Housley and Lars Eggert for the time they devoted to ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ reviewing of this document and/or for the comments received. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade