[ingo] Ingo Fails In Script.php @ 116:createAll

[Michael M Slusarz]

Quoting Adam Tauno Williams <awilliam at whitemice.org>:

> On Tue, 2014-04-15 at 08:30 -0400, Adam Tauno Williams wrote:
>> I am attempting to update a Horde instance that uses Ingo with a SIEVE
>> backend.  The filters application runs - but there are no filters
>> displayed and no "New Rule" button.
>
> Ah, my bad [sort of], the configuration of the SIEVE backend has
> changed.  Now backends.local.php contains:
>
> $backends['imap']['disabled'] = true;
> $backends['sieve']['disabled'] = false;
> $backends['sieve']['script'][Ingo::RULE_ALL]['params']['utf8'] = true;
> $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['hostspec'] =
> ***;
> $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['logintype'] =
> 'PLAIN';
> $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['usetls'] =
> ***;
> $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['port'] =
> 2000;
> $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['scriptname']
> = 'ingo';
> $backends['sieve']['shares'] = false;
>
>  - and it works.  I was looking for docs in horde/ingo, but the docs are
> in the pear module [pear/docs/ingo/UPGRADING], they mention the config
> change.
>
>     The 'script' and 'transport' settings of the backend configuration
>     have been changed from strings to arrays, to allow different
>     backends for different filter rules.
>
> Which is helpful, but not overly illustrative.

If you could suggest additional/better language for the documentation  
that would have been more helpful, that would be great to add.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]