[ingo] ingo is modifying wrong .sieve file

[Thomas Preissler]

Mariusz,

sorry... I fixed it now:

$backends['sieve'] = array(
         'driver' => 'timsieved',
         'preferred' => 'localhost',
         'hordeauth' => full,
         'params' => array(
                 'hostspec' => 'localhost',
                 'logintype' => 'PLAIN',
                 'usetls' => false,
                 'port' => 2000,
                 'scriptname' => 'ingo'
         ),
         'script' => 'sieve',
         'scriptparams' => array(),
         'shares' => false
);

And some tweakage was required for managesieve - but in the end  
everything is nicely documented on Dovecot and nicely linked. No  
problem.

It is working now, ie. both users have their own .dovecot.sieve filter  
file. Awesome


Thanks again.



Quoting Thomas Preissler <thomas at preissler.co.uk>:

> Mariusz,
>
> I think you found it... awesome. In my file backends.php is the following:
>
> $backends['dovecot'] = array(
>     'driver' => 'vfs',
>     'hordeauth' => true,
>     'params' => array(
>         'filename' => '.dovecot.sieve',
>         'vfsroot' => '/dir1/dir2',
>         'vfs_path' => '/domain/user/Maildir',
>         'vfstype' => 'file'
>     ),
>     'script' => 'sieve',
>     'scriptparams' => array(),
> );
>
> Basically the directory in there is exactly pointing to the  
> .dovecot.sieve what has been modified for both users.
>
> I would be using different directories for the domain for each user,  
> but how can I do that? Can I somehow refer to the userdb_sieve  
> variable from my Dovecot configuration?
>
>
> Many thanks again
>
> Thomas
>
>
>
>
> Quoting Mariusz Czyz <mczyz at artic.edu>:
>
>> Thomas,
>>
>> Another place I'd verify is the ../ingo/config/backends.php file.
>> Specifically, this note in the file may shed some more light on your issue:
>> "        // The following settings can be used to specify an administration
>>        // user to update all users' scripts. If you want to use an admin
>>        // user, you also need to disable 'hordeauth' above. You have to use
>>        // an admin user if you want to use shared rules."
>>
>> Is it possible that your system us set up to use shared rules?
>>
>> Mariusz
>>
>>
>> On 01/15/2010 04:42 PM, Thomas Preissler wrote:
>>> Mariusz,
>>>
>>> thanks for that. I just checked and it is set to "Let a Horde
>>> application handle authentication", and that is "Imp".
>>>
>>> So I checked the Imap config, and dont see anything obvious. I
>>> configured the whole thing intially to authenticate against my IMAP
>>> server, Dovecot.
>>>
>>>
>>> Quoting Mariusz Czyz <mczyz at artic.edu>:
>>>
>>>> Thomas,
>>>>
>>>> My wild guess is that Horde is setup to authenticate as a certain user,
>>>> which could be you in this case.
>>>>
>>>> You can verify this by logging in with an administrative privileges and
>>>> going to: Administration -> Setup -> Horde -> Authentication(tab), once
>>>> there check what the $conf[auth][driver] is set to.
>>>>
>>>> Good luck,
>>>> Mariusz
>>>>
>>>>
>>>> On 01/12/2010 05:51 PM, Thomas Preissler wrote:
>>>>> Hello,
>>>>>
>>>>> I have the following setup: The Horde authentication is done by IMAP,
>>>>> ie. Dovecot, which works fine. I recently had to setup a vacation
>>>>> message for an IMAP user who is not using Horde. Ok, no problem, it is
>>>>> IMAP authentication, so that shouldnt be a problem.
>>>>> So I logged in as that user to setup a vacation message. I got various
>>>>> confirmations that it was alright, so I tested it. Long story short, I
>>>>> found out, that the configuration for Sieve is written to _my own_
>>>>> IMAP user (this was the first user who was used on Horde).
>>>>>
>>>>> I set the sieve file in Dovecot by passing a
>>>>> userdb_sieve=[PATH]/Maildir/.dovecot.sieve
>>>>> in the userlist.
>>>>>
>>>>> I enabled all sorts of debugging in Dovecot and can confirm that the
>>>>> correct .dovecot.sieve file is used when email is delivered.
>>>>>
>>>>> Shortly, the issue is, that ingo is writing the rules to the wrong
>>>>> file (it is actually always using the same file.) What can I do? I
>>>>> just did a MySQL dump of the Horde database right now and looked for
>>>>> sieve - nothing found. I was assuming the path/location is somewhere
>>>>> in there.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>>
>>>>> Cheers
>>>>> Thomas
>>>>>
>>>>>
>>>>> Versions used
>>>>> Horde Groupware Webmail Edition  1.2.5
>>>>> Filters (ingo)  H3 (1.2.3)
>>>>> Debian Lenny, up2date
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>
>