Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: DekuDekuplex@Yahoo.com (Benjamin L. Russell)
To: info-gnus-english@gnu.org
Subject: Re: IMAP- Gmail mark sent as read
Date: Thu, 19 May 2011 19:01:18 +0900	[thread overview]
Message-ID: <8262p7j9g1.fsf@Yahoo.com> (raw)
In-Reply-To: <m2hbe3q6md.fsf@verilab.com>

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 list exactly matches my own list displayed in Gnus upon entering
M-x gnus-group-describe-all-groups RET.  This issue seems to be a
server-side configuration bug.

Thank you for your responses; they have been very helpful.  Now I know
that the issue doesn't seem be be related with a configuration bug in my
~/.gnus.el file.  For the next step, I'll try to find a way to get in
touch with the news.gnus.org server maintainers to advise them of their
server configuration bug.

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^

      reply	other threads:[~2011-05-19 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 16:05 Richard Riley
2010-12-24 18:48 ` Sivaram Neelakantan
     [not found] ` <mailman.11.1293216528.7272.info-gnus-english@gnu.org>
2010-12-24 19:39   ` Richard Riley
2010-12-24 20:05     ` Tommy Kelly
2011-05-19 10:01       ` Benjamin L. Russell [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=8262p7j9g1.fsf@Yahoo.com \
    --to=dekudekuplex@yahoo.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).