[ingo] Problem with Ingo and timsieved

[Jose-Marcio Martins da Cruz]

Hello,

I'm not able to configure sieve filters with Ingo.

I'm using the last stable release of all Horde suite (horde,
imp, ingo, turba, ...), and the last stable release of Cyrus suite
(imapd and sasl).

Horde and Cyrus IMAP are running in the same server. Ther's no
problem to configure sieve scripts using CLI sieveshell, so
it seems that isn't a cyrus problem.

At ingo/conf/backends.php, the only backend configured is sieve
(timsieved).

The only storage driver available at Ingo Administration/Setup interface
is "prefs".

When I define a new filter it seems that it is really saved at
user_prefs (verified with "strings horde_prefs*" command), and not at
/usr/sieve/ directory.

How can I configure Ingo to really use timsieved to save sieve scripts ?

Thanks

Jose-Marcio