[ingo] Solved: Strange Sieve Problem

Chuck Hagenbuch chuck at horde.org
Wed Aug 2 19:51:49 PDT 2006


Quoting Darron Froese <darron at nonfiction.ca>:

> Found it, this is what finally fixed the problem:
>
> In lib/Ingo.php in the activateScript and getScript functions - we   
> ended up changing this:
>
> if (!empty($_SESSION['ingo']['backend']['hordeauth'])) {
>             $username = ($_SESSION['ingo']['backend']['hordeauth']   
> === 'full')
>                         ? Auth::getAuth() : Auth::getBareAuth();
>             // $password = Auth::getCredential('password');
>             $password = $_SESSION['ingo']['backend']['params']['password'];
>
> What was happening was that Ingo was supplying the:
>
> 1. Cyrus admin user's username
> 2. Effective user's password
>
> That was the problem - once we got it to use the right Cyrus admin   
> user's password - it works like a charm.
>
> Is this a bug - or are we using things incorrectly?

Certainly sounds wonky. Can you create a ticket on bugs.horde.org so  
that it doesn't get lost, unless of course someone who knows the Sieve  
backend better than I do responds in the mean time? :)

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris


More information about the ingo mailing list