Re: [Kolab-devel] Fwd: Re: can't connect to Sieve -- bug ?
Johannes Graumann <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | Graumann Family |
| Message-ID | <[email protected]> |
Geoff Nordli wrote: > > > -------- Original Message -------- > Subject: Re: can't connect to Sieve > Date: Thu, 21 Nov 2013 12:12:35 -0800 > From: Geoff Nordli <[email protected]> > Reply-To: [email protected] > To: [email protected] > > > > On 13-11-21 12:02 PM, Troy Carpenter wrote: >> I had something similar recently. I was able to connect to the daemon, >> but >> Kolab and Roundcube had issues. From memory, Kolab said it couldn't >> retrieve the scripts, while Roundcube complained about not connecting to >> the server. >> >> 1. Check to make sure the /var/lib/imap/sieve directory exists and has >> what you would expect below that ("domain/<letter>/<domainname>"). >> 2. Check permissions (on my system that's 700) and ownership >> (cyrus:mail). >> > > Thanks Troy. > > You are right, it doesn't have that folder structure under sieve > directory. > > Maybe it is a bug then? > > Anyone have ideas on when this should be created? > > Geoff > > > ---------------- > > I am running CentOS 6.4 with Kolab Enterprise. > > It seems the Sieve folder doesn't get correctly setup. > > Can anyone point me to the script that is supposed to configure the > directory? Hello, I have exactly the same configuration and problem - it's the last thing that's preventing me from going life. Any pointers on how to fix the inexistent sieve structure? Geoff, are you running by any chance in an lxc container as well and may this be related? Joh