search for: script_data

...n = priv/sieve/name/$script_name table = user_sieve_scripts username_field = username value_field = id fields { script_name = $script_name } } map { pattern = priv/sieve/data/$id table = user_sieve_scripts username_field = username value_field = script_data fields { id = $id } } But when I update the rules in mysql sieve continue to apply only the "old" rules stored in the binary. The only way to apply the new rules is to delete the .sieve-bin/activesql.svbin. If I remove ";bindir=~/.sieve-bin" works fine. T...

...xxx map { pattern = priv/sieve/name/$script_name table = user_sieve_scripts username_field = username value_field = id fields { script_name = $script_name } } map { pattern = priv/sieve/data/$id table = user_sieve_scripts username_field = username value_field = script_data fields { id = $id } } CREATE TABLE IF NOT EXISTS `user_sieve_scripts` ( `id` int(11) NOT NULL DEFAULT '0', `username` varchar(40) DEFAULT NULL, `script_name` varchar(255) DEFAULT NULL, `script_data` varchar(10240) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KE...

...user_sieve_scripts > username_field = username > value_field = id > fields { > script_name = $script_name > } > } > map { > pattern = priv/sieve/data/$id > table = user_sieve_scripts > username_field = username > value_field = script_data > fields { > id = $id > } > } > > But when I update the rules in mysql sieve continue to apply only the > "old" rules stored in the binary. The only way to apply the new rules > is to delete the .sieve-bin/activesql.svbin. If I remove > ";bi...