nnimap no workee once again

nnimap no workee once again

[Harry Putnam]

Running recent gnus and emacs

These lines in .gnus:


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

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

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

-------        ---------       ---=---       ---------      -------- 

And this in .authinfo (password obfuscated)

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

-------        ---------       ---=---       ---------      -------- 

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

In messages buffer I get:

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

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

Re: nnimap no workee once again

[Steinar Bang]

Have you tried using git bisect to narrow it down to a specific commit?

Re: nnimap no workee once again

[Harry Putnam]

Steinar Bang <sb@dod.no> writes:

> Have you tried using git bisect to narrow it down to a specific commit?

I've never bisected a git... I Disected a few frogs once : )

Honestly I have no idea what you are talking about... but it did get
me thinking to update gnus and see if the problem persists.

-------        ---------       ---=---       ---------      -------- 

Update:  I just did a `git pull' in my gnus module ./configure && make

Started gnus but see nothing has changed.... still the same failure
and same message output

Tassilo Horn <tassilo@member.fsf.org> writes:


> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry,
>
>>   (add-to-list 'gnus-secondary-select-methods '(nnimap "hputnam3"
>>                               (nnimap-address "imap.gmail.com")))
>>
>> -------        ---------       ---=---       ---------      -------- 
>>
>> And this in .authinfo (password obfuscated)
>>
>>   machine imap.gmail.com login hputnam3@gmail.com password ??XXX?? port imap
>>
>> -------        ---------       ---=---       ---------      -------- 
>
> My ./authinfo.gpg entry basically looks similar, except that I don't
> specify the port (Gnus figures that out) and I have a "force yes".  Try
>
>   machine imap.gmail.com login hputnam3@gmail.com password ??XXX?? force yes
>
> and see what happens.

I edited authinfo as suggested; restarted gnus, but no success... same
kind of messages:

,----
| Opening nnimap server on hputnam3@gmail.com...
| Opening connection to imap.gmail.com via tls...
| Opening TLS connection to `imap.gmail.com'...
| Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
| Opening TLS connection to `imap.gmail.com'...done
| Opening nnimap server on hputnam3@gmail.com...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
`----

I feel sure it will end up being something really silly and
boneheaded.  Like it really is the wrong credentials or the
like... but I can login to hputnam3 account on gmail with those self
same credentials.

Steiner may have something... so I will update gnus and see what
happens then post this with that report as well

-------        ---------       ---=---       ---------      -------- 

Turned out neither of your suggestion, nor updating to latest gnus has
helped the situation... same basic errors:

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

TIP: using git-bisect (Was: nnimap no workee once again)

[Steinar Bang]

>>>>> Harry Putnam <reader@newsguy.com>:
> Steinar Bang <sb@dod.no> writes:
>> Have you tried using git bisect to narrow it down to a specific commit?

> I've never bisected a git... I Disected a few frogs once : )

Googling for git-bisect should give you the docs
 http://book.git-scm.com/5_finding_issues_-_git_bisect.html

> Honestly I have no idea what you are talking about... but it did get
> me thinking to update gnus and see if the problem persists.

Ok.  Sounds like the not working didn't come because of a "git pull"...?
If so, it's a good idea to say so.  It narrows down the possibilities.

Using git bisect applies when a "git pull" leaves you with a broken
gnus.  What I do in that case, is:
 1. Find the SHA1 from before the last pull (the contents of
    .git/ORIG_HEAD), this will be "good"
 2. Start the command
     git bisect start bad good
    where bad is a sha1 hash, or tag, that you know is bad, eg. HEAD and
    good is a sha1 hash, or tag, that you know is good.  If I've done
    nothing except pulling from upstream in my repo, and the previous
    version was ok, I can actually do this
     git bisect start HEAD ORIG_HEAD
    then you loop, doing this:
     a. do "make clean" followed by "make" (or "./configure && make" if
        that's your preference)
     b. start a new emacs and start gnus and see if the problem persist.
        If the problem persists, do
         git bisect bad
        If the problem isn't there, do
         git bisect good
        If "git bisect" tells me that it has found the first offending
        commit, then go to 3, else go to a.
 3. Copy the text from "git bisect" where it found the offending commit,
    and send it to the gnus group
 4. Use "git bisect reset" to set the working directory back to normal,
    then decide if I want to try to fix the issue yourself, or pull
    back to the last good version, until it can be fixed, and then "make
    clean" and "make" gnus


 

Re: TIP: using git-bisect

[Harry Putnam]

Steinar Bang <sb@dod.no> writes:

> Using git bisect applies when a "git pull" leaves you with a broken
> gnus.  What I do in that case, is:

 [...] snipped the nifty walk thru

Thanks Steiner... that looks really useful

Re: nnimap no workee once again

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

>   (add-to-list 'gnus-secondary-select-methods '(nnimap "hputnam3"
>                               (nnimap-address "imap.gmail.com")))
>
> -------        ---------       ---=---       ---------      -------- 
>
> And this in .authinfo (password obfuscated)
>
>   machine imap.gmail.com login hputnam3@gmail.com password ??XXX?? port imap
>
> -------        ---------       ---=---       ---------      -------- 

My ./authinfo.gpg entry basically looks similar, except that I don't
specify the port (Gnus figures that out) and I have a "force yes".  Try

  machine imap.gmail.com login hputnam3@gmail.com password ??XXX?? force yes

and see what happens.

Bye,
Tassilo

Re: nnimap no workee once again

[Ted Zlatanov]

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

Re: nnimap no workee once again

[Harry Putnam]

Ted Zlatanov <tzz@lifelogs.com> writes:


[...]

>
> 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*?

Quite a bit of hoopla but here it is. I think one or two lines are
lost when I open the messages buffer... apparently unavoidable.

-------        ---------       ---=---       ---------      -------- 
Messages buffer:

[...]

Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hputnam3...
Opening connection to imap.gmail.com via tls...
Opening TLS connection to `imap.gmail.com'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.gmail.com'...done
Opening TLS connection to `imap.gmail.com'...done
auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-netrc-parse: using CACHED file data for ~/.authinfo
auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)
Server previously determined to be down; not retrying
Opening nnimap server on hput3fm...done

Re: nnimap no workee once again

[Ted Zlatanov]

On Mon, 09 Jan 2012 14:13:08 -0500 Harry Putnam <reader@newsguy.com> wrote: 

HP> auth-source-search: found 3 backends matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
HP> auth-source-netrc-parse: using CACHED file data for ~/.authinfo
HP> auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
HP> auth-source-search: found 1 results (max 1) matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143") :user nil :require (:user :secret) :create t)
HP> Opening nnimap server on hputnam3...failed: NO (AUTHENTICATIONFAILED) Invalid credentials (Failure)

That's weird.  Well, it looks like the netrc data is cached.  Could you
check, using the new function I just added for Richard, that the first
two elements are correctly the user name and the password you want?

(auth-source-user-and-password "imap.gmail.com")
(auth-source-user-and-password "hputnam3")

Thanks
Ted

Re: nnimap no workee once again

[Harry Putnam]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Mon, 09 Jan 2012 14:13:08 -0500 Harry Putnam <reader@newsguy.com> wrote: 
>
> HP> auth-source-search: found 3 backends matching (:max 1 :host
> HP> ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143")
> HP> :user nil :require (:user :secret) :create t)
> HP> auth-source-netrc-parse: using CACHED file data for ~/.authinfo
> HP> auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo
> HP> matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port
> HP> ("imaps" "imap" "993" "143") :user nil :require (:user :secret)
> HP> :create t)
> HP> auth-source-search: found 1 results (max 1) matching (:max 1 :host
> HP> ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143")
> HP> :user nil :require (:user :secret) :create t)
> HP> Opening nnimap server on hputnam3...failed: NO
> HP> (AUTHENTICATIONFAILED) Invalid credentials (Failure)
>
> That's weird.  Well, it looks like the netrc data is cached.  Could you
> check, using the new function I just added for Richard, that the first
> two elements are correctly the user name and the password you want?
>
> (auth-source-user-and-password "imap.gmail.com")
> (auth-source-user-and-password "hputnam3")

You did mean for that to be eval'd right?

If so, in each case it reports `(nil nil nil)'

Is that what you expected?

Re: nnimap no workee once again

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Mon, 09 Jan 2012 14:13:08 -0500 Harry Putnam <reader@newsguy.com> wrote: 
>>
>> HP> auth-source-search: found 3 backends matching (:max 1 :host
>> HP> ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143")
>> HP> :user nil :require (:user :secret) :create t)
>> HP> auth-source-netrc-parse: using CACHED file data for ~/.authinfo
>> HP> auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo
>> HP> matching (:max 1 :host ("imap.gmail.com" "hputnam3") :port
>> HP> ("imaps" "imap" "993" "143") :user nil :require (:user :secret)
>> HP> :create t)
>> HP> auth-source-search: found 1 results (max 1) matching (:max 1 :host
>> HP> ("imap.gmail.com" "hputnam3") :port ("imaps" "imap" "993" "143")
>> HP> :user nil :require (:user :secret) :create t)
>> HP> Opening nnimap server on hputnam3...failed: NO
>> HP> (AUTHENTICATIONFAILED) Invalid credentials (Failure)
>>
>> That's weird.  Well, it looks like the netrc data is cached.  Could you
>> check, using the new function I just added for Richard, that the first
>> two elements are correctly the user name and the password you want?
>>
>> (auth-source-user-and-password "imap.gmail.com")
>> (auth-source-user-and-password "hputnam3")
>
> You did mean for that to be eval'd right?
>
> If so, in each case it reports `(nil nil nil)'
>
> Is that what you expected?

Yikes, please do not waste anymore of your time on this.  I found a
second entry for that mailbox in .authinfo, that still contained the
old credentials.

I'm sorry.  My only excuse is that it had been placed in a section of
.authinfo dealing with other servers and I just did now look in that
section  where it should not have been, very well.

So the old credentials were listed above the newer ones.