A.L.E.C wrote: > Vladislav Bogdanov wrote: > >> * (if not an immediate delete) copy messages to another folder >> * mark original messages with \Deleted flag >> * Expunge them >> >> This is not an atomic operation, and if one polls folder state between >> second and third operations are run, (s)he will get list with messages >> marked for deletion too. And, original messages will be shown in a >> source folder if this happen between first and second operations. IMAP >> logs show following: > > [cut] > >> Do anybody knows, how to avoid such asynchronous behavior when doing >> non-atomic IMAP operations? > > We should just disable 'list' action on folder from which messages are > deleted/moved until we receive a response from 'move_del' action. We > should also add an operation progress indicator. >
So simple solution, cool... Can I hope that you or someone else with enough code knowledge will supply a quick patch for that, so I can concentrate on a next revision of threaded-view-mode patch, (upcoming and almost ready, but depends on a threaded-view because touches same code fragments) spam-column patch and promised enhancements to JohnDoe's sauserprefs plugin? Cheers, Vladislav _______________________________________________ List info: http://lists.roundcube.net/dev/
