From: Peter Davis <pfd@pfdstudio.com>
To: ding@gnus.org
Subject: Re: nnimap backend performances ?
Date: Fri, 01 Jan 2016 19:09:15 -0500 [thread overview]
Message-ID: <m2vb7c266s.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <m0poz4bey2.fsf@kcals.intra.maillard.im> (Xavier Maillard's message of "Fri, 20 Nov 2015 21:20:37 +0100")
Xavier Maillard <lists.emacs.gnus@xavier.maillard.im> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Xavier Maillard <lists.emacs.gnus@xavier.maillard.im> writes:
>>
>>> Hi,
>>>
>>> Currently I am fetching my incoming mails using a fantastic tool:
>>> offlineimap. Mails are then deserved by a local imap server (dovecot) on which
>>> Gnus is connected. So far so good.
>>>
>>> As far as I can remeber, I do this from the age of stone principally because,
>>> nnimap was considered pretty slow and also because I was nomade and it was
>>> comfortable to do this.
>>>
>>> Today, is it considered harmful to fetch my mail in "direct connect" to my
>>> remote imap server ?
>>
>> My understanding is that the nnimap backend was re-written quite
>> significantly two or three years ago (?). At any rate, the people who
>> used the first iteration and were horrified now seem mostly happy with
>> the new version, YMMV. I used to use isync and local dovecot, now use
>> the direct connection, and it doesn't kill me. It isn't great (I'm in
>> China), but it doesn't kill me.
>
> Understand. SO this is definetely something I should test again and
> reconsider.
I never got back to this, but I'm curious. I'm running Gnus 5.13. Does that mean I've got the re-written NNIMAP back end?
Thanks!
-pd
next prev parent reply other threads:[~2016-01-02 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 5:27 Xavier Maillard
2015-11-20 5:51 ` Eric Abrahamsen
2015-11-20 20:20 ` Xavier Maillard
2016-01-02 0:09 ` Peter Davis [this message]
2016-01-02 3:22 ` Eric Abrahamsen
2016-01-02 12:04 ` Peter Davis
2016-01-02 12:20 ` Peter Davis
2016-01-02 13:57 ` Eric Abrahamsen
2015-12-29 19:25 ` myglc2
2015-12-31 6:07 ` Eric Abrahamsen
2016-01-01 3:51 ` myglc2
2016-01-02 3:38 ` Eric Abrahamsen
2016-01-04 0:35 ` myglc2
2016-01-04 1:50 ` 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=m2vb7c266s.fsf@PFDStudio-Air.home \
--to=pfd@pfdstudio.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).