Even on many OS's move copies the file, make sure that it is a good
copy, and then deletes the original. MOVE still wouldn't handle this
case because there still needs to be 2 copies at a given point in time
to handle fault tolerance.
Just a thought,
B
I dont see that behavior on my
What exactly would dictate a move?
Even on many OS's move copies the file, make sure that it is a good
copy, and then deletes the original. MOVE still wouldn't handle this
case because there still needs to be 2 copies at a given point in time
to handle fault tolerance.
Just a thought,
B
On Wed, Jul 06, 2005 at 12:48:30PM -0400, Robert Scussel wrote:
Gregg Berkholtz wrote:
On Fri, Jul 01, 2005 at 02:00:03PM -0500, John Madden wrote:
Because IMAP doesn't provide a move operation for messages. Your
client is probably first doing an append of the message to the
destination
On Fri, Jul 01, 2005 at 02:00:03PM -0500, John Madden wrote:
Because IMAP doesn't provide a move operation for messages. Your
client is probably first doing an append of the message to the
destination folder (which is what's putting it over quota) then storing
the delete flag of the
Hi everybody again,
As Ken helped me with my feature request for the quota behavior of cyrus-imapd
i now have one more question i don't understand.
If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to move
one message with 1 MB from one folder to another, cyrus gives me an
Christian Anton wrote:
Hi everybody again,
As Ken helped me with my feature request for the quota behavior of
cyrus-imapd
i now have one more question i don't understand.
If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to move
one message with 1 MB from one folder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to
move one message with 1 MB from one folder to another, cyrus gives me an
error message that says i'm over quota. Why does moving a message need
space in the mailbox, i don't
Because IMAP doesn't provide a move operation for messages. Your
client is probably first doing an append of the message to the
destination folder (which is what's putting it over quota) then storing
the delete flag of the original message and expunging.
I'm sure we've all had problems with
John Madden wrote:
Because IMAP doesn't provide a move operation for messages. Your
client is probably first doing an append of the message to the
destination folder (which is what's putting it over quota) then storing
the delete flag of the original message and expunging.
I'm sure we've all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it wise to modify these clients to instead FETCH, delete/expunge, then
STORE?
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough quota
that the STORE would
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough quota
that the STORE would put it over quota? What do you do with the message?
4th and 15. Punt.
That's certainly a tough situation. So what *is* the
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough
quota
that the STORE would put it over quota? What do you do with the message?
4th and 15. Punt.
That's certainly a tough situation. So what *is*
Lars Kristiansen wrote:
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough
quota
that the STORE would put it over quota? What do you do with the message?
4th and 15. Punt.
That's certainly a tough
13 matches
Mail list logo
