Re: Sieve bytecode vs plaintext configuration files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks! I'll look into this sievec utility.  I've found it in
/usr/lib/cryus-imapd/sievec

I guess I would use it like "sievec ~/.sieve ~/.sievebc"

It appears to generate the bytecode output correctly.  Is there any
way of testing the resulting file, apart from sending test emails to
the account?

On 2/15/07, Thomas Robers <robers@xxxxxxxxx> wrote:
emdeex schrieb:
[...]
>
> Is it that I can't just write plaintext .sieve files, that they have
> to be bytecode?  If so, how can I do this without sieveshell?

I don't really know, if plain text sieve files can still be used or not, but to
make bytecode out of the plain text sieve files you can use the program
sievec:

root@imap:~ # sievec
Syntax: sievec [-C <altconfig>] <filename> <outputfile>

HTH Thomas

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux