MBOX-Line: From ptao at apple.com  Wed Sep  9 12:01:51 2020
To: imap-protocol@u.washington.edu
From: Phillip Tao <ptao@apple.com>
Date: Wed Sep  9 12:02:13 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: <9E1B3336-9D01-4B3C-A86E-6532A4EB8190@apple.com>



> On Sep 9, 2020, at 1:49 AM, Gary R. Schmidt <grschmidt@acm.org> 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."

For the latter two examples, a copy to another account would almost certainly be an APPEND, and not actually a COPY.

But, I can't imagine that you wouldn't break someone's workflow almost immediately if you implemented this "COPY as alias for MOVE" behavior.

- Phillip
> 
> 	Cheers,
> 		Gary	B-)
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol

