I gather from previous posts on this list that with Cyrus 2.2 even sieve scripts in home directories must be compiled, and sievec is the tool to do so.
I have a couple questions, and a comment. First, is sievec documented anywhere? In Debian's cyrus-doc-2.2, sievec does not appear on the list of man pages. Second, is there any point in sieveusehomedir given this requirement? I was allowing scripts in home dirs because it was easy to make changes in the scripts (though admittedly easy to make syntax errors too). But if one has to run a program on the resulting script, it seems as easy to run a program that sticks it on the IMAP server. Also, if sievec overwrites .sieve with compiled code, this sounds like an operation that could only be done once. My comment is that the documentation could be more forthcoming about these issues; as far as I can tell, it says nothing at all about how sieveusehomedir interacts with the compilation mechanism. My assumption had been that only the code on the server is compiled and that home directory .sieve scripts were simply compiled on the fly each time they were encountered. I gather that interpretation is wrong. Ross Boylan ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
