i got this to work with manual installation.
for automatic installation there exists somewhere a web-frontend which is
called websieve.
i haven't used it until now.
manual installation:
i assume that "sievedir" is "/foo".
you are right, that sieve looks for the user "bar" in the folder
"/foo/b/bar" for sieve scripts.
on the mail-archive, i found a message, which explained, that sieve looks
in the folder for a script which is called "default". so i made a symbolic
link to my sieve script. (you can also rename it, but a symbolic link is
for me better, bacause i have some different sieve scripts.)
now it works for me without problems.
manfred
--On Donnerstag, 15. Februar 2001 16:03 -0500 Christopher Audley
<[EMAIL PROTECTED]> wrote:
> I'm trying to get sieve working with an installation of cyrus I'm
> prototyping.
>
> First the preliminaries, I've built and installed cyrus imap without
> mentioning sieve
> on the configure script command line ( no --enable or --disable-sieve ).
> The sieve
> directory is built, however ( libsieve.a exists ) so the build looks good.
> On install,
> I create the directory /var/imap/sieve and added the line 'sievedir:
> /var/imap/sieve
> to /etc/imapd.conf.
>
> On restart, the directory /var/imap/sieve is filled with subdirectories
> for every letter
> in the alphabet, so I guess the directory is found and all is well up to
> this point.
>
> So now I would like to put a sieve script on the server for my account (
> audley ).
> To this end I try sieveshell.pl. At first I went for installsieve as the
> documentation
> says but this directory wasn't built on my system and the Makefile.in
> wasn't even processed by configure, in fact the directory is never
> mentioned in configure
> or configure.in. A little searching turned up the perl script
> installsieve.pl in
> perl/sieve/scripts so I took a look at that and see that it is deprecated
> in favor of
> sieveshell.pl. So I'm trying sieveshell.pl and it claims that it can't
> connect to the
> server. When I examined the perl, it appears to be trying to connect to
> an ACAP
> server. So do I need ACAP running to use sieve? Why?
>
> On a separate track, I figure I'll try installing a sieve script manually.
> Not
> knowing what exactly is needed, I guess and put my sample script in
> /var/imap/sieve/a/audley. Nothing happens. Is this where the script is
> supposed
> to go?
>
> TIA
>
> Cheers
> Chris
>
>
>
