Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <lmi@gnus.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>, 8050@debbugs.gnu.org
Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more
Date: Wed, 16 Feb 2011 13:26:07 -0800	[thread overview]
Message-ID: <87lj1fr7rk.fsf@gnus.org> (raw)
In-Reply-To: <874o836dfv.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 16 Feb 2011 12:29:08 -0600")

Ted Zlatanov <tzz@lifelogs.com> writes:

> 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).

What's a good test case to tickle the bug?

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

Hm...  if you look at how Firefox deals with this, it asks something
like "save password, don't save now, never save for this host", and I
think that's pretty nice, UX wise.  But there isn't a "never ask me
about saving passwords for any hosts ever again", I think?

> 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.

I'd prefer a longer timeout than 30 minutes as the default.  Perhaps two
hours? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen



  parent reply	other threads:[~2011-02-16 21:26 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
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 [this message]
     [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=87lj1fr7rk.fsf@gnus.org \
    --to=lmi@gnus.org \
    --cc=8050@debbugs.gnu.org \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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).