From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Making Gnus ask my IMAP username and password after the recent auth-source changes
Date: Wed, 23 Feb 2011 12:56:48 -0600 [thread overview]
Message-ID: <87ipwalgun.fsf@lifelogs.com> (raw)
In-Reply-To: <ik3hof$5mt$1@dough.gmane.org>
On Wed, 23 Feb 2011 14:56:26 -0300 Raphael Kubo da Costa <kubito@gmail.com> wrote:
RKdC> This is my ~/.authinfo:
RKdC> machine imap.gmail.com login XXXX port 993
RKdC> When I lauch Gnus, it asks me if I want to carry on after a failed login
RKdC> attempt. No password was asked. *Messages* shows this:
RKdC> auth-source-search: found 3 backends matching (:max 1 :host
RKdC> ("imap.gmail.com" "Personal") :port ("143" "993" "imap" "imaps") :create t)
RKdC> auth-source-search-backend: got 1 (max 1) in netrc:~/.authinfo matching
RKdC> (:max 1 :host ("imap.gmail.com" "Personal") :port ("143" "993" "imap"
RKdC> "imaps") :create t)
RKdC> auth-source-search: found 1 results (max 1) matching (:max 1 :host
RKdC> ("imap.gmail.com" "Personal") :port ("143" "993" "imap" "imaps") :create t)
RKdC> nnimap (Personal) open error: 'NO (AUTHENTICATIONFAILED) Invalid credentials
RKdC> (Failure)'. Continue? (y or n)
RKdC> Couldn't open server on Personal
nnimap.el should handle the case where the returned info doesn't have a
password. There are cases where IMAP servers do not require a password,
so it would not be appropriate to ask in `nnimap-credentials'. I think
the change needs to be made in `nnimap-login', replacing all instances
of `password' with `(nnimap-login-password password)' which could look
like this (100% untested):
(defmacro nnimap-login-password (password)
(setq password (if password
password
(read-passwd "Password: "))))
This is something that Lars will have to do, though. I don't know that
code well enough to say whether it's the right solution; the password
prompt should mention the server, user name, and port. And it may make
sense to do this prompting for the user name as well.
Ted
next prev parent reply other threads:[~2011-02-23 18:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 2:06 Raphael Kubo da Costa
2011-02-15 13:46 ` Ted Zlatanov
2011-02-15 20:57 ` Raphael Kubo da Costa
2011-02-16 19:13 ` Ted Zlatanov
2011-02-16 20:39 ` Matt Lundin
2011-02-16 20:46 ` Ted Zlatanov
2011-02-17 1:15 ` Matt Lundin
2011-02-17 11:03 ` Ted Zlatanov
2011-02-17 13:49 ` Matt Lundin
2011-02-17 14:20 ` Matt Lundin
2011-02-17 15:22 ` Steinar Bang
2011-02-18 20:21 ` Ted Zlatanov
2011-02-21 19:40 ` Steinar Bang
2011-02-17 3:34 ` Raphael Kubo da Costa
2011-02-17 11:44 ` Ted Zlatanov
2011-02-17 13:34 ` Raphael Kubo da Costa
2011-02-17 14:16 ` Ted Zlatanov
2011-02-17 23:54 ` Lars Ingebrigtsen
2011-02-18 20:19 ` Ted Zlatanov
2011-02-18 23:10 ` Lars Ingebrigtsen
2011-02-22 21:52 ` Ted Zlatanov
2011-02-23 8:52 ` Lars Ingebrigtsen
2011-02-23 14:47 ` Ted Zlatanov
2011-02-23 17:00 ` Raphael Kubo da Costa
2011-02-23 17:09 ` Ted Zlatanov
2011-02-23 17:56 ` Raphael Kubo da Costa
2011-02-23 18:56 ` Ted Zlatanov [this message]
2011-02-25 4:42 ` Lars Ingebrigtsen
2011-02-25 11:31 ` Ted Zlatanov
2011-03-05 12:15 ` Lars Magne Ingebrigtsen
2011-03-08 18:26 ` Ted Zlatanov
2011-03-15 16:28 ` Lars Magne Ingebrigtsen
2011-03-15 16:43 ` Ted Zlatanov
2011-02-23 23:35 ` Lars Ingebrigtsen
2011-02-23 23:36 ` Lars Ingebrigtsen
2011-02-24 5:43 ` Ted Zlatanov
2011-02-24 11:35 ` Lars Ingebrigtsen
2011-02-24 13:06 ` Ted Zlatanov
2011-02-24 13:48 ` Raphael Kubo da Costa
2011-02-24 16:42 ` Ted Zlatanov
2011-02-25 4:47 ` 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=87ipwalgun.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).