From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Unpleasant catch 22
Date: Thu, 24 Sep 2020 17:27:06 -0400 [thread overview]
Message-ID: <871riquaqd.fsf@local.lan> (raw)
In-Reply-To: <87pn6bg6fk.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
[...]
First let me say that problem is fixed by finally getting a working
password in place for news.forteinc. So once again I'm able to enter a
gnus interface on startup.
For future reference, one thing I'm curious about... is there a way to
tell gnus NOT to scan for news/mail on startup. At least then in the
event of some kind of server snafu at least one could start gnus and
take care of server problems.
>> You didn't mention if `gnus-no-server' is expected to scan for
>> mail/news and if so, what is the point since no servers are supposed
>> to be engaged.
>
[...]
> So far as I can tell, calling `gnus-no-server' skips the initial
> connection to `gnus-start-news-server' (which only starts
> `gnus-select-method'), but then later on connects to it anyway, during
> `gnus-get-unread-articles'. Essentially, `gnus-no-server' seems to be
> functionally equivalent to starting Gnus normally, but only activating
> groups at levels 1 and 2.
Thanks; so not much use apparently.
[...]
> 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.
> . . . . . . . . . . . . . . . . . . . . . .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.
next prev parent reply other threads:[~2020-09-24 21:28 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 [this message]
2020-09-25 1:26 ` Eric Abrahamsen
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=871riquaqd.fsf@local.lan \
--to=reader@newsguy.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).