sieveusehomedir true - IOERROR: not a sieve bytecode file

[Andrew Morgan]

On Mon, 24 Oct 2005, Ken Murchison wrote:

> Andrew Morgan wrote:
>> 
>> On Mon, 24 Oct 2005, Ken Murchison wrote:
>> 
>>> Andrew Morgan wrote:
>>>> 
>>>> On Mon, 24 Oct 2005, Ken Murchison wrote:
>>>> 
>>>>> Yes.  lmtpd in Cyrus 2.2+ only reads bytecode scripts.
>>>> 
>>>> Hmmm.  This means changing how I handle mail filtering for my users.  How 
>>>> do other large installations handle this?  I currently generate .sieve 
>>>> files for my users' most common needs, and this is integrated into our 
>>>> larger self-service account tools.  I guess I'll most likely move to 
>>>> timsieved, but I'm open to suggestions now.
>>> 
>>> Just change your tool to run 'sievec' on the text script to compile it to 
>>> bytecode.
>> 
>> Yeah, that is looking like the least-pain solution.  It will be weird for 
>> people that edit those files by hand, but I guess they'll get over it. How 
>> does CMU handle sieve scripts?
>
> timsieved.  All of CMUs Cyrus servers are sealed (no user accounts). Editing 
> is done via a web interface on a portal.

Is this a custom written web interface for sieve updates, or something 
generally available?

 	Andy