Re: autocreate.sieve doesn't work correct. temporary files

Hi Artyom, Yeah wow, this is really gross. I'm pretty sure the gibberish in those "??Default.script.bc" filenames is just whatever junk was in the (uninitialised) sieve_script_dir variable. I've had a rummage around, and there's a user_sieve_path() function in imap/user.c that does the

Re: autocreate.sieve doesn't work correct. temporary files

Where are the default sieve rules at? If I go into round cube there is a sieve group called round cube. Where is that at? - Paul > On Oct 5, 2015, at 8:51 PM, ellie timoney wrote: > > Hi Artyom, > > Yeah wow, this is really gross. > > I'm pretty sure the gibberish in

Re: thread=refs

Great, Ken. Can you give me some advice / pointer to the sources I should look at? Gabriele Da: Ken Murchison A: info-cyrus@lists.andrew.cmu.edu Data: 2 ottobre 2015 19.08.04 CEST Oggetto: Re: thread=refs On 10/02/2015 10:53 AM, Gabriele Bulfon wrote: Nice, it's not a big deal for us to

Re: thread=refs

As far as I can tell, the last specification for thread=refs was here:https://tools.ietf.org/html/draft-ietf-morg-inthread-01 To implement this you want to look at index.c in the Cyrus source and add another entry to the thread_algs[] array. I'm guessing that you can reuse a lot of the

Re: autocreate.sieve doesn't work correct. temporary files

Guys I don't understand hot it can work. I added additional logging and found that sieve_script_dir is not defined. After adding this definition the problem gone. 147 /* Check if autocreate_sieve_compiledscript is defined in imapd.conf */ 148 if(!(compiled_source_script =