GNOME Bugzilla – Bug 342998
Connector doesn't dismiss Calendar events on Exchange Server
Last modified: 2013-07-23 14:32:02 UTC
When an event comes up in the calendar and it pops up the Clock in the task bar there is no option to dismiss the event like in Outlook. As a result when you go into the Exchange account using either OWA or Outlook you get all your past events pop up and you have to dismiss them all. There should be an option to either sleep or 'complete', 'dismiss' or 'finish' the event with the appropriate commands sent to the exchange server to complete this.
Bug 245103 returned, eh?
Certainly looks like it. When i was searching bugs I was only looking in open bugs.
Peter Robinson, Are you seeing this issue in Evolution 2.6.x?
Yes (hence the 2.6.0 version tag), in fact its 2.6.1 as in Fedora Core 5.
Reproducible in evo 2.6.x
Created attachment 92531 [details] [review] patch in e-cal-backend-exchange-calendar.c fixed by synchronizing with Exchange server on closing an alarm popup.. [equivalent to dismissing an alarm in Microsoft Outlook]
This will patch will not work with recurring appointments. Why is the function modify_object_with_href not being used ? Avoid code duplications and attach the ChangeLog for the patch.
the function modify_object_with_href is not being used because the processing done within that function is non-essential for the event of dismissing an alarm (In reply to comment #7) > This will patch will not work with recurring appointments. Why is the function > modify_object_with_href not being used ? Avoid code duplications and attach the > ChangeLog for the patch. >
Hmm. go through the function and understand what it does before making a conclusion whether it would be need or not.
Created attachment 92970 [details] [review] patch in e-cal-backend-exchange-calendar.c fixed by synchronizing with Exchange server on closing an alarm popup.. uses (modify_object_with_href).. for alarms of recurring events, Outlook changes only the LAST-MODIFIED property on dismissing an alarm - the attached patch also does the same [by not removing the VALARM component, yet calling (modify_object_with_href)]..
Even with the patch i guess the alarms popup for recurring appointments. A better way needs to be found for solving this. Am not sure if exchange provides an interface for dismissing alarms.
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.