From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more
Date: Wed, 16 Feb 2011 12:29:08 -0600 [thread overview]
Message-ID: <874o836dfv.fsf@lifelogs.com> (raw)
In-Reply-To: <mailman.12.1297821996.25725.bug-gnu-emacs@gnu.org> (Stefan Monnier's message of "Tue, 15 Feb 2011 20:54:32 -0500")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.bug as well.
On Tue, 15 Feb 2011 20:54:32 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
SM> When I start Gnus, it seems to try and connect to my IMAP server but
SM> never asks for my password (which I don't save in authinfo.gpg).
SM> In just ends up saying "done", but the *Server* buffer says "offline".
SM> If I try to use O in the *Server* buffer, it switches instantly to
SM> "opened" but if I try to do anything that involves the IMAP server,
SM> I get (wrong-type-argument arrayp nil) errors because nnimap-object
SM> is nil.
I think this is fixed in the Gnus trunk as far as the auth-source
credentials go (Lars will have to fix the nnimap code failure on empty
credentials).
Now auth-source-search with :create t and :type 'netrc will ask for all
the missing data. If the user doesn't want to add the netrc entry, it
will still work (until the password-cache times out).
I have two usability questions (cross-posting to the Gnus mailing list):
1) should we have a global override to say "never add netrc entries", or
should the prompt be Y/N/y/n instead of just y-or-n-p, or should the
save question be asked only once per file, or something else?
2) should auth-source let-bind the password-cache timeout to something
larger? The default is pretty short and for auth-source I think at
least 30 minutes are reasonable. It could be a customizable integer.
Thanks
Ted
next parent reply other threads:[~2011-02-16 18:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12.1297821996.25725.bug-gnu-emacs@gnu.org>
2011-02-16 18:29 ` Ted Zlatanov [this message]
2011-02-16 21:22 ` Stefan Monnier
2011-02-16 21:34 ` Michael Albinus
2011-02-16 22:08 ` Ted Zlatanov
2011-02-18 0:24 ` Lars Ingebrigtsen
2011-02-18 2:37 ` Stefan Monnier
2011-02-18 8:19 ` Lars Ingebrigtsen
2011-02-18 10:54 ` Steinar Bang
2011-02-18 20:16 ` Ted Zlatanov
2011-02-18 22:43 ` Stefan Monnier
2011-02-22 21:51 ` Ted Zlatanov
2011-02-18 23:04 ` Lars Ingebrigtsen
2011-02-22 22:46 ` Stefan Monnier
2011-02-16 21:26 ` Lars Magne Ingebrigtsen
[not found] <jwv8vxg7nt4.fsf-monnier+@gnu.org>
[not found] ` <mailman.0.1298509609.2066.bug-gnu-emacs@gnu.org>
2011-02-24 12:50 ` Ted Zlatanov
2011-02-24 15:22 ` Stefan Monnier
2011-02-24 16:29 ` Ted Zlatanov
2011-02-25 4:29 ` Lars Magne Ingebrigtsen
2011-02-25 11:21 ` Ted Zlatanov
2011-02-25 11:50 ` Ted Zlatanov
2011-03-05 12:17 ` Lars Magne Ingebrigtsen
[not found] ` <mailman.17.1299357452.24947.bug-gnu-emacs@gnu.org>
[not found] ` <874o7e23i8.fsf@lifelogs.com>
[not found] ` <mailman.2.1299548219.4111.bug-gnu-emacs@gnu.org>
[not found] ` <87lj0ptv9y.fsf@lifelogs.com>
2011-03-08 19:49 ` Ted Zlatanov
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=874o836dfv.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).