Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: server access when quitting a group?
Date: Tue, 29 Mar 2011 09:45:00 -0500	[thread overview]
Message-ID: <87y63ygf4j.fsf@lifelogs.com> (raw)
In-Reply-To: <ehvcz2gyq5.fsf@news.eternal-september.org>

On Tue, 29 Mar 2011 09:41:38 +0200 Richard Riley <rileyrg@googlemail.com> wrote: 

RR> I just noticed here (very bad wireless) when messing around with agent
RR> etc, that when I quit a group Gnus started doing an nnimap read. Why
RR> would that be? Normally I wouldnt notice it as its all instantaneous at
RR> home but here the wireless broke down while I was reading from the
RR> summary. When I hit q to return to the group buffer my gnus hung doing a
RR> starttls attempt to my (gmail) imap servers which are not agentised. Why
RR> would that be?

Your marks are saved to the IMAP server when you exit the group.  That's
very likely to be the reason for the network activity.

Ted




      reply	other threads:[~2011-03-29 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  7:41 Richard Riley
2011-03-29 14:45 ` Ted Zlatanov [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=87y63ygf4j.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).