Horst Fickenscher wrote:
Hello,
after our upgrade to 2.1.7 we have been playing with Sieve scripts in
the last week and ran into some unexpected scenarios.
Maybe anyone can help us out?
require ["fileinto"];
if header :contains "To" "[EMAIL PROTECTED]" {
fileinto "Test";
stop;
}
We expected mail to "[EMAIL PROTECTED]" to be moved to the folder "Test".
Indeed, messages were filed into "Test" but still kept in the Inbox. If
we didn't get RFC3028 wrong, we thought the fileinto command would
revoke the "implicit keep".
What are your thoughts about this? Is there anything wrong with our
Sieve script?
Since 2.1.7 was released which requires the newer version of libsieve
(2.1.12), there were complaints about sieve functionality on the lists.
Check the archives.
I use sieve for filtering, vacation and mail redirection (with a nice
web interface for users, which generates the sieve scripts). So I
haven't yet upgraded.
I have svn version 2192 or smth like that running on my test server. (to
quote Paul: "2.1.7 *is* 2211") That means my test environment is still
using libsieve 2.1.10.
Sent a mail to the test user, using the script below and worked as
expected -- delivered only to the folder 'test', 'Inbox' stayed empty.
test:~/testforhorst # dbmail-sievecmd -u test -l
*** dbmail-sievecmd ***
Opening connection to database...
Opening connection to authentication...
Ok. Connected!
Found 1 scripts:
+ kred_script
test:~/testforhorst # dbmail-sievecmd -u test -c kred_script
*** dbmail-sievecmd ***
Opening connection to database...
Opening connection to authentication...
Ok. Connected!
require ["fileinto"];
if header :contains "To" "[EMAIL PROTECTED]" {
fileinto "test";
stop;
}
test:~/testforhorst #
So I'd say it's the new libsieve or dbmail at fault. I'd wait for Aaron
to return from vacation or try an older version.
HTH,
Alex
