31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
MBOX-Line: From dpc22 at cam.ac.uk Wed Sep 9 02:30:35 2020
|
|
To: imap-protocol@u.washington.edu
|
|
From: David Carter <dpc22@cam.ac.uk>
|
|
Date: Wed Sep 9 02:31:09 2020
|
|
Subject: [Imap-protocol] Any valid use case for COPY besides moving
|
|
messages?
|
|
In-Reply-To: <cf5ca346-0ff8-831d-7dc4-4027803f6e82@acm.org>
|
|
References: <CAPacwgy_1WJd5TLRDbykTnzfwv9hgcTLzBQZte5=bMRK-RUFLQ@mail.gmail.com>
|
|
<cf5ca346-0ff8-831d-7dc4-4027803f6e82@acm.org>
|
|
Message-ID: <5109ccf6cec7384b014f594e29e6d3f9@cam.ac.uk>
|
|
|
|
On 2020-09-09 09:49, Gary R. Schmidt wrote:
|
|
> On 09/09/2020 17:27, Andris Reinman wrote:
|
|
>> Hi,
|
|
>>
|
|
>> As the subject states, is there actually any valid use case these days
|
|
>> for COPY to just copy messages instead of being a poor substitute for
|
|
>> MOVE (that is COPY+EXPUNGE)?
|
|
>>
|
|
> I often copy bunches of email to other folders, to other users
|
|
> accounts, and to various archive accounts, after which the messages
|
|
> are *not* deleted, so I would say, "Yes, there are valid use cases for
|
|
> COPY doing *exactly* what the word says."
|
|
|
|
I frequently COPY mail which has been filtered into a folder on delivery
|
|
back to my inbox if there is something odd that I need to investigate
|
|
and/or action.
|
|
|
|
Roundcube has "drag and drop" for MOVE, and Shift+"drag and drop" for
|
|
COPY, which is quite convenient of it.
|