From: Jody Klymak <jklymak@coas.oregonstate.edu>
Cc: Nicolas Kowalski <Nicolas.Kowalski@imag.fr>, ding <ding@gnus.org>
Subject: Re: nnimap slow for message copy
Date: Fri, 26 Apr 2002 10:50:09 -0700 [thread overview]
Message-ID: <ug01inycu.fsf@coas.oregonstate.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0204261922330.20589-100000@yxa.extundo.com> (Simon Josefsson's message of "Fri, 26 Apr 2002 19:23:46 +0200 (CEST)")
Simon Josefsson <jas@extundo.com> writes:
> The problem is that the Gnus backend interface doesn't use COPY when
> copying something, I think, so it ends up using fetch+store. Of course,
> the nnimap backend could detect this situation and use COPY instead. (As
> it does when moving messages, I think.)
Hi Simon,
Moving is really slow for me too.
Cheers, Jody
--
Jody M. Klymak mailto:jklymak@coas.oregonstate.edu
College of Oceanic and Atmospheric Sciences
Oregon State University, Corvallis, OR, 97331
next prev parent reply other threads:[~2002-04-26 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 13:40 Nicolas Kowalski
2002-04-26 17:23 ` Simon Josefsson
2002-04-26 17:50 ` Jody Klymak [this message]
2002-04-26 18:07 ` Nicolas Kowalski
2002-04-26 22:25 ` Simon Josefsson
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=ug01inycu.fsf@coas.oregonstate.edu \
--to=jklymak@coas.oregonstate.edu \
--cc=Nicolas.Kowalski@imag.fr \
--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).