dovecot - Sep 2008 - Dovecot ManageSieve + ingo or avelsieve

Hi,

does anyone got Dovecot ManageSieve and Horde/Ingo working together ?

i'm running Dovecot 1.1.2 with managesieve patch
(dovecot-1.1.2-managesieve-0.10.3.diff)

following intructions at http://wiki.dovecot.org/ManageSieve now my
Dovecot have ManageSieve available :-)

I've setup Horde/Ingo (ingo-h3-1.1.5-1.el5)

when I specify some new filtering rules in Ingo, they are successfully
uploaded using managesieve to Dovecot server and seems to be working.
But when I logout/login back to Ingo, no rules are visible. Previously
defined rules are still working with dovecot (because the ingo.sieve
which links to .dovecot.sieve contains them), but Ingo is ignoring them
at all.

also my Dovecot managesieve setup is working well with avelsieve-1.9.4
plugin for Squirrelmail, but not with latest avelsieve-1.9.7 (see
http://article.gmane.org/gmane.mail.squirrelmail.plugins/13818 ) :
in avelsieve-1.9.7 same as Ingo, it forget rules !

any suggestion ?

Ingo backends.php is :
----

$backends['sieve'] = array(
    'driver' => 'timsieved',
    'preferred' => 'localhost',
    'hordeauth' => true,
    'params' => array(
        // Hostname of the timsieved server
        'hostspec' => 'localhost',
        // Login type of the server
        'logintype' => 'PLAIN',
        // Enable/disable TLS encryption
        'usetls' => false,
        // Port number of the timsieved server
        'port' => 2000,
        // Name of the sieve script
        'scriptname' => 'ingo',
    ),
    'script' => 'sieve',
    'scriptparams' => array()
);

----



PS : any ManageSieve patch for Dovecot v1.1.3 ?

thanks

-- 
Olivier

on 9/3/08 5:06 PM , Olivier Dijoux wrote  :
> does anyone got Dovecot ManageSieve and Horde/Ingo working together ?
> (...)
well, I found the trick :
Ingo stores its own copy of sieve rules into the Horde preference 
backend system,
seems it doesn't read/parse rules from ManageSieve server, but can only 
push them.
so after setup the Horde backend correctly to MySQL, everything works fine;
i can edit sieve rules, they are stored into horde/ingo SQL prefs 
backend, and then uploaded via ManageSieve into Dovecot server

however i would consider avelsieve, as it can parse (GETSCRIPT) and push 
(PUTSCRIPT) sieve rules via ManageSieve, that's propably better if I 
offer ManageSieve tcp/2000 service to my users so they can you their own 
managesieve clients...


anyway, does ManageSieve patch for Dovecot v1.1.3 exists yet ?

-- 
Olivier