IMAP Clients see duplicate emails after webclient moves email item!

[lukedouglass]

Hello Zimbra fans and devs.

After years of being a zimbra webmail master, I have a small task that is IMAP heavy. Note the server spec is not in question here.


Found a very annoying quirk with IMAP clients connecting to zimbra 8.8.12...

1 If you start with a fresh mailbox, only use IMAP to access the content, no issues.

2 If you start with a fresh mailbox, only use IMAP to access the content, move a single example item around in imap client from folder to folder (inbox > test-folder1 > test-folder2 > back to inbox), no issues then either.

3 Continuing on with the same IMAP client view, confirming IMAP client example item movement test works, go to webclient after and do the exact same test in webclient, (inbox > test-folder1 > test-folder2 > back to inbox) thunderbird and apple mail IMAP clients start seeing the same item remain (visually) in all folders that the test item was placed in! (3 movements = 3 look-a-like copies of the same email test)

Testing has shown that once you delete the email item has been used in testing movements within webclient, all imap clients show the multiple view copy are removed successfully as well as the original being deleted - only via webclient deleted items empty action - If you delete the same item via IMAP client after webclient actions as example above, the IMAP client sees the same email re-appear in any location it was seen in!


I tested this on a new server and two existing servers, all updated 8.8.12.1562740562.p4-1.u16 - no issues with IMAP clients if only IMAP client used. - even tried skipping the reverse proxy imap ports, ie direct 7993 IMAPS and same result, its like the webmail client cannot tell the IMAP service things have changed correctly?!

Thoughts on this IMAP client only email view disaster when using webclient? (dont just say "use webmail", personally I do and is the best flexible way to use a mail service!)


Thanks in advance.

[andrey.ivanov]

You should create a ticket if you have Zimbra support, looks like a real bug.