GNOME Bugzilla – Bug 312433
Move to Folder using Filters actually copies in offline
Last modified: 2012-02-02 14:38:26 UTC
Steps to reproduce: 1.Create a filter which will move the filtered mails to a local mail folder 2.Switch to offline and select "Inbox" 3.Select all mails and apply filters, filtered mails will be moved to the destination folder. This is fine till now. 4.Now switch to online and restart evolution Observe that the filtered mails are still present in "Inbox".
This is happening with the devel snaps, evolution-exchange-2.3.6.0.200507270301-0.snap.novell.11.1 evolution-data-server-1.3.6.0.200507270301-0.snap.novell.11.1 evolution-2.3.6.0.200507270301-0.snap.novell.11.1
This should be fixed now.
This is still reproducible with the devel snaps dated, 31st Aug 2005.
Exchange doesnot sync with the server on moving from offline to online. This is why the changes are not reflected. A similar behaviour has been seen when I try to delete a few mails from a folder marked for offline operation. Since the folder is marked for offline operation, the mails that are deleted should not be reflected once we restart evolution in online mode . But the behaviour seen, is quite contrary to this expectation.
move , delete , mark as read , dont sync up... but some flags like important and follow up do sync up while moving from offline to online
Bumping version to a stable release.
Sorry that this report has not received attention earlier. Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages. This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) AND with either evolution-mapi or evolution-ews? Thanks in advance!
Closing this bug report as no updated information has been provided. Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment. Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.