From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: nnimap no workee once again
Date: Mon, 02 Jan 2012 17:00:57 -0500 [thread overview]
Message-ID: <87d3b1sr1i.fsf@newsguy.com> (raw)
In-Reply-To: <87obumqefo.fsf@dod.no>
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
`----
next prev parent reply other threads:[~2012-01-02 22:00 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 [this message]
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
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=87d3b1sr1i.fsf@newsguy.com \
--to=reader@newsguy.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).