[Extra] Comments on draft-ietf-extra-sieve-special-use-03

[Alexey Melnikov <[e-mail]>]

Hi all,
I've just tried to implement this Sieve extension and I have a couple of
comments:

3.  Test "specialuse_exists"

   Usage:  specialuse_exists [<mailbox: string>]
                             <special-use-flags: string-list>

This defines an optional argument. According to the base Sieve RFC 5228,
optional arguments must be tagged:

  2.6.1.  Positional Arguments

   Positional arguments are given to a command that discerns their
   meaning based on their order.  When a command takes positional
   arguments, all positional arguments must be supplied and must be in
   the order prescribed.

 and

  2.6.3.  Optional Arguments

   Optional arguments are exactly like tagged arguments except that they
   may be left out, in which case a default value is implied.  Because
   optional arguments tend to result in shorter scripts, they have been
   used far more than tagged arguments.

So I don't think you can have "mailbox" being positional without a tag!

4.  ":specialuse" Argument to "fileinto" Command

   Usage:  fileinto [:specialuse <special-use-flag: string>]
                    <mailbox: string>

Can I suggest that all special-use-flag strings should not include the
leading "\" character? It requires escaping in Sieve, so people might
make mistakes when writing scripts.

Best Regards,
Alexey