Cyrus-IMAP authenticates - Sieve doesn't ?!?

Cyrus-IMAP authenticates - Sieve doesn't ?!?

Post by poesi » Thu, 08 Jul 2004 05:25:35


I have a working installation of Cyrus-IMAP, except for Sieve. The
'timsieved' server runs, but I cannot authenticate to the server.

With sivtest <servername> I get:

S: "IMPLEMENTATION" "Cyrus timsieved v2.2.4"
S: "SASL" "PLAIN LOGIN DIGEST-MD5 CRAM-MD5"
S: "SIEVE" "fileinto reject envelope vacation imapflags notify
subaddress relational regex"
S: OK
C: AUTHENTICATE "DIGEST-MD5"
S: {240}
S: (...)
Please enter your password:
C: {344+} (...)
S: NO "Authentication Error"
Authentication failed. generic failure
Security strength factor: 128

With 'imtest <servername>' I get:

S: * OK <servername> Cyrus IMAP4 v2.2.4 server ready
C: C01 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS
NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND
BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE
AUTH=DIGEST-MD5 AUTH=CRAM-MD5 SASL-IR
S: C01 OK Completed
C: A01 AUTHENTICATE DIGEST-MD5
S: + (...)
Please enter your password:
C: (...)
S: + (...)
C:
S: A01 OK Success (privacy protection) Authenticated.
Security strength factor: 128

With 'sieveshell <servername>' I get:

connecting to <servername>
Please enter your password:
Please enter your password:
Bad protocol from MANAGESIEVE server: lost connection

auth.log shows the following lines for the above three tests:

Jul 6 12:10:37 <servername> sieve[3222]: DIGEST-MD5 server step 1
Jul 6 12:10:37 <servername> sivtest: DIGEST-MD5 client step 2
Jul 6 12:10:41 <servername> sivtest: DIGEST-MD5 client step 2
Jul 6 12:10:41 <servername> sieve[3222]: DIGEST-MD5 server step 2

Jul 6 12:14:41 <servername> imap[3231]: DIGEST-MD5 server step 1
Jul 6 12:14:41 <servername> imtest: DIGEST-MD5 client step 2
Jul 6 12:14:46 <servername> imtest: DIGEST-MD5 client step 2
Jul 6 12:14:46 <servername> imap[3231]: DIGEST-MD5 server step 2
Jul 6 12:14:46 <servername> imtest: DIGEST-MD5 client step 3

Jul 6 12:24:19 <servername> sieve[3261]: DIGEST-MD5 server step 1
Jul 6 12:24:19 <servername> perl: DIGEST-MD5 client step 2
Jul 6 12:31:52 <servername> sieve[3261]: DIGEST-MD5 server step 2
Jul 6 12:31:57 <servername> sieve[3261]: attempting server step after
doneflag

The tests results are the same if I specify different users and/or
authentication mechanisms.

Sieve is running. I do get this header added to emails: X-Sieve: CMU
Sieve 2.2

If I dump the SASL database with sasldblistusers2 I get a user
password, a cmusaslsecretSRP, and a cmusaslsecretOTP for each login
name.

I did, initially, have a great deal of difficulty getting the SASL
code working with Cyrus-imap. Most, if not all, of those problems were
related to multiple versions of the Berkeley Db along with older
versions of some of the utilities that were still installed. I've
looked for those same problems with sieve but versions, latest builds,
etc. look ok.

Comments and suggestions are most welcome.

Cork Crawbaugh
poesis, inc.