On Wed, 2005-09-21 at 16:05 +0100, Alexey Melnikov wrote:
Philip Guenther wrote:
Note that it is not possible to use this extension to set or clear the
\Recent flag or any other special system flag which is not settable
in [IMAP]. If the \Recent flag is included in a flag list, it MUST be
silently ignored, but a warning message SHOULD be logged by the Sieve
interpreter.
[...]
However, the suggestion that the implementation should log these events
is kinda weird. In my experience, admins have *no* interest in being
bothered by this stuff.
As Rob pointed out, the draft doesn't actually say what kind of logging
should be done.
Some kind of user specific logging would be useful, so that people can
answer a question like "why such and such flag is not being set".
Should I change the "SHOULD" to "should"?
Should the draft explain this in more details?
as long as there is no facility for accessing such logs in Sieve, I
think the spec shouldn't be mentioning any. what gets logged or not is
an administrative issue.
I'd drop the text after the comma, and also remove the "silently", since
it may be taken to mean that no logging is allowed. what happens to
special system flags other than \Recent? shouldn't the behaviour be the
same? suggested replacement text (only the last sentence is different):
Note that it is not possible to use this extension to set or
clear the \Recent flag or any other special system flag which is
not settable in [IMAP]. Any such flags MUST be ignored if
included in a flag list.
--
Kjetil T.