GNOME Bugzilla – Bug 257641
Exchange account Mails marked as junk are not storing in junk folder
Last modified: 2013-07-23 14:34:08 UTC
Description of Problem: When I marked my exchange account mails as junk they are not moving to junk folder. Steps to reproduce the problem: 1. Go to exchange view. 2. Select any message from any folder other than junk-folder. 3. Mark them as junk mail. Mail will get disappeared. Actual Results: But they wont be there in the junk folder. Expected Results: They should be stored in the junk folder. How often does this happen? Everytime Additional Information: This is working fine with other accounts. The mails got deleted after marking as junk-mails from exchange account from the respected folder are not going to store anywhere.
fixed
I checked with the latest build dated 22-june-2004. This is still not working. I am reopening the bug
Fixed again... the "junk" flag was not being preserved between sessions, but now it is.
Mails which are marked as junk are disappearing again. It seems that this feature is broken in devel sanps dated, evolution-2.3.4.0.200507021459-0.snap.novell.11.1 evolution-exchange-2.3.4.0.200507021459-0.snap.novell.11.1 Reopening the bug.
Marking this as "Major" due to the shown behavior.
Its better to have a proper plugin handle these for Exchange junk mails now.
We need to have Exchange specific Junk flags. When the user clicks on junk-button, the mails should be moved to Junk folder overrirding the defauklt action. See groupwise-features for a sample implementation. The custom exchange flag should be set for all mails in the exchange junk folder.
Created attachment 65226 [details] [review] Fix
Can we do something better to check if the message in a folder is marked for junk? A store level has table and a flag? Every time (even if none of the message is marked for junk) checking all the messages in a folder for junk flag, might cause a delay in folder swtiching, that too with the huge accounts (with lakhs of mails) which we can see in other mailer performance related bugs.
This is still broken for me. Using 2.6.3 on FC5.
The attached patch will solve your problem. However we could not profile if there could be any performance delays due to the patch. So it did not went in. However, as a workaround, if you want to get your mails back, what you can do is: rm -rf ~/.evolution/mail/exchange/<account>/folders/<folder-name> If you delete the cache corresponding to the folder in which you have marked the message as junk, you will get the mails back, next time when Evolution launches.
(In reply to comment #9) > Can we do something better to check if the message in a folder > is marked for junk? A store level has table and a flag? > > Every time (even if none of the message is marked for junk) > checking all the messages in a folder for junk flag, might > cause a delay in folder swtiching, that too with the > huge accounts (with lakhs of mails) which we can see in other > mailer performance related bugs. > > We cant do them with our current infrastructure. All the providers (GW and IMAP) do it in this way only. Anyway, we can measure if there is any performance delay due to this patch and take it in based on the test.
Bumping version to a stable release.
*** Bug 536755 has been marked as a duplicate of this bug. ***
*** Bug 558496 has been marked as a duplicate of this bug. ***
*** Bug 353715 has been marked as a duplicate of this bug. ***
look for more information at bug 353715
*** Bug 604045 has been marked as a duplicate of this bug. ***
Created attachment 158101 [details] [review] interim evo patch for evolution; This is an interim solution for evolution, to not hide junk emails in folders where their store doesn't support vJunk folder. In that case the junk mail should be either placed in a real junk folder or not having the flag set. But because there can be mails with the junk flag set, and they would be otherwise hidden for a user, then this allows to show them. Created commit 6bf1024 in evo master (2.31.1+) Created commit fc627d1 in evo gnome-2-30 (2.30.1+)
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.