ietf-mta-filters
[Top] [All Lists]

Re: The last remaining issue in the Sieve variables draft

2005-04-25 03:28:28

Kjetil Torgrim Homme wrote:

On Sun, 2005-04-24 at 19:07 +0100, Alexey Melnikov wrote:
 Namespaces are meant for future extensions which make internal state
 available through variables.  These variables SHOULD be put in a
 namespace with the same name as its capability string.  Notice that
 the user can not specify a namespace when setting variables with SET.
Which reminded me: can we change the last sentence to:

Unless explicitly allowed by a Sieve extension, the user can not specify a namespace when setting variables with SET.

Once again, I don't like to be too restrictive for no good reason.

I'd prefer other extension to add their own action if they need it.  the
way I figure is that most uses of namespaces will be read-only, or with
specialised needs for setting values.  you don't really want

  SET "mimestructure.body.2.1" "Hi there";

do you?

I was thinking more about something like

  SET "annotate.body.2.1" "\\Seen";

(where "annotate" is an extension to set IMAP annotations).