[ingo] ingo is modifying wrong .sieve file

Mariusz Czyz mczyz at artic.edu
Fri Jan 15 16:28:37 UTC 2010


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,

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

More information about the ingo mailing list