"Kevin J. Menard, Jr." wrote:
>
> Hey Ken,
>
> Tuesday, July 24, 2001, 12:39:19 PM, you wrote:
>
> KM> "Kevin J. Menard, Jr." wrote:
> >>
> >> Hey David,
> >>
> >> Wednesday, July 25, 2001, 12:02:50 AM, you wrote:
> >>
> >> DF> I recreated your situation on my own system... but had no trouble...
> >>
> >> DF> cyradm -u cyrus localhost
> >> DF> Please enter your password: ********
> >> DF> IMAP Password: ******** (Why it asks for two passwords I don't
> >> DF> know... =] )
> >>
> >> I could be wrong here, but the first pass through is for MD5 SASL passwords
> >> or something. If that doesn't work, it falls back to a plaintext protocol,
> >> which would be sending a LOGIN command to the IMAP server directly. I don't
> >> know why the SASL passwd look up succeeds with LOGIN and not the other way,
> >> but go figure :-P
>
> KM> Close. The first is for a failed PLAIN attempt, and the second is for
> KM> IMAP LOGIN. This is a bug in IMAP.pm that I fixed in CVS. If you're
> KM> interested, just comment (or remove) the following line:
>
> KM> $opts{-mechanism} .= 'PLAIN';
>
> KM> This line was forcing cyradm to try PLAIN even if the server didn't
> KM> advertise it.
>
> But this has no affect if other methods are advertised and used, correct?
Yes.
> I mean, this is just appending PLAIN to the list already there, and AFAIK MD5
> takes precedence over PLAIN.
Yes.
> Likewise, should probably kill the line that
> says $opts{-mechanism} |= 'plain'; or something a little later on. I don't
> recall right now, and I don't have source in front of me.
Um, I don't think any other changes are necessary. If you actually have
an MD5 secret in sasldb then everything should be fine, otherwise the
behavior you are seeing is correct.
Ken
--
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
