Received: by ATHENA-PO-2.MIT.EDU (5.45/4.7) id AA28252; Wed, 22 Mar 89 18:00:54 EST
From: <maya@ATHENA.MIT.EDU>
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA05662; Wed, 22 Mar 89 18:01:30 EST
Received: by BRIDGETOWN.MIT.EDU (5.45/4.7) id AA15745; Wed, 22 Mar 89 18:00:27 EST
Message-Id: <8903222300.AA15745@BRIDGETOWN.MIT.EDU>
To: <bgardner@ATHENA.MIT.EDU>
Subject: Re: Meaning of move-to 
In-Reply-To: Your message of Wed, 22 Mar 89 14:02:20 -0500.
             <8903221902.AA15068@PINK.MIT.EDU> 
Date: Wed, 22 Mar 89 18:00:24 EST

I am still having trouble with this, although your proposal may
be a reasonable compromise for now.  It would take care of th
quota problem, at least.

If what is going to happen is to move a message, then copy a message to
a second folder, why don't we force the user to make a rule that says
*copy* the message to a second folder?  Otherwise, we aren't making a 
distinction between move and copy.  Sometimes move really moves, sometimes
move actually copies.  

Is there something called "move" in rmail?  If so, what does it do exactly?
If not, what are the actions called that do move-like, copy-like, and
delete-like things in rmail?  Although I understand we want to be independent
of any mail system, perhaps we should start with the available paradigms
in our development environment.  I don't know enough about rmail to know
what the other possibilities are that you're thinking about though.
   --- Maya
