|
|
Re: imap4flags and sieve filter: msg#00084
mail.ims.general
|
Subject: |
Re: imap4flags and sieve filter |
Rahul Shah wrote:
> Just to add on this. There was bug while setting the flags due to
which
> the system flags were not getting set properly(bug 6548718). This bug
> was fixed in 6.3-1.02 and was not backported.
>
> -Rahul
Thanks Rahul, that must be what I'm experiencing since I tried Ned's
suggestion of using the "\\" for the flag name, but still no joy.
While we're on this topic of bugs, is this another one?
The Sieve IMAP flag Extension draft states:
"Note that the parameter specifying a variable name to setflag/
addflag/removeflag actions and the hasflag test is optional. If the
parameter is not specified the actions operate on the internal
variable, which has the empty value when the script starts
execution.
If the SIEVE interpreter doesn't support the "variables" extension
[VARIABLES], the presence of the variable name parameter will cause
a runtime error [SIEVE]."
And yet when I try this syntax
if allof(header :contains "X-SpamLabel" ["SPAM", "VIRUS"],
header :contains "X-MailRoute" "InboundMail") {
setflag "\\Seen";
fileinto "SPAM";
}
I get this error message:
# imsimta test -expression -mm -block -message=/tmp/spam -input=/tmp/
rule.siv
Expression: require ["fileinto","imap4flags"];
Expression: Expression:
Expression: Expression: if allof(header :contains "X-
SpamLabel" ["SPAM", "VIRUS"],
Expression: Expression: header :matches "X-MailRoute"
"InboundMail") {
Expression: Expression: setflag "\\Seen";
Expression: Expression: fileinto "SPAM";
Expression: Expression: }
Expression: Parse error: Insufficient arguments in call to function:
setflag [etflag "\\Seen" ; f^ileinto "Auto-Expire]
It seems like its expecting another argument to the "setflag"
command. A variable name perhaps? Isn't this optional?
w
Yes, this is a bug in 6.2. It was fixed in 6.3 but again was not backported.
Ned
|
|