From: Harry Putnam <reader@newsguy.com>
To: info-gnus-english@gnu.org
Subject: Re: Can't access the gnu.* hierarchy using Gnus
Date: Sat, 03 Jun 2017 14:18:45 -0400 [thread overview]
Message-ID: <86lgp9exyy.fsf@local.lan> (raw)
In-Reply-To: <23d9a870-d73b-4b31-bc49-a297339a13dd@googlegroups.com>
Joseph Fineman <joe_f@verizon.net> writes:
> I use Gnus 5.13 to read newsgroups (as well as mail). I have
> recently encountered a frustration with regard to certain
> newsgroups -- in particular, those in the gnu.* hierarchy. I am
> subscribed to them, but they do not show up in the *Group* buffer.
> When I bring them up by hitting L, they all show 0 for the number of
> postings, and when I call them up, they omit all recent postings. In
> particular, gnu.emacs.gnus shows nothing since 24 September 2016, tho
> Google Groups (may its name be blotted out!) reveals a dozen more
> recent postings, the latest on 8 January 2017. Gnus seemed to accept
> a posting by me, but it never appeared, there or on Google Groups.
8 January...Yikes
Using enews.newsguy.com...as a foreign server in gnus, I see your
message of 10:35 today on gnu.emacs.gnus and I see 5 since Jan 8, the
most recent being May 4
Sorry I'm not really helping with your request. But thought you might
like the input about gnu.emacs.gnus.
Also, you might learn something by checking the server buffer with `^'
in group buffer.
But I kind of doubt anything there would make all messages appear as
old.
next prev parent reply other threads:[~2017-06-03 18:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 17:35 Joseph Fineman
2017-06-03 18:18 ` Harry Putnam [this message]
2017-06-12 19:30 ` Mike Small
2017-06-12 23:11 ` Emanuel Berg
2017-06-13 11:24 ` Automatically sort groups into topics John Ankarström
2017-06-13 18:29 ` B.V. Raghav
2017-06-14 1:32 ` Emanuel Berg
2017-06-14 1:29 ` Emanuel Berg
2017-06-14 6:57 ` Adam Sjøgren
2017-06-14 7:04 ` Emanuel Berg
2017-06-14 7:11 ` Adam Sjøgren
2017-06-14 7:30 ` Emanuel Berg
2017-06-14 7:53 ` Adam Sjøgren
2017-06-14 8:14 ` Emanuel Berg
2017-06-14 11:07 ` Adam Sjøgren
2017-06-14 11:30 ` Emanuel Berg
2017-06-14 13:20 ` John Ankarström
2017-06-15 6:40 ` Emanuel Berg
2017-06-15 13:26 ` Emanuel Berg
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=86lgp9exyy.fsf@local.lan \
--to=reader@newsguy.com \
--cc=info-gnus-english@gnu.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).