From: Bob Newell <bobnewell@bobnewell.net>
To: info-gnus-english@gnu.org
Subject: nnimap-keepalive
Date: Sun, 28 Mar 2021 08:37:59 -1000 [thread overview]
Message-ID: <874kgvunso.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <87zgyz1qp1.fsf@trigram.no> (Kevin Brubeck Unhammer's message of "Fri, 19 Mar 2021 09:40:58 +0100")
Aloha everyone,
I ran into a problem which apparently has history. I'm
spending a month at my son's house and his internet setup
doesn't do well with persistent IMAP connections. So if I
don't do anything with my IMAP connection for a little while,
and then try something, nnimap hangs (I can point out the
precise spot but I assume this is well known already).
Hence nnimap-keepalive. But that's hardwired to run every 15
minutes and check for lack of activity in the past 5
minutes. You can see the problem already, and in fact I found
an old discussion thread suggesting the keepalive time should
be configurable.
By hacking nnimap.el I changed it to a 1 minute run interval
and a 1 minute idle check, and now there is no problem with
hanging. However being largely ignorant of things gnu and
IMAP, I don't know if there is a dark side to this. Probably
so.
However I'd like to re-suggest configurability for the
keepalive timings (both the run interval and the inactivity
interval). IMAP over gnus is a real pain to use at my son's
house and I suspect elsewhere, when similar conditions
prevail.
Mahalo,
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-03-28 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:40 wash forwarded threads Kevin Brubeck Unhammer
2021-03-28 18:37 ` Bob Newell [this message]
2021-03-29 16:27 ` nnimap-keepalive Eric Abrahamsen
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=874kgvunso.fsf@emailmessageidheader.nil \
--to=bobnewell@bobnewell.net \
--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).