Randall Gellens wrote:
At 2:13 AM +0300 11/13/98, Alexey Melnikov wrote:
Other important issue. As Tim Showalter noticed setflags should be bind to
fileinto, because multiple fileinto are possible for the same message. Any
ideas? (Tim Showalter proposed to add additional parameter to fileinto, so I
mean "any other ideas" here)
I think the simplest thing to do is to have setflags and fileinto be
separate actions. A setflags which is not followed by a fileinto sets
flags for the message when it is filed into the default folder (inbox).
A setflags followed by a discard means the setflags was for naught, but
so what?
This is the current behaviour. The problem with multiple fileinto can be shown
in
the following example:
fileinto "INBOX/TodayMail";
setflag "\Deleted";
fileinto "INBOX/FromBoss";
setflag "\Answered";
The second setflag relates to the first or second fileinto?
Alexey, how would you feel about pursuing setflags as an extension
after the Sieve base spec is published? As useful as I think setflags
is, I think we need to focus on keeping Sieve simple and getting it out
the door.
I really want SIEVE to be published as standard as soon as possible.
I don't want setflag to be added to the base spec. Do you propose to abandon
setflag until SIEVE is published as RFC?
--
Regards,
Alexey Melnikov
------------------------------------------
SMTP/POP3/IMAP4/ACAP servers creation team
Epsylon Technologies, Russia
http://www.taxxi.com
Imap Development Kit (my own product)
http://194.87.43.111/homerus/mail/idk/index.htm
Fax (in San Diego, California): 1 (619) 8393837
------------------------------------------