On Wednesday 13 October 2004 00:23, William K. Hardeman wrote: Hi William,
> I had this problem, too, after I upgraded. I can't say exactly the best way > to deal with the sieve script error, except to say that, if the 'mcp' > account has an existing sieve script, it needs to be byte compiled into the > new format. The man pages should have more information on that. Well, user mcp does not have a sieve script, therefore the error :) It would be nice if there's a way to ignore non-existent sieve scripts, because a new created user won't have a sieve script. > Regarding the sasl errors, specifically the sql error, just move the sasl > mechanism .so object files in /usr/lib/sasl2 or /usr/local/lib/sasl2 that > you are _not_ using to some other place (or delete them). SASL is > attempting to load those libraries and use them in the chain of available > authentication mechanisms. I created a sub-directory named > /usr/lib/sasl2/not_used and put them all in there, so I would have them if > needed in the future, but they wouldn't generate spurious log messages or > be used when I did not want them to be used. that's it. Thanks alot :-) -- ciao, Marc --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
