wasm-demo/demo/ermis-f/imap-protocol/cur/1600095011.22589.mbox:2,S

32 lines
1.3 KiB
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Tue May 26 10:07:15 2015
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun 8 12:34:55 2018
Subject: [Imap-protocol] COPYUID message order
In-Reply-To: <55641351.8030608@ymail.com>
References: <555FBFD2.1030800@ymail.com>
<CABa8R6tpd-2GPoSTX0_d8wnROvQpm4_zmMxconJDPPud3NNdww@mail.gmail.com>
<555FD141.1060300@ymail.com>
<B992E8DF-EF7F-4C29-9869-41C8B4728D2D@isode.com>
<CABa8R6s6FQaj6tJRfkiZp+U1ybUeKsOYNb96BrFyiP4=WGavUA@mail.gmail.com>
<55641351.8030608@ymail.com>
Message-ID: <23e30726-1ae2-46da-abba-e50cdf1d3359@gulbrandsen.priv.no>
Bill Shannon writes:
> I'd like to be able to report the status of each message that
> was requested to be copied. If one of the messages was not
> copied for some reason, and so is left out of the returned list
> of source UIDs, how do I figure out which one that was? Without
> a complete map from sequence number to UID, it seems that the
> COPYUID response code for the simple COPY command may not be
> sufficient.
True. For that case you'll need to issue "FETCH ... UID" and then "COPY ...
target" (without waiting). When you have received tagged responses for
both, you know that your MSN-UID map is contains all the necessary UIDs and
you can process the COPYUID response code completely.
Arnt