I this problem only with DIGEST-MD5? What about CRAM-MD5? You might
try doing a clean compile of SASL and Cyrus. Sometimes weird behavior
occurs when you update from CVS but don't build cleanly (depending on
what code has changed).
[EMAIL PROTECTED] wrote:
>
> Here's what I'm seeing in auth.log
>
> Feb 9 14:44:44 myhost sieve[384]: DIGEST-MD5 server step 1
> Feb 9 14:44:44 myhost sivtest: DIGEST-MD5 client step 2
> Feb 9 14:44:48 myhost sivtest: DIGEST-MD5 client step 2
> Feb 9 14:44:48 myhost sieve[384]: DIGEST-MD5 server step 2
>
> ........
>
> Feb 9 14:45:10 myhost imap[390]: DIGEST-MD5 server step 1
> Feb 9 14:45:10 myhost imtest: DIGEST-MD5 client step 2
> Feb 9 14:45:13 myhost imtest: DIGEST-MD5 client step 2
> Feb 9 14:45:13 myhost imap[390]: DIGEST-MD5 server step 2
> Feb 9 14:45:13 myhost imtest: DIGEST-MD5 client step 3
>
> So there appears to be a missing client step 3 for sivtest?
>
> I'm seeing this in imapd logs:
>
> Feb 9 17:58:35 rainman master[1383]: about to exec
> /usr/cyrus/bin/timsieved
> Feb 9 17:58:35 rainman sieve[1383]: executed
> Feb 9 17:58:35 rainman sieve[1383]: accepted connection
>
> Here's the complete output from sivtest:
>
> S: "IMPLEMENTATION" "Cyrus timsieved v2.2.prealpha"
> S: "SASL" "DIGEST-MD5"
> S: "SIEVE" "fileinto reject envelope vacation imapflags notify
> subaddress relational regex"
> S: "STARTTLS"
> S: OK
> C: AUTHENTICATE "DIGEST-MD5"
> S: {240}
> S:
>
>bm9uY2U9IkRJczNqU3VNRzhXTUhKYXI0MEpPSW1wNUZZZk0rSFNpT0N1SE5NamJibGc9IixyZWFsbT0icmFpbm1hbiIscW9wPSJhdXRoLGF1dGgtaW50LGF1dGgtY29uZiIsY2lwaGVyPSJyYzQtNDAscmM0LTU2LHJjNCxkZXMsM2RlcyIsbWF4YnVmPTQwOTYsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=
> Please enter your password:
> C: {376+}
>
>dXNlcm5hbWU9ImVkd2FyZC56YXJlY29yIixyZWFsbT0icmFpbm1hbiIsbm9uY2U9IkRJczNqU3VNRzhXTUhKYXI0MEpPSW1wNUZZZk0rSFNpT0N1SE5NamJibGc9Iixjbm9uY2U9IkRnVGtxNXVsNVNnVnVQRExzbEw5Wit5Z1hnYnZzU3NoNlpWaWVqS00xaTQ9IixuYz0wMDAwMDAwMSxxb3A9YXV0aC1jb25mLGNpcGhlcj0icmM0IixtYXhidWY9MTAyNCxkaWdlc3QtdXJpPSJzaWV2ZS9sb2NhbGhvc3QubG9jYWxkb21haW4iLHJlc3BvbnNlPWY1NTI0NGYwMTk0OTI0NzU1OGE4YzA0MTg2ZjkyYTJi
> S: NO "Authentication Error"
> Authentication failed. generic failure
> Security strength factor: 128
>
> Thanks again for taking a look.
>
> Ed.
>
> ---------Included Message----------
> >Date: Sun, 09 Feb 2003 10:30:34 -0500
> >From: "Ken Murchison" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Cc: <[EMAIL PROTECTED]>
> >Subject: Re: strange sieve issue
> >
> >
> >
> >[EMAIL PROTECTED] wrote:
> >>
> >> With cyrus 2_2 from CVS I have a successful virtual domain
> configuration
> >> up and operational with sasl and postfix.
> >>
> >> I'm having some strange sieve issues though.
> >>
> >> This command results in the following error
> >>
> >> sivtest -u edward.zarecor -a edward.zarecor -v -m digest-md5 -r
> >> example.com localhost
> >>
> >> S: NO "Authentication Error"
> >> Authentication failed. generic failure
> >> Security strength factor: 128
> >>
> >> While the exact same switches issued to imtest yields successful
> login.
> >>
> >> imtest -u edward.zarecor -a edward.zarecor -v -m digest-md5 -r
> >> example.com localhost
> >>
> >> S: A01 OK Success (privacy protection)
> >> Authenticated.
> >> Security strength factor: 128
> >
> >
> >Post the rest of the sivtest output. Also turn up the auth logging to
> >debug level and post the relevant parts of auth.log.
> >
> >--
> >Kenneth Murchison Oceana Matrix Ltd.
> >Software Engineer 21 Princeton Place
> >716-662-8973 x26 Orchard Park, NY 14127
> >--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
> >
> >
> ---------End of Included Message----------
>
> Content-Type: application/octet-stream; name=""
> Content-Transfer-Encoding: BASE64
>
> DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tMTM3OTU4NjM1NDI0MDY5MTQ5MzI2MjQ0
> MDI4Mw==
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
