dovecot - Feb 2013 - Best practice for sieve script synchronization

We consider deploying a two server active-active setup with
dsync replication for ~2500 users. 

I was wondering how people handle sieve script synchronization in such
setups. 

We came up with a few options for syncing:

 1) rsync/unison ~/sieve every x seconds  

 2) move sieve dirs to separatate partition and sync with
   gluster or drbd

 3) patch roundcube managesieve sieve plugin to upload to both
 managesieve servers (only roundcube can access managesieve in our
 setup)

 4) store sieve scripts in mysql and patch roundcube managesieve plugin
 to directly access the db instead of using managesieve (we tried this,
 but apparently sieve scripts read from db via dovecot dict can't have
 more than one line? show stopper due to roundcube sieve plugin  needing
   comments to parse the scripts)

 5) wait until Timo/Stephan add additional magic to dsync for sieve
 scripts as discussed in
 http://www.dovecot.org/list/dovecot/2011-October/061699.html ;-)

We are tending towards 1) as this seems  simplest and most robust
solution but before we re-invent the wheel we'd like to "hear"
your
thoughts...

Thanks
Oli

-- 
This message does not contain horse meat

Am 28.02.2013 09:58, schrieb Oli Schacher:
> I was wondering how people handle sieve script synchronization in such
> setups.
depending on your setup, use sieve with sql

http://hg.rename-it.nl/dovecot-2.1-pigeonhole/file/e9ed5d5cef4b/doc/script-location-dict.txt

but other solutions may work too, i.e with rsync ssh etc


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstra?e 15, 81669 M?nchen

Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich

* Oli Schacher <dovecot at lists.wgwh.ch>:
> We consider deploying a two server active-active setup with
> dsync replication for ~2500 users. 
When? Dovecot 2.2 will have a much improved dsync protocol, allowing for sieve
replication. IIRC the functionality isn't there yet, but I guess you can
either build your own logic or pay Timo to add it to dync.

p at rick
> -- 
> This message does not contain horse meat
THAT made my day. :D


-- 
[*] sys4 AG
 
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstra?e 15, 81669 M?nchen
 
Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich

On 2013-02-28 9:58, Oli Schacher wrote:
> I was wondering how people handle sieve script synchronization in such
> setups.
> 
> We came up with a few options for syncing:
> 
>  1) rsync/unison ~/sieve every x seconds
[...]
> We are tending towards 1) as this seems  simplest and most robust
> solution but before we re-invent the wheel we'd like to
"hear" your
> thoughts...
I am using unison for synchronizing sieve scripts for some years, now.
It does what it is supposed to do very well.

Regards,
Michael