I seem to have worked around my earlier problem. For some reason, the Cyrus::SIEVE::managesieve Perl package didn't get properly compiled/installed when I first built Cyrus 2.3.14. I remade and installed this package and the "sieveshell" script, and sieveshell works for me now. And, using sieveshell, I am able to contact my mail server and manipulate Sieve scripts on it. So, my original, immediate problem appears to be solved. Sorry it was such a bizarre problem that no one else out there seemed to have any idea what to say about it. The bug may, in fact, be in "sieve-connect", not in the Cyrus code. But I'm still suspicious of a situation where sieve-connect may have done something which caused a timsieved process to crash mysteriously -- something which no client should be able to do to a server process. But whatever . . . . -- Rich Wales / richw@xxxxxxxxx / richw@xxxxxxxxxxxx Wikipedia: http://en.wikipedia.org/wiki/User:Richwales Facebook: http://www.new.facebook.com/profile.php?id=206680 ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
