Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap no workee once again
Date: Fri, 06 Jan 2012 20:43:17 -0500	[thread overview]
Message-ID: <874nw8uw22.fsf@lifelogs.com> (raw)
In-Reply-To: <878vlq15uq.fsf@newsguy.com>

On Mon, 02 Jan 2012 10:28:29 -0500 Harry Putnam <reader@newsguy.com> wrote: 

HP> Running recent gnus and emacs
HP> These lines in .gnus:


HP>    (setq gnus-secondary-select-methods
HP>         '((nnml ""))) 

HP>   (add-to-list 'gnus-secondary-select-methods '(nnimap "hputnam3"
HP>                               (nnimap-address "imap.gmail.com")))

HP> [ PS - Also tried with the long form username hputnam3@gmail.com, with
HP> no hange and as far as I remember it was just `hputnam3' that has been
HP> working.

HP> -------        ---------       ---=---       ---------      -------- 

HP> And this in .authinfo (password obfuscated)

HP>   machine imap.gmail.com login hputnam3@gmail.com password ??XXX?? port imap

HP> -------        ---------       ---=---       ---------      -------- 

HP> Have been working to retrieve groups on gmail. It quit working
HP> recently. not sure why.

HP> In messages buffer I get:

HP> ,----
HP> | Opening nnimap server on hputnam3...
HP> | Opening connection to imap.gmail.com via tls...
HP> | Opening TLS connection to `imap.gmail.com'...
HP> | Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
HP> | Opening TLS connection to `imap.gmail.com'...done
HP> | Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
HP> | Server previously determined to be down; not retrying
HP> | Opening nnimap server on hputnam3...
HP> | Opening connection to imap.gmail.com via tls...
HP> | Opening TLS connection to `imap.gmail.com'...
HP> | Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
HP> | Opening TLS connection to `imap.gmail.com'...done
HP> | Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
HP> | Server previously determined to be down; not retrying
HP> `----

HP> Authentication failures.. but why?  I can login with those same
HP> credentials just fine.

Could you please do:

`M-x auth-source-forget-all-cached'

Then turn up `gnus-verbose' to 10 and `auth-source-debug' to 'trivia
just before trying to connect, then show us the logs in *Messages*?

Thanks
Ted




  parent reply	other threads:[~2012-01-07  1:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 15:28 Harry Putnam
2012-01-02 16:03 ` Steinar Bang
2012-01-02 22:00   ` Harry Putnam
2012-01-03  7:39     ` TIP: using git-bisect (Was: nnimap no workee once again) Steinar Bang
2012-01-03 20:10       ` TIP: using git-bisect Harry Putnam
2012-01-02 16:27 ` nnimap no workee once again Tassilo Horn
2012-01-07  1:43 ` Ted Zlatanov [this message]
2012-01-09 19:13   ` Harry Putnam
2012-01-10 14:50     ` Ted Zlatanov
2012-01-11  3:16       ` Harry Putnam
2012-01-11  3:32         ` Harry Putnam

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=874nw8uw22.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).