SASL/Sieve problems

[David H. Lynch Jr.]

    I recently had to rebuild a Cyrus 2.2 Mail Server.
    I cloned the root partition first.
    Built the new system.
    copied the appropriate configuration from the old system, checked
permissions and got everything running.
    Cyrus IMAP works fine.
    cyradm works fine.
    but sieve filters on accounts are inactive - they are present in
/var/spool/sieve

    And sieveshell will not authenticate.
    authlog has lots of  cyrus/sieve errors every time I try to run
sieveshell.
    basically sieveshell appears to be running through a bunch of SASL
authentication methods (NTLM, OTP, DIGEST-MD5, ..) and failing each
    and finally complaining that there are "no worthy mechs"

    I have scoured the old system and I can not find anywhere that
sieve/SASL is configured separately from cyrus imap - and my imapd.conf,
and cyrus.conf have not changed.
   
    I am using sasldb for authentication. I have run sasldblistusers2
with expected results, checked permissions on everything sasl related.
   
    What am I missing ? How can cyrus imap be using SASL correctly but
sieve is not ?
 





-- 
Dave Lynch 						DLA Systems
Software Development:  				     Embedded Linux
717.627.3770 	     dhlii at dlasys.net 	      http://www.dlasys.net
fax: 1.253.369.9244 			       Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.