[horde] Cannot edit filter rules (ingo with timsieved)

[Andy Dorman]

On 10/01/2013 11:31 AM, sascha at schmidt.ps wrote:
>
>> Am 01.10.2013 um 14:50 schrieb Andy Dorman <adorman at ironicdesign.com>:
>>
>>> On 10/01/2013 03:35 AM, Sascha Schmidt wrote:
>>>   Zitat von Sascha Schmidt <sascha at schmidt.ps>:
>>>
>>>> Zitat von Jan Schneider <jan at horde.org>:
>>>>
>>>>> Zitat von Sascha Schmidt <sascha at schmidt.ps>:
>>>>>
>>>>>> Zitat von Sascha Schmidt <sascha at schmidt.ps>:
>>>>>>
>>>>>>> I've activated sieve as my filter backend. Everything works fine for
>>> my
>>>>>>> user. Activating the "shares" option and giving the rights for a
>>>>
>>>> special
>>>>>>> user to show, read, edit and delete rules does not really work...
>>>>>>>
>>>>>>> If I try to edit the rules for another user (I can choose the ruleset
>>>>
>>>> of
>>>>>>> this user) ingo tells me that I'm not allowed to edit the rules of
>>> this
>>>>>>> user... Checking the permissions again I can see a hook at every
>>>>>>> permission.
>>>>>>>
>>>>>>> Any hints whats going wrong here? How does ingo auth against the sieve
>>>>>>> daemon to change the ruleset of another user?
>>>>>>
>>>>>> Additionally I cannot change/edit/vuew the rules of the other user.
>>>>
>>>> Every
>>>>>> time I click on a rule the ruleset is changed to my user. So it's
>>>>>> actually
>>>>>> impossible to handle shared rules.
>>>>>>
>>>>>> Is there something I can do to fix or analyse this problem?
>>>>>
>>>>> Reporting a bug.
>>>>
>>>> Reported: http://bugs.horde.org/ticket/12694
>>>
>>>   Today I realised that I cannot add my own CUSTOM rules. They are denied
>>> with the same reason "permission denied". Adding emails to the
>>> positve/negative list works. I can display the sieve script within the
>>> filter settings and it's correctly added and activated.
>>>
>>> Someone who can verify this problem?
>>>
>>>   Thanks
>>> Sascha
>>
>> We are NOT having any problems with our own sieve scripts with Horde
>> 5.1.4 & Ingo 3.1.2 after we set up our ingo/backends.local.php.
>>
>> We have not tried using shares and do not have any plans to.  Ours is a
>> public service and enabling shares is just too dangerous.  So I doubt if
>> our backends.local.php would apply to your case.
>
> Could you provide your backends config? Perhaps I can find a hint to my problem there.
>
> Greets
> Sascha
>

Sascha, our backends.local.php looks something like below.

If you are running horde on the same server with Cyrus and your 
mailboxes, the $hostname below would be 'localhost'.  And you will need 
to make sure the logintype is correct for your sieve server.

/* Our Cyrus Sieve backend */
$backends['sieve']['disabled'] = false;
$backends['sieve']['preferred'] = '';

$backends['sieve']['script'][Ingo::RULE_ALL]['driver'] = 'sieve';
$backends['sieve']['script'][Ingo::RULE_ALL]['params']['utf8'] = false;

$backends['sieve']['transport'][Ingo::RULE_ALL]['driver'] = 'timsieved';
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['hostspec'] = 
$hostname;
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['logintype'] = 
'PLAIN';
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['usetls'] = true;
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['port'] = 4190;
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['scriptname'] 
= 'ingo';
$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['debug'] = false;

Hope this helps,

-- 
Andy Dorman