Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: nnfolder change?
Date: Wed, 22 Sep 2010 13:55:22 -0400	[thread overview]
Message-ID: <87hbhhpss5.fsf@uwo.ca> (raw)
In-Reply-To: <m3mxr9kag0.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> I also still get lots of nnfolder groups creating buffers that stick
>> around.  And I also get a lot of nnimap buffers for a remote imap
>> server that I don't actually use much:
>>
>>   * *nnimap jdc.math.uwo.: 161  Fundamental
>>   * *nnimap jdc.math.u:<2> 256  Fundamental
>>   * *nnimap jdc.math.u:<3> 256  Fundamental
>>   * *nnimap jdc.math.u:<4> 256  Fundamental
>>   * *nnimap jdc.math.u:<5> 256  Fundamental
>
> This again points to the thing I thought was wrong.
>
> Could you, too, do a
>
> (gnus-find-method-for-group "nnimap+that.server:a.few.groups")
>
> on a few group names and post the output?

I tried on about 8 of the 12 groups, and every one had the following:

  (nnimap "jdc" (nnimap-address "jdc.math.uwo.ca") (nnimap-stream shell))

Some more information:  all of the groups on that server are at level 5,
so they are not activated by default.  And most of the buffers contain
just the following:

-----
* CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1.
3290 OK Capability completed..
Read from remote host jdc.math.uwo.ca: Connection reset by peer.

Process *nnimap*<1> exited abnormally with code 255
-----

Some of them contain:

-----
* SEARCH 6271 6272 6273 6274 6276 6277 6278 6279 6285.
3447 OK Search completed (0.000 secs)..
* BYE Disconnected for inactivity..

Process *nnimap*<1> finished
-----

So maybe this has something to do with having a server with no groups
below the current active level?  The same is true for many of my
nnfolder groups.

Dan




  reply	other threads:[~2010-09-22 17:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 14:44 Stephen Berman
2010-09-20 15:08 ` Dan Christensen
2010-09-20 17:58   ` Stephen Berman
2010-09-21 16:13 ` Lars Magne Ingebrigtsen
2010-09-21 18:50   ` Stephen Berman
2010-09-21 21:11     ` Lars Magne Ingebrigtsen
2010-09-22  8:16       ` Stephen Berman
2010-09-22 12:12         ` Dan Christensen
2010-09-22 16:30           ` Lars Magne Ingebrigtsen
2010-09-22 17:55             ` Dan Christensen [this message]
2010-09-22 19:26               ` Lars Magne Ingebrigtsen
2010-09-22 19:41                 ` Dan Christensen
2010-09-22 16:29         ` Lars Magne Ingebrigtsen
2010-09-22 18:52           ` Stephen Berman
2010-09-22 19:27             ` Lars Magne Ingebrigtsen
2010-09-22 19:32               ` Dan Christensen
2010-09-22 19:39                 ` Lars Magne Ingebrigtsen
2010-09-22 19:45                   ` Lars Magne Ingebrigtsen
2010-09-22 20:39                     ` Dan Christensen
2010-09-22 22:27                 ` Stephen Berman
2010-09-22 22:33                   ` Lars Magne Ingebrigtsen
2010-09-23  8:24                     ` Stephen Berman
2010-09-23 16:39                       ` Lars Magne Ingebrigtsen

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=87hbhhpss5.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --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).