From: Dave Abrahams <dave@boostpro.com>
To: ding <ding@gnus.org>
Subject: Faster/solider GMail connection?
Date: Fri, 30 Sep 2016 11:32:47 -0700 [thread overview]
Message-ID: <m2ponltf00.fsf@boostpro.com> (raw)
Recently `G' in my *Group* buffer now takes a long time and sometimes
appears to truly hang here:
Debugger entered: ("Quit")
nnimap-wait-for-response(167)
nnimap-request-list("imap.gmail.com")
gnus-request-list((nnimap "imap.gmail.com" (nnimap-server-port 993) (nnimap-stream ssl)))
gnus-read-active-file-1((nnimap "imap.gmail.com" (nnimap-server-port 993) (nnimap-stream ssl)) nil)
gnus-get-unread-articles(7 nil nil)
gnus-group-get-new-news(nil)
funcall-interactively(gnus-group-get-new-news nil)
call-interactively(gnus-group-get-new-news nil nil)
command-execute(gnus-group-get-new-news)
I am now using GMail to store gnus-cloud data whereas all my other mail
is going through my local dovecot instance (which I sync with GMail and
another server in the background), but it still seems like it should be
more reliable and speedier than this to connection. Is there some trick
I'm missing?
Thanks,
--
-Dave
next reply other threads:[~2016-09-30 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 18:32 Dave Abrahams [this message]
[not found] <9862d9052dcf456991f95fab37762087@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-01 12:52 ` Eric S Fraga
2016-10-02 19:11 ` Dave Abrahams
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=m2ponltf00.fsf@boostpro.com \
--to=dave@boostpro.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).