[ingo] Solved: Strange Sieve Problem

Jan Schneider jan at horde.org
Thu Aug 3 00:49:29 PDT 2006

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> 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? :)

I already replied in the bug ticket:

This is wrong. You have setup Ingo to use hordeauth, otherwise you won't
even get to that part of the code. And if you have set hordeauth you want
to authenticate as the current user, not as the cyrus user.


Do you need professional PHP or Horde consulting?

More information about the ingo mailing list