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

[Barry Leiba <leiba at watson.ibm.com>]

Greg says...
> 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.

StÃphane says...
> I am working on the mapping and examples. Give me a few days to see
> if it works. I will try to allign with this new draft and extend to
> NF.

StÃphane has basically answered Greg's question, that it falls into
NF.  But it could also fall into DF, as Greg suggests.  I don't see,
right now, where lemonade would need DF filtering at the IMAP
APPEND/COPY level, but this will enable that if it be needed.

Background: This actually came up on Paris, not Vancouver, only I
didn't get the time to write the draft by Vancouver time.  In Paris,
StÃphane was talking about s-to-c notifications, and I suggested that
Sieve be used, since it's got a notification framework in the works.
StÃphane agreed that it might be usable if we extended things so that
Sieve scripts were called at times other than mail delivery, and I
volunteered to write a draft to get us going on it.

> 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.  

Right, it doesn't.  It puts in a placeholder for some of it, with the
SIEVEFILTER maybe-command, but I'm not, in general, happy with how
Sieve scripts can (more properly, can't) be managed.  The managesieve
protocol is too limited.  It assumes that there's one active Sieve
script per user, and that there either is or isn't an active script.
That's fine when Sieve scripts are only called for mail delivery, but
not if we start calling scripts at other times: Now we find we need to
consider different scripts for different causes, and perhaps (for
efficiency or management purposes) specify which mailboxes trigger the
script(s) and which don't.  Maybe there are other issues too.

I'm not sure we'll get consensus on an extensive script-management
interface in IMAP -- it's quite an overload for IMAP.  That's why I
left the "SIEVEFILTER" command unspecified, and just there as something
to open discussion on the issue.  Managesieve can certainly be
extended, and perhaps this draft should add another section, replacing
the SIEVEFILTER stuff, that extends managesieve to handle causes and
multiple active scripts, at least.

Do others have comments there?

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