GNOME Bugzilla – Bug 317276
Can't clear followup flags
Last modified: 2013-07-23 14:31:09 UTC
Distribution: Gentoo Base System version 1.12.0_pre8 Package: Evolution Severity: normal Version: GNOME2.10.2 unspecified Gnome-Distributor: Gentoo Synopsis: Can't clear followup flags Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified Description: Description of Problem: Can not clear the Followup Flag from a mail message. I am using Exchange connector to get my mail. Steps to reproduce the problem: 1. Right click on a mail message that has the followup flag set and select "Clear Flag" 2. Flag is cleared 3. Return to mail later and followup is set again Actual Results: Return to mail later and followup is set again Expected Results: Flag should remain cleared How often does this happen? Every time Additional Information: ------- Bug moved to this database by unknown@gnome.bugs 2005-09-26 20:36 UTC -------
Hi john. Thanks for the bug report. But this seems to be working fine for me. I am using Evolution 2.4. What version of evolution are you using?? Thanks
I am using 2.4 as well. Every time I clear a followup flag it goes away, but then I go back to the message later and the flag is back. I'm not sure if it is relevant but I am using MS Exchage to store mail on the server.
perhaps. The issue can indeed be with the Exchange Connector. I used IMAP/POP to test it. And it seems to be working fine. Re-assigning to the Connector component. Thanks.
Has anyone had a chance to look into this? No matter what I do, the flag goes away when I select Clear Flag from the menu, but when I leave the folder and go back, the flag is still there. This happens from vFolders as well as normal folders. And yes, this is with the exchange mail backend.
Try this: 1) Mark a mail as flagged (from Evolution or OWA) 2) Observe that in outlook also the message gets flagged (maybe after a little delay) 3) Now Clear-Flag using Outlook. 4) Clear your Evolution's cache (~/.evolution/exchange) and browser's cache so that all messages will be fetched afresh from the server. 5) View the message in Evolution or OWA. Both of them will show the message as Flagged. In OWA, you have to open the message to see that it is flagged. It may not be visible in the messages-list-view. So a bug in the webDAV interface (which Evo and OWA uses) could be causing this problem. The trouble is not with the unflag code in Evolution but most likely in the server's interface. You can start evolution-exchange process in a terminal, set E2K_DEBUG=4 and see that the server returns the unflagged message as flagged. There is nothing that we can do for this bug in this release. So retargetting to future and removing from the tracker bug. P.S: I have used Microsoft(R) Office(R) Outlook 2003, Evolution 2.5.91 and Microsoft(R) Exchange-server 2003 for the above analysis.
Looks like there is nothing that we can do in Evolution to resolve this. Hence closing the bug.
I did some troubleshooting on this before I came across this bug and here is the debug from the "clear flag" function in evolution. I performed the following test above from Sankar. 1. Set Follow-up flag via OWA 2. Send/Receive with evolution (see the email is flagged in evolution and OWA) 3. Clear cache (also Internet Options -> TIF -> Settings -> "Check for newer version of stored pages = Every vist to the page 4. Close IE 5. Clear 'Follow-up' with Evolution 6. Log in to OWA, see follow-up flag is still there 7. Clear flag in OWA (Right Click -> Clear Flag) 8. Log off OWA, clear cache, close IE 9. Log on to OWA, see flag is cleared, click on Message, follow up not set in message. What's wrong with this process? Seems my OWA interface handles the follow-up flag just dandy. But look at this: 1. Mark a message as follow-up in OWA or Evolution 2. Click send/receive in evolution 3. Notice that the follow-up flag is set immediately in OWA 4. Be sure "check email automatically" is turned off in Evolution 5. Clear the flag in OWA 6. Reload the message and notice the flag is gone in OWA (reload browser and clear cache to make sure) 7. Click "send/receive" with Evolution 8. Notice no change in OWA 9. Click follow-up in Evolution on same message 10. Hit Send/Receive 11. Notice the follow-up flag is back 12. Hit "clear flag" in Evolution 13. Click "send/receive" 14. Notice the flag is gone in OWA, but the follow-up is still present in the message body. <b:x10900003>0</b:x10900003> (see below) is the property being set. The only reference I could find to this was under 'XML view definitions' in MSDN. I'm no expert in the schema for the XML passed to handle the properties but is the clear flag just clearing the property of the "red flag" instead of the actual data of the follow-up? Next Send/Receive evolution goes through, will repopulate the follow-up information since that information was never cleared. This is the message and response from Evolution -> Exchange Server when clicking "clear flag" in Evolution. PROPPATCH /exchange/mikew/Inbox/Re: Potential Hire.EML HTTP/1.1 E2k-Debug: 0x8107ce0 @ 1172620010 Host: exchange.localhost.com If-Match: * Brief: t User-Agent: Evolution/1.6.3 Content-Type: text/xml <?xml version="1.0" encoding="utf-8" ?><D:propertyupdate xmlns:D="DAV:" xmlns:b="http://schemas.microsoft.com/mapi/proptag/" xmlns:a="urn:schemas:httpmail:" xmlns:f="urn:schemas:mailheader:" xmlns:T="urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/"> <D:set><D:prop> <b:x10900003>0</b:x10900003> </D:prop></D:set><D:remove><D:prop> </D:prop></D:remove> </D:propertyupdate> 207 Multi-Status E2k-Debug: 0x8107ce0 @ 1172620010 MS-Exchange-Permanent-URL: https://exchange.localhost.com/exchange/mikew/-FlatUrlSpace-/4635cb9c341622408646b8ded954e9b8-2081ec/4635cb9c341622408646b8ded954e9b8-14088ad MS-WebStorage: 6.5.7638 ResourceTag: <rt:4635cb9c341622408646b8ded954e9b80000014088ad4635cb9c341622408646b8ded954e9b8000001a89f7b> Date: Tue, 27 Feb 2007 23:46:50 GMT X-Powered-By: ASP.NET Server: Microsoft-IIS/6.0 Content-Length: 239 Repl-UID: <rid:4635cb9c341622408646b8ded954e9b80000014088ad> Content-Type: text/xml <?xml version="1.0"?><a:multistatus xmlns:b="http://schemas.microsoft.com/mapi/proptag/" xmlns:a="DAV:"><a:response><a:href>https://exchange.localhost.com/exchange/mikew/Inbox/Re:%20Potential%20Hire.EML</a:href></a:response></a:multistatus> w
Forgot to mention: ||/ Name Version Description +++-==============================-==============-============================================== ii evolution 2.6.3-3 groupware suite with mail client and organizer ii evolution-common 2.6.3-3 architecture independent files for Evolution ii evolution-data-server 1.6.3-3 evolution database backend server ii evolution-data-server-common 1.6.3-3 architecture independent files for Evolution D ii evolution-dbg 2.6.3-3 debugging symbols for Evolution ii evolution-exchange 2.6.3.dfsg-1 Exchange plugin for the Evolution groupware su ii evolution-plugins 2.6.1-3 All bundled plugins for Evolution Not sure what version of Exchange I am on. I can find out if you need this information. Regards, - Mike
REOPENING as per the last comments. Duplicates, bug 335337 and bug 341127.
*** Bug 335337 has been marked as a duplicate of this bug. ***
Issue reproducible with v2.8 on RHEL5. Updating version from 2.4 to reflect the same.
Still reproducible on Fedora8 with Evo2.12 :(
using OWA in IE clears the flag as expected
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) by reporting back and providing both your version and the package that you use? Thanks in advance!
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.