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: Thu, 17 Feb 2011 08:16:22 -0600 [thread overview]
Message-ID: <87aahu3fwp.fsf@lifelogs.com> (raw)
In-Reply-To: <ijj85l$8js$1@dough.gmane.org>
On Thu, 17 Feb 2011 11:34:43 -0200 Raphael Kubo da Costa <kubito@gmail.com> wrote:
RKdC> Ted Zlatanov wrote:
>> On Thu, 17 Feb 2011 01:34:25 -0200 Raphael Kubo da Costa
RKdC> I am still wondering if the prompts I get are better than the old
RKdC> though -- the old code used to infer the port from my ~/.gnus
RKdC> (via nnimap-server-port),
>>
>> This can be helped with `auth-source-creation-defaults'. I will add a
>> default to the first port to `nnimap-credentials'.
RKdC> Well, it got a bit confusing now.
RKdC> I need to use port 993 to connect to the IMAP server. Previously, Gnus tried
RKdC> the port list for ssl (143, 993, imap and imaps), settled on 993 and asked
RKdC> me for my username and password showing "imap.gmail.com:993" in the prompt.
IMAP/S is normally port 993 (IMAP over SSL). TLS is on port 143. This
is confusing enough that before we had a whole lot of special cases to
get the result you detail.
RKdC> Now, the prompt shows me "Personal:143", so the host is not shown, and the
RKdC> port is wrong. It then asks me to write this information (with the wrong
RKdC> port) into ~/.authinfo.gpg. I then choose "n" and it works fine, because
RKdC> after that Gnus ends up connecting to port 993.
The first part, "Personal", is the nnimap server name. It will work as
far as Gnus is concerned. I guess we can put the address first in the
list so it gets picked as the default. I'll commit that change.
The second part is correct: 143 is the first element of the search that
nnimap.el constructs. We should put "imap" first if that's what we want
(but Lars should decide the order). I will change auth-source to ask
when there are multiple candidates.
RKdC> Any other program that prompts for confirmation of this sort of data usually
RKdC> uses "***" or something like that when asking to write the password.
RKdC> Wouldn't it be possible to at least add a variable for the paranoid? :)
OK.
Ted
next prev parent reply other threads:[~2011-02-17 14:16 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 [this message]
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
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=87aahu3fwp.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).