Victor wrote:
>
> Well, thanks to Haim Dimermanas, now my setup works.
>
> Except one thing that has been discussed on the mailing list but without any
> solutions: sieve.
> neither installsieve nor sieveshell seem to work.
>
> ----- SHELL OUTPUT -----
>
> $ /usr/cyrus/bin/sieveshell -u [EMAIL PROTECTED] localhost
> connecting to localhost
> Please enter your password: *****
> unable to connect to server: Authentication error at
> /usr/cyrus/bin/sieveshell line 149, <STDIN> chun
> k 1.
>
> $ /usr/cyrus/bin/installsieve -i ./test.sieve -u [EMAIL PROTECTED] localhost
> Please enter your password: *****
> Unable to connect to server at /usr/cyrus/bin/installsieve line 121, <STDIN>
> chunk 1.
>
> ----- SHELL OUTPUT -----
>
> Is CYRUS actually a production ready system? As I understand it, CMU is
> using it. Is it all working for them?
> I really like the aspects of the system, if only it could all work. I don't
> seem to be the only one having these issues (especially with perl modules).
> Are there C alternatives to cyradm and sieveshell?
>
> When is the Cyrus 2.1 supposed to arrive?
well, it seems to be working but the troubleshooting is extremely
hard. and the sieve is extra hard to troubleshoot.
my last problem was that I included two reject rules in one script
(and a message matched both). Of course I got no message about this
problem (I have enabled log to syslog), even test program (located in
sieve subdir of cyrus source tree) didn't say anything interesting, only
said error (printed some number which you can find in one of the *.h
files and it means sieve error). I had to debug the sieve test to find
out what's the problem (and there is an error message inside of the
program but it get's ignored (never reported to user).
overall quite annoying... there were some other problems of the same
character (wrong settings but since lot of settings are not documented
how can one get them right?)
erik
