Just as a test, change the sievedir to usehomedirs, and then test a
sieve script with that. You will not be able to use installsieve, or
sieveshell in this case, because it will say "can't use home directory"
or something to that effect. I am running the same version on one of my
servers, and sieve works fine with the home directory.  Haven't tried it
the other way.  If sieve works using the home directory, it may help
narrow down the problem.

B

Jim Holmes wrote:
> 
> Didn't help, guess that would have just been too easy. Thanks anyway
> 
> -jlh
> 
> --On Wednesday, January 02, 2002 10:07 -0500 Robert Scussel
> <[EMAIL PROTECTED]> wrote:
> 
> > Your configuration file looks fine.
> >
> > Try explicitly setting the sievedir to /usr/sieve, or wherever your
> > sieve scripts are kept.  If installsieve is working, I assume that they
> > are in /usr/sieve.
> >
> > Hope this helps.
> >
> > B
> 
> Jim Holmes
> [EMAIL PROTECTED]

-- 
Robert Scussel
1024D/BAF70959/0036 B19E 86CE 181D 0912  5FCC 92D8 1EA1 BAF7 0959

Reply via email to