From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: slow nnimap moves due do many SELECTs
Date: Wed, 22 Sep 2010 13:52:15 -0400 [thread overview]
Message-ID: <87k4mdmzsg.fsf@maru.md5i.com> (raw)
In-Reply-To: <m3zkv9d7f9.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 22 Sep 2010 19:17:30 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <md5i@md5i.com> writes:
>
>> You may not need to copy over the marks. The spec says: "The flags and
>> internal date of the message(s) SHOULD be preserved, and the Recent flag
>> SHOULD be set, in the copy." If the SHOULD is bothersome, it would be
>> nice to have a per-server variable we can set if we know that that
>> server handles this correctly.
>
> Gnus copies over marks on articles on `B m' if the backend supports it.
> IMAP does, so Gnus does.
I think I may have not provided enough context, or I have misunderstood
your response. The above applies to the IMAP COPY command, which SHOULD
preserve marks. Which would mean that Gnus may not have to do this
manually. Which would mean that it does not need the ID of the copied
message in the destination folder.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2010-09-22 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 14:19 Ted Zlatanov
2010-09-22 16:53 ` Lars Magne Ingebrigtsen
2010-09-22 17:09 ` Michael Welsh Duggan
2010-09-22 17:17 ` Lars Magne Ingebrigtsen
2010-09-22 17:52 ` Michael Welsh Duggan [this message]
2010-09-22 17:57 ` Lars Magne Ingebrigtsen
2010-09-28 13:30 ` Ted Zlatanov
2010-09-29 21:46 ` Lars Magne Ingebrigtsen
2010-09-30 15:50 ` Ted Zlatanov
2010-09-30 16:35 ` Lars Magne Ingebrigtsen
2010-09-30 16:43 ` Lars Magne Ingebrigtsen
2010-09-30 18:11 ` Ted Zlatanov
2010-09-30 18:16 ` Lars Magne Ingebrigtsen
2010-09-30 16:54 ` Ted Zlatanov
2010-09-30 17:02 ` Lars Magne Ingebrigtsen
2010-09-30 15:22 ` Austin F. Frank
2010-09-22 17:25 ` Ted Zlatanov
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=87k4mdmzsg.fsf@maru.md5i.com \
--to=md5i@md5i.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).