Bug 394166 - KMail - No action buttons for calendar invitations in mail body anymore
Summary: KMail - No action buttons for calendar invitations in mail body anymore
Status: RESOLVED INTENTIONAL
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.8.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 16:15 UTC by Steeven Hudon
Modified: 2018-08-31 22:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Plain text that displays instead of the action buttons (38.21 KB, image/png)
2018-05-12 16:15 UTC, Steeven Hudon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steeven Hudon 2018-05-12 16:15:09 UTC
Created attachment 112600 [details]
Plain text that displays instead of the action buttons

Since updrading to KMail 5.8.0 on Manjaro, no action buttons (accept, refuse, tentative, etc.) does appear anymore in the mail body, no matter the source. Only the HTML status bar indicates "Calendar Message", and dependently of the source, an .ICS file is attached.
 
Furthermore, receiving calendar invitations from Outlook.live.com (PRODID: Microsoft Exchange Server 2010 - see attachment), KMail seems to recognize it as a calendar invitation (the HTML status bar indicates "Calendar Message") but in this case, no action buttons appear, neither is an .ICS file attached either.
Comment 1 Laurent Montel 2018-08-31 16:55:17 UTC
Hi,
Do you have an example email ?

Thanks
Comment 2 Steeven Hudon 2018-08-31 22:43:39 UTC
Hi Laurent,

In fact, this behavior didn't happen in the last months (so I cannot give any example)... sorry.  Is it because there since has been distro updates OR because I changed the Kmail settings (Kmail > Configure Kmail > Misc > Invitations > Groupware Compatibility & Legacy Options) and selected the 'three options ?  I cannot say.  

Now the buttons appears in the mail body.  So everything's fine.
I can now close this bug as I cannot provide more info about it.