Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Unpleasant catch 22
Date: Thu, 24 Sep 2020 18:26:43 -0700	[thread overview]
Message-ID: <877dsibq98.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871riquaqd.fsf@local.lan>

Harry Putnam <reader@newsguy.com> writes:

[...]

> Thanks; so not much use apparently.

Not much, I think it's weird.

>> This is separate from the fact that authentication failure of any server
>> shouldn't hang the whole startup process.
>
> No need to keep on in this vain as it is fixed in fortinc server.

Fixed for you, but not for the next user who runs into it!

>>......................Is the bum authentication
>> information for this server stored in ~/.authinfo{.gpg}? If it is, and
>> you delete the corresponding line, does Gnus prompt you anew for a
>> password to use?
>
> Egad I wish I'd have thought of that. I was mucking around with
>.authinfo trying different passwd etc... and still never cottoned to
> that simple fix.
>
> Although given the way gnus was resonded to bad authinfo, I suspect
> using the `prompted for' passwd and having a wrong passwd entered might
> still have stopped the music.

Possibly so, so we're back to fixing the underlying issue. Anyway, I'll
poke at it and try to figure out what's going on.



      reply	other threads:[~2020-09-25  1:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 23:03 Harry
2020-09-23 23:10 ` Eric Abrahamsen
2020-09-24  0:36   ` Harry
2020-09-24  1:01     ` 黃炳熙
2020-09-24  4:11     ` Eric Abrahamsen
2020-09-24  4:32       ` Eric Abrahamsen
2020-09-24 21:27       ` Harry Putnam
2020-09-25  1:26         ` Eric Abrahamsen [this message]

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=877dsibq98.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).