Re: Gnus cannot describe all Quimby (news.gnus.org) groups

[Benjamin L. Russell]

Tassilo Horn <tassilo@member.fsf.org> writes:

> DekuDekuplex@Yahoo.com (Benjamin L. Russell) writes:
>
> Hi Benjamin,
>
>>> It has nothing to do with that being your third nntp server.  I did some
>>> more testing and added news.gnus.org as my fourth nntp server.
>>>
>>> (add-to-list 'gnus-secondary-select-methods
>>>              '(nntp "Quimby"
>>>                     (nntp-address "news.gnus.de")))
>>>
>>> That's the only entry for Quimby, and since there's no group listed and
>>> "Has read" doesn't look like a proper description, it looks like a
>>> server issue to me.
>>
>> You added news.gnus.de, instead of news.gnus.org; are you sure that
>> those two NNTP addresses point to the same server?
>
> Argh, stupid me!  Ok, now I did that with the right address, did M-x
> gnus-group-describe-all-groups RET, and those are all Quimby groups I
> got described:
>
> 11 matches for "Quimby" in buffer: *Group*
>    2026:      *: nntp+Quimby:local.general Local general group
>    2216:      *: nntp+Quimby:control.cancel Cancel messages (no posting)
>    4929:      *: nntp+Quimby:control  Various control messages (no posting)
>    8872:      *: nntp+Quimby:         Has read
>   10485:      *: nntp+Quimby:local.test Local test group
>   10798:      *: nntp+Quimby:.        
>   11634:      *: nntp+Quimby:junk     Unfiled articles (no posting)
>   17588:      *: nntp+Quimby:control.rmgroup Newsgroup removal control 
> messages (no posting)
>   17647:      *: nntp+Quimby:control.newgroup Newsgroup creation control 
> messages (no posting)
>   24293:      *: nntp+Quimby:215      Descriptions in form "group description"
>   27158:      *: nntp+Quimby:control.checkgroups Hierarchy check control 
> messages (no posting)
>
> These are still not all groups, and the nameless group, the group 215,
> and "." don't look correct.  And the description 'Descriptions in form
> "group description"' pretty much looks like a parsing issue.

Your listing exactly matches mine.  This issue seems to be a server-side
configuration bug.

Thank you for all your assistance; now I know that this issue is likely
not caused by a configuration bug in my ~/.gnus.el file.  Next, I'll try
to get in touch with the new.gnus.org maintainers to advise them that
they seem to have a bug in their server configuration.

Cheers,

Benjamin L. Russell
-- 
Benjamin L. Russell  /   DekuDekuplex at Yahoo dot com
http://dekudekuplex.wordpress.com/
Translator/Interpreter / Mobile:  +011 81 90-6526-1406
"Furuike ya, kawazu tobikomu mizu no oto." -- Matsuo Basho^