Gnus development mailing list
 help / color / mirror / Atom feed
From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: [BUG] Prefer AUTH=CRAM-MD5 makes login fail in some IMAP servers.
Date: Mon, 10 Jan 2011 19:21:43 +0100	[thread overview]
Message-ID: <871v4ktya0.fsf@babel.ls.fi.upm.es> (raw)

Hi all,

starting with:

,----
| commit 1809f181366e42a47ba94551b54fd0d56d7e8dee
| Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
| Date:   Sun Jan 2 23:28:40 2011 +0100
|
|     (nnimap-login): Prefer AUTH=CRAM-MD5, if it's available.
|
|     This avoids sending passwords in plain text over non-encrypted
|     channels.
`----

I cannot login to one of my IMAP servers anymore.

I have several IMAP servers enabled, but as much as I try to isolate
that faulty server the other connect. I've tried to edit newsrd.eld,
etc... but to no avail, one server always gets reconnected.

So I'm not able to meaningful debug it, but here is some info from IMAP
debug buffers:

29 BAD unrecognized IMAP4 command or invalid state
30 BAD unrecognized IMAP4 command or invalid state
31 BAD unrecognized IMAP4 command or invalid state
32 BAD unrecognized IMAP4 command or invalid state
33 BAD unrecognized IMAP4 command or invalid state
34 BAD unrecognized IMAP4 command or invalid state
35 BAD unrecognized IMAP4 command or invalid state
36 BAD unrecognized IMAP4 command or invalid state
37 BAD unrecognized IMAP4 command or invalid state
38 BAD unrecognized IMAP4 command or invalid state
39 BAD unrecognized IMAP4 command or invalid state
40 BAD unrecognized IMAP4 command or invalid state
41 BAD unrecognized IMAP4 command or invalid state
42 BAD unrecognized IMAP4 command or invalid state
43 BAD unrecognized IMAP4 command or invalid state
44 BAD unrecognized IMAP4 command or invalid state
45 BAD unrecognized IMAP4 command or invalid state
46 BAD unrecognized IMAP4 command or invalid state
47 BAD unrecognized IMAP4 command or invalid state
48 BAD unrecognized IMAP4 command or invalid state
* BYE user input timeout

Process *nnimap*<2> connection broken by remote peer

19:08:12 (nnimap "server" (nnimap-address "server.com") (nnimap-stream network))

19:08:15 7 AUTHENTICATE CRAM-MD5
19:08:22 29 EXAMINE "Spam"

Regards,
Emilio




             reply	other threads:[~2011-01-10 18:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 18:21 Emilio Jesús Gallego Arias [this message]
2011-01-11 18:51 ` Lars Magne Ingebrigtsen
2011-01-11 21:52   ` Emilio Jesús Gallego Arias
2011-01-11 21:57     ` Lars Magne Ingebrigtsen
2011-01-11 22:55       ` Emilio Jesús Gallego Arias
2011-01-22 19:29         ` Lars Ingebrigtsen
2011-01-24 17:44           ` Ted Zlatanov
2011-01-24 22:07             ` Lars Ingebrigtsen
2011-01-24 22:10               ` Ted Zlatanov
2011-01-24 22:30                 ` Lars Ingebrigtsen
2011-01-25 17:03                   ` Ted Zlatanov
2011-01-25 21:28                     ` Lars Ingebrigtsen
2011-01-25 22:00                       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871v4ktya0.fsf@babel.ls.fi.upm.es \
    --to=egallego@babel.ls.fi.upm.es \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).