RE: [lemonade] draft-ietf-lemonade-imap-sieve-00

["Vaudreuil, Greg M (Greg)" <gregv at lucent.com>]

I don't understand the big picture here.

In earlier discussions, we determined there were four cases where filtering occures:
	AF: Administrative filtering upstream of user processing
	DF: Traditional deposit time filtering
	NF: Filtering of notification events (maybe including notification actions resulting from deposit events?)
	VF: View filters of messages in a mailbox.

This draft appears to me to address DF filters where "deposit" comes from the IMAP client.  Is that a correct reading?  My alternate guess is that this specifies a means of performing a view filter by automatically (re)foldering messages into an alternate mailbox, in which case you want to capture all trigger events to apply the view filter to.

Can you map this document to the above filtering model or suggest changes to the model?

This draft also does not discuss the management of the scripts.  Are you assuming MANAGE SIEVE?  I would prefer to see a fuller script management interface included in IMAP that subsumes basic management capabilities of the SIEVEFILTER command.  

Greg V.


-----Original Message-----
From: lemonade-bounces at ietf.org [mailto:lemonade-bounces at ietf.org]On
Behalf Of Barry Leiba
Sent: Monday, December 19, 2005 12:14 AM
To: lemonade at ietf.org
Subject: [lemonade] draft-ietf-lemonade-imap-sieve-00


I have just sent the attached draft to be published as an I-D.  It's a
first pass at describing an extension to IMAP and Sieve that could be
used to drive server-to-client notifications with a Sieve script.

Please review and comment here, and especially note the "open issues"
section.

Barry

--
Barry Leiba, Pervasive Computing Technology  (leiba at watson.ibm.com)
http://www.research.ibm.com/people/l/leiba
http://www.research.ibm.com/spam

_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade