[ingo] Current status on multiple backends for sieve?

[D G Teed]

Thanks for that code on backends.php .  Looks like it could work.
It probably does, but I'm having a problem authenticating
to a server which I thought I had working before.
I can connect to it with sieveshell on the remote cyrus server,
but saving a forward there shows the error in the browser:

 There was an error activating the script. The driver said: Failed to
connect, server said: "Authenticate first"

I've increased the logging in horde and I can't see any more detail.
I don't see anything in the apache error log relating to this failure.

On imapd.log on the remote box, there is no indication of a problem.
I see sometimes an entry related to timseived, but no errors.

Jun  4 17:15:23 campus timsieved[80628]: login: campus.mydomain[x.x.x.x]
donaldtest LOGIN User logged in
Jun  4 17:17:42 campus master[80666]: about to exec
/usr/local/cyrus/bin/timsieved
Jun  4 17:17:42 campus service-sieve[80666]: executed

Are there any suggestions on how I can debug ingo further?

--Donald

On 5/30/07, Rafael Varela Pet <srrafa at usc.es> wrote:
>
> Hi,
> El mié, 30-05-2007 a las 09:29 -0300, D G Teed escribió:
>
> > On the FAQ I read the suggestion to set up multiple ingo instances
> > to support more than one backend to ingo.  In my case I have
> > 3 cyrus servers one can login to from imp, and I'd like the
> > filter option to work with the corresponding cyrus imap server
> > running its own timsieved.
>
>
> Our solution was putting some PHP logic in backends.php. Basically, we
> populate the backends array comparing the name of the IMAP server where
> the user logs with the preferred field of the available backends.
>
>
> Our configuration looks like this:
>
>
>
> $availableBackends['foo'] = array(
>     'driver' => 'null',
>     'preferred' => 'foo.company.com',
>     'hordeauth' => true,
>     'params' => array(),
>     'script' => 'imap',
>     'scriptparams' => array()
> );
>
>
>
>
> $availableBackends['bar'] = array(
>     'driver' => 'timsieved',
>     'preferred' => 'bar.company.com',
>     'hordeauth' => true,
>     'params' => array(...)
> );
>
>
>
>
>
>
> $backends['default'] = $availableBackends['foo'];
>
> $currentServer = $GLOBALS['registry']->call('mail/server');
>
>
> /*
>   Selects a backend using 'preferred' field
> */
>
> foreach ($availableBackends as $temp) {
>     if (!empty($temp['preferred'])) {
>         if (is_array($temp['preferred'])) {
>             foreach ($temp['preferred'] as $val) {
>                 if ($val == $currentServer) {
>                     $backends['default'] = $temp;
>                 }
>             }
>          }
>          elseif ($temp['preferred'] == $currentServer) {
>             $backends['default'] =  $temp;
>         }
>     }
> }
>
>
>
> > In 2005 there was a patch suggested against an earlier
> > Ingo.php to support this, but someone replied this was
> > not the right approach to reference session variables inside Ingo.php
> >
> > The old horde we have in production currently runs
> > multiple ingos as the workaround.  I'd like to implement
> > something easier to access than that.
> >
> > If multiple backends isn't possible, then can anyone suggest
> > an easy way to add the multiple ingo instances to the imp
> > menu so people can pick the correct filter for their server?
> > I thought I saw an Administration item for editing the horde
> > menu with additional links, but I don't see it now.
>
>
> Regards,
>
> --
> Rafael Varela Pet
> Area de Tecnoloxías da Información e Comunicacións
>
> Universidade de Santiago de Compostela
> 15782 Santiago de Compostela
> http://www.usc.es/atic
>
> --
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>