Ken Murchison wrote:
Barry
Leiba wrote:
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?
Disclaimer: I haven't made my mind yet on whether running Sieve scripts
on IMAP events is a proper thing.
I
think we need to either extend MANAGESIEVE or use mailbox annotations
(Cyrus currently does the latter for running a script when a message is
delivered to a shared mailbox)
Both seems like reasonable approaches. However I have slight bias
towards extending ManageSieve to allow for multiple Sieve triggers, as
this seems to provides better abstraction layer. Mailstores that
implement generic mailbox annotations can still use mailbox annotations
to store Sieve scripts.
|