search for: sieve_id

Displaying 2 results from an estimated 2 matches for "sieve_id".

Did you mean: sieve_dir
2015 Aug 17
2
Segfaults after upgrade to Debian Jessie
...st (trying default script location instead)" I have a dict:proxy configured (/etc/dovecot/pigeonhole-sieve.dict): connect = host=127.0.0.1 dbname=postfix user=postfix password=xxx map { pattern = priv/sieve/name/$script_name table = virtual_users username_field = email value_field = sieve_id fields { sieve_active = $script_name } } And that added to dovecot.conf: dict { sieve = mysql:/etc/dovecot/pigeonhole-sieve.dict } And that in 90-sieve.conf: plugin { sieve = dict:proxy::sieve;name=active } I guess I'm doing something stupid. Any ideas? Thanks, Andy
2015 Aug 17
2
Segfaults after upgrade to Debian Jessie
On Mon, 2015-08-17 at 14:13 +0200, Stephan Bosch wrote: > but until then you can avoid this by using the the exdata hg revision before tip > (57c8d3e6b562). Great, thanks for the quick reply, that fixed the compilation problem. I'm still getting a segfault though. This time the backtrace is: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was