Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Novak <novak@ucolick.org>
Subject: nnimap slow checking for new mail?
Date: Fri, 4 Nov 2005 08:35:03 -0800	[thread overview]
Message-ID: <17259.36279.550049.682864@localhost.localdomain> (raw)

I am having the same problem regarding sluggish checks for new mail
detailed in this thread in May 2005:

http://groups.google.com/group/gnus.ding/browse_thread/thread/3446e973d47f26cc/365a82d99261013c

I saw very nice threads about this circa 2000, but tryiing the
suggested fixes didn't work for me, and I'm wondering if the situation
has changed since then.

Possibly releveant information:
I'm on OSX 10.4.2, Emacs from CVS version listed as 22.0.50.1,
compiled on Sept 29,  Gnus version 5.11.

The relevant bit of my .gnus file:
(setq gnus-secondary-select-methods 
      '((nnimap "fm" (nnimap-address "fastmail.fm"))))

I created my IMAP groups using gnus-browse-foreign-server, and "G e"
on the imap groups yields:

(nnimap "fm")

When I hit g in the group buffer to check for new mail, Gnus checks
each imap group, reporting "Updating blah blah ... done" in the
Messages buffer, with each group taking about a second or two.
Needless to say, this time adds up because there are many folders.  Of
course, mail is only ever delivered to one of them and then split by
Gnus into one group per mailing list.  Does this mean I can turn off
new mail checking for all but the INBOX IMAP folder?

I treid replacing '(nnimap "fm")' with '"nnimap:fm"' per instructions I
found in this mailing list crica 2000, but it made no difference.
Supposedly this was supposed to result in messages from Gnus that
looked like "Checking blah blah" instead of" Updating", but that
didn't work for me.

Thanks for any guidance,
Greg



             reply	other threads:[~2005-11-04 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 16:35 Greg Novak [this message]
2005-11-08 13:19 ` Gregory Novak
2005-11-09 16:32   ` Simon Josefsson

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=17259.36279.550049.682864@localhost.localdomain \
    --to=novak@ucolick.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).