> Currently, the Sieve language lacks the means of freely accessing the
> IMAP special-use mailbox attributes (RFC 6154). For example, it would be
> nice to be able to determine what the Junk mailbox is during Sieve
> processing at delivery, based on which mailbox has the "\Junk"
> special-use attribute assigned. I believe I have coined this idea before
> several years ago, but the incentive to actually build or document
> anything was never very high.
> Recently, I found the motivation to design a proper Sieve extension for
> this; I finished implementing IMAPSIEVE and in that context such
> functionality can also be very useful. The draft specification is
> attached, since the IETF draft submission is currently blocked.
> Please tell me what you think. I aim to submit this to appsawg soon, but
> I think most Sieve people are still concentrated here, so I post it here
> first.
This looks like a useful addition to sieve to me. I support its adoption as a
draft.
One thing you'll need to address is the ability for the same special use
attribute to be attached to multiple mailboxes. Since the ability to have the
same special-use attribute on multiple mailboxes is implementation-specific, my
suggestion would be to make the behavior in this case implementation-specific
as well.
Ned
_______________________________________________
sieve mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sieve
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.