Daryl Field wrote:
>
> I'm using(trying to) use sieve to filter, am using homedir for the scripts.
> It doesn't work & I'm not getting any usefull feedback via any of the logs.
> Here are a few details re the current configuration. If anyone is aware of
> any documentation I'm missing & could point me in the right direction, I'd
> be eternally gratefull.
>
> Cyrus.conf:
> sieve cmd="timsieved" listen="sieve" prefork=0
>
> imapd.conf:
> partition-default: /var/spool/imap
> admins: cyrusadm
> sasl_pwcheck_method: saslauthd
> sieveusehomedir: true
> allowanonymouslogin: no
> imapidresponse: no
>
> ~$less ~xxx/.sieve
> require ["fileinto", "reject", "vacation", "regex", "relational"];
>
> if header :contains ["to", "cc"] "[EMAIL PROTECTED]" {
> fileinto "INBOX.Cyrus";
> } elsif header :contains ["to", "cc"] "list2" {
> fileinto "INBOX.list2";
> }
>
> This log entry may be from a filter attempt - but I'm of the opinion, its
> from when I tried to use sieveshell without the usehomedir option being
> present, as theres not enough entries like this to indicate they are
> carried out on every filter attempt:
>
> Feb 18 11:46:19 mini-me master[28444]: about to exec
> /usr/cyrus/bin/timsieved
> Feb 18 11:46:19 mini-me sieve[28444]: executed
> Feb 18 11:46:19 mini-me sieve[28444]: accepted connection
> Feb 18 11:46:19 mini-me timsieved[28444]: can't use home directories
timesieved is only used when sieve scripts are stored in the 'sievedir'
hierarchy. If you're using home directories, then there is no reason to
have timsieved in cyrus.conf.
The syntax of your script looks ok, but you might want to check it with
the sieve/test.c program in the distribution. Other than that, make
sure that the 'cyrus' user has permissions to read the sieve script --
that includes execute permissions on all of the parent directories of
the script.
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
