GNOME Bugzilla – Bug 220780
Better subject in outgoing iMIP messages
Last modified: 2013-07-23 14:34:43 UTC
replies to imip messages should have better body text than they currently do. (Even just "Accepted", "Declined", "Tentatively accepted"). 1.0.3?
Also "Updated event info"
Well i already fixed this for 1.2. I could probably back port the fix.
JP: what did you change exactly? I don't see it in the ChangeLog. Since we can no longer include a separate message body with iMIP, we need to use the DESCRIPTION property (since that's what Outlook will display in the preview pane). The description for a request should probably include at least start/end times and location. The description for a reply should include that info plus whether the request was accepted, tentatively accepted, or declined. The description for an update should include something about "updated information". If it could show both the old and new times that woudl be cool. In bug 214705, Damon also suggested adding an "X-DESCRIPTION" property, at the top level of the VCALENDAR object, formatted for human-reading rather than machine. This should have the same info as the DESCRIPTION basically, plus a "your mailer doesn't understand iMIP" explanation. It would probably have to be inserted into the iMIP text by hand rather than by using libical, since we want to guarantee it looks a certain way in the message source.
Oh, body text, i misinterpreted what you meant. I added a status field to the html of the itip control.
OK, we don't actually want to set DESCRIPTION, because the user may have set that. I've submitted a patch to improve subject lines, but we still need to deal with the case of putting "Updated: " when sending an update to a previous PUBLISH/REQUEST. This will require some changes somewhere, to make the meeting editor pass the "this is an update" flag to the itip-sending code.
Fixed in 1.0.3
no, as my previous commented stated, we still don't properly deal with "Updated".
*** This bug has been marked as a duplicate of 230191 ***
Not duplicated.
Retargeting 1.5.3 reports to 1.5.4. Sorry for the spam.
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.