From: Richard G Riley <rileyrgdev@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: IMAP closing connection after inactivity
Date: Thu, 31 Jan 2008 18:32:45 +0100 [thread overview]
Message-ID: <60ef22F1pq2j3U1@mid.uni-berlin.de> (raw)
In-Reply-To: <60bi33F1qaegrU1@mid.uni-berlin.de>
Richard G Riley <rileyrgdev@gmail.com> writes:
> I have the same problem as the article I link and reproduce below. Is
> there a way to get Gnus to keep an IMAP session open without using a
> daemon to check for all new messages regularly?
>
> http://osdir.com/ml/emacs.gnus.user/2006-02/msg00133.html
>
I received a reply (below) on the Dovecot mailing list. Could anyone here
suggest a Gnus fix?
,----
| [[PGP Signed Part:Timo Sirainen <tss@iki.fi>
| Untrusted, Fingerprint: E643 F0BD FDCD 04D9 FFCB 6279 C948 5251 4055 8AC9]]
| On Thu, 2008-01-31 at 17:51 +0100, Richard G Riley wrote:
| > Could someone suggest what the solution here is? Dovecot is terminating
| > the connection to Gnus after a certain period of activity. It's my own
| > mail server so no need to worry about "hogging resources". Should/could
| > Dovecot be configured to keep the connection alive, or should Gnus be
| > programmed to automatically reopen the conneection? The current problem
| > that one can not leave an IMAP group if the connection is cut by the
| > server.
| ..
| > | "dovecot: 2008-01-31 08:50:38Info: IMAP(gour): Disconnected for
| > | inactivity"
|
| I'd say this is a Gnus bug. If an IMAP client wants the connection to
| stay open, it should send something at least every 29 mins. Most (if not
| all) IMAP servers disconnect connections after 30 minutes of idling.
| This is hardcoded in Dovecot, but you can of course change it:
|
| src/imap/common.h:
| #define CLIENT_IDLE_TIMEOUT (60*30)
|
| [[End of PGP Signed Part]]
`----
next prev parent reply other threads:[~2008-01-31 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 15:06 Richard G Riley
2008-01-31 7:53 ` Gour
2008-01-31 17:32 ` Richard G Riley [this message]
2008-01-31 18:56 ` Gour
2008-01-31 19:27 ` Reiner Steib
2008-01-31 20:33 ` Gour
2008-01-31 21:37 ` Reiner Steib
2008-02-01 6:35 ` Gour
2008-02-01 8:17 ` Gour
2008-02-01 9:42 ` Gour
2008-02-02 5:59 ` Richard G Riley
2008-02-02 7:43 ` Gour
2008-02-04 3:29 ` Richard G Riley
2008-02-04 19:11 ` Gour
2008-02-04 19:18 ` Richard G Riley
2008-02-06 21:15 ` Richard G Riley
2008-02-05 16:44 ` Allen S. Rout
2008-01-31 23:44 ` Richard G Riley
2008-01-31 23:55 ` Richard G Riley
2008-03-03 9:49 ` Gour
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=60ef22F1pq2j3U1@mid.uni-berlin.de \
--to=rileyrgdev@gmail.com \
--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).