From: Rainer M Krug <Rainer@krugs.de>
To: Rasmus <rasmus@gmx.us>
Cc: help-gnu-emacs@gnu.org
Subject: Re: From Gnus to mu4e
Date: Fri, 28 Aug 2015 12:41:05 +0200 [thread overview]
Message-ID: <m2y4gvn1a6.fsf@krugs.de> (raw)
In-Reply-To: <87si7367yt.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 28 Aug 2015 12:08:42 +0200")
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
Rasmus <rasmus@gmx.us> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Yes - offlineimap is running permanently, but ony checks in specific
>> intervalls - the rest of the time it is idling, but can, if told so,
>> keep the connection open (and this is what I do in my config).
>
> This is incorrect.
>
> In email technology, IDLE is an IMAP feature described in RFC 2177
> that allows a client to indicate to the server that it is ready to
> accept real-time notifications. (Wikipedia)
> ^^^^^^^^^^^^^^^^^^^^^^^
Sorry - mixed it up with running offlineimap in daemon mode with
checking periodically, controlled by the "autorefresh" option.
Didn't know about the idlefolders option.
>
> What you are talking about is polling; like a chron job. This is
> inefficient.
Why is it inefficient, and inefficient in regards to local resources,
time, bandwidth? The connections are kept open, and it is just
polling every few minutes. With idlefolders, offlineimap is permanently
listening to the server?
Rainer
>
> Rasmus
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 480 bytes --]
next prev parent reply other threads:[~2015-08-28 10:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:23 From Gnus to mu4e Julien Cubizolles
2015-08-21 10:28 ` Julien Cubizolles
2015-08-21 10:49 ` Colin Yates
2015-08-21 13:06 ` Suvayu Ali
2015-08-26 6:53 ` Julien Cubizolles
2015-08-25 5:49 ` Bastien
2015-08-25 6:28 ` Ian Zimmerman
2015-08-25 6:56 ` Bastien Guerry
2015-08-26 7:22 ` Julien Cubizolles
2015-08-27 12:50 ` Rainer M Krug
2015-08-27 17:15 ` Bastien
2015-08-28 8:39 ` Rainer M Krug
2015-08-28 8:44 ` Bastien
2015-08-28 8:51 ` Rainer M Krug
2015-08-28 8:58 ` Rasmus
2015-08-28 9:15 ` Julien Cubizolles
2015-08-28 10:03 ` Rainer M Krug
2015-08-28 10:08 ` Rasmus
2015-08-28 10:41 ` Rainer M Krug [this message]
2015-08-28 10:04 ` Rasmus
2015-08-28 8:51 ` Bastien
2015-08-27 21:27 ` Julien Cubizolles
2015-08-27 23:34 ` Suvayu Ali
2015-08-27 23:50 ` Ian Zimmerman
2015-08-28 0:14 ` Suvayu Ali
2015-08-28 0:24 ` Ian Zimmerman
2015-08-28 8:25 ` Rainer M Krug
2015-08-28 9:06 ` Suvayu Ali
2015-08-28 15:31 ` Ian Zimmerman
2015-08-31 0:16 ` Suvayu Ali
2015-08-28 8:21 ` Rainer M Krug
2015-08-27 12:58 ` Suvayu Ali
2015-08-27 15:52 ` Glenn Morris
2015-08-27 17:32 ` Suvayu Ali
2015-08-27 17:11 ` Bastien
2015-08-27 17:08 ` Bastien
2015-08-27 17:30 ` Suvayu Ali
2015-08-27 21:52 ` Julien Cubizolles
2015-08-27 22:18 ` Bastien
2015-08-27 23:30 ` Julien Cubizolles
[not found] <mailman.14.1440105837.31004.help-gnu-emacs@gnu.org>
2015-08-24 11:19 ` Joost Kremers
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=m2y4gvn1a6.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=help-gnu-emacs@gnu.org \
--cc=rasmus@gmx.us \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.