This is just a follow-up for the archives. When I create the IMAP
folders by hand from an IMAP client, sieve works. I had expected that
Cyrus would create the folder if it didn't already exist - apparently,
it doesn't. I'll try Nick's suggestion about the filepaths, too.
Thanks to Nick and Paul
MAIL PROTECTED]
Date: Thu, 14 Nov 2002 11:27:57 -0800 (PST)
Subject: Re: Sieve isn't sieving for me - things to check
> The link from /usr/lib/sasl2 to /usr/local/lib/sasl2 did indeed work.
> Now sieveshell works and I can upload a sieve script. But it still
> isn't sieving.
>
&
The link from /usr/lib/sasl2 to /usr/local/lib/sasl2 did indeed work.
Now sieveshell works and I can upload a sieve script. But it still
isn't sieving.
PROMPT# sieveshell --user=sstest --authname=sstest localhost
connecting to localhost
Please enter your password:
> put /root/sievescr
This may or may not be your problem, but when I had the exact same
problem, I fixed it like this. (Everything else worked fine, but sieve
showed no available mechs, and I couldn't login using sieveshell.)
When I first built Cyrus, I symlinked to the /usr/lib/sasl2 directory
like this:
# ln -s /us
I went through the same thing..
There were 4 basic things to check
1) Check the location of the sasl2 libs
The default location is /usr/lib/sasl2 but apparently sometimes you need
to link that dir to /usr/lib/local/sasl2. Get and use strace to check this.
2) Incorrect permissions on the s
