[Dovecot] Strange behaviour with moving mail
Hi All,
Sorry to bother you again. I am not too familiar with IMAP yet, so maybe I am asking stupid questions. Here goes anyway:
In our (Dovecot 1.0-stable) setup, we have two namespaces: the default namespace, which location is '/var/mailstore/1%u/%u' and the "Mailstorage" namespace, which location is '~/.Mailstorage/'.
Now we create a folder called 'Test' in the default namespace and the "Mailstorage" namespace. As far as I know this is possible and not a strange thing to do.
When moving an email from the first 'Test' folder to the other 'Test' folder, it appears that everything works like expected, but when refreshing the mailbox, the message is still in the original folder. This happens with a number of different mailclients (which are configured with an empty namespace setting).
I guess Dovecot doesn't look at the namespace in which the mail folder is.
Is this a Dovecot bug or is this normal behaviour?
Best regards, Remy
B.T.W: When moving the mail, this is the IMAP conversation: 00029 UID COPY 4 TEST * 2 EXISTS * 2 RECENT 00029 OK Copy completed. 00030 UID STORE 4 +Flags.silent (\Deleted) 00030 OK Store completed.
On Fri, 2005-03-04 at 14:45 +0100, Remy Zandwijk wrote:
When moving an email from the first 'Test' folder to the other 'Test' folder, it appears that everything works like expected, but when refreshing the mailbox, the message is still in the original folder. This happens with a number of different mailclients (which are configured with an empty namespace setting). .. When moving the mail, this is the IMAP conversation: 00029 UID COPY 4 TEST * 2 EXISTS * 2 RECENT 00029 OK Copy completed. 00030 UID STORE 4 +Flags.silent (\Deleted) 00030 OK Store completed.
That's how moving is done with IMAP. Copy + mark as deleted. Dovecot is buggy only if the message isn't left marked as deleted. Expunge would then delete the message entirely.
That's how moving is done with IMAP. Copy + mark as deleted. Dovecot is buggy only if the message isn't left marked as deleted. Expunge would then delete the message entirely.
Timo, I think you don't understand the problem. Let me explain it once more in other words.
I have two namespaces, the default one and another one. In both namespaces, I have made a folder called 'Test'. Let's refer to this folders as:
'Folder A': 'Test' in the default namespace.
'Folder B': 'Test' in the not-default namespace.I have a message in 'Folder B' and I transfer this message to 'Folder A'. The message is marked as deleted in 'Folder B', but 'Folder A' does *not* contain the moved message, even though I refreshed the folder list.
When expunging the message in 'Folder B' it disapears, but after a folder refresh, the message apears again and it's not marked deleted. The message is still not in 'Folder A'.
I think this is incorrect behaviour and therfore a bug.
Regards, Remy
On Sun, 2005-03-06 at 14:46 +0100, Remy Zandwijk wrote:
I have two namespaces, the default one and another one. In both namespaces, I have made a folder called 'Test'. Let's refer to this folders as:
'Folder A': 'Test' in the default namespace. 'Folder B': 'Test' in the not-default namespace.I have a message in 'Folder B' and I transfer this message to 'Folder A'. The message is marked as deleted in 'Folder B', but 'Folder A' does *not* contain the moved message, even though I refreshed the folder list.
When expunging the message in 'Folder B' it disapears, but after a folder refresh, the message apears again and it's not marked deleted. The message is still not in 'Folder A'.
I think this is incorrect behaviour and therfore a bug.
Right. Fixed in upcoming snapshots (cvs and stable).
participants (2)
-
Remy Zandwijk
-
Timo Sirainen