Bug 347862

Summary: To-Do created out of kmail : attached email can't be opened
Product: [Applications] korganizer Reporter: JHF2442 <j-kde_bts>
Component: todoviewAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED FIXED    
Severity: major CC: montel, y
Priority: NOR    
Version First Reported In: GIT (master)   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description JHF2442 2015-05-17 20:53:08 UTC 
A to-do was created out of kmail (button "create to-do" in the toolbar)
In korganizer, when opening the todo item, the email is show as attachement. But it is not possible to open the email.
Therefore it's not possible to get back the information that lead to the todo item, unless the original mail was kept in kmail !

This may lead to a loss of data the user is not aware of !

When editing the properties of the attachement, the "location" field contains a 32K character string. No idea what that should be !

Found out that the issue happens when the email is stored on an IMAP account. Local account seems to work so far. Difference is also that local mail attachement is stored inline whilst IMAP attachement is not stored inline


Reproducible: Always

Steps to Reproduce:
1. Create to-do out of email in kmail
2. Go to korganizer and open the created item
3. Go to attachements try to open the mail

Actual Results:  
Nothing happens

Expected Results:  
Email should open !

BTW, this relates to korganizer 4.14.8 (arch linux), but this version is not visible in the list !
Comment 1 Chris 2016-01-22 21:33:07 UTC 
I can confirm the bug on Kubuntu 15.10  with Kontact 5.0.2 (15.08.2-0ubuntu1).

It also affects POP3 accounts. Saving the message inline does not change anything, the message still cannot be opened.

Trying to save the message via right click -> "Save as" results in an error message like the following:
"
Malformed URL UmV0dXJuLVBhdGg6IDxpdWxpYW5hLmJsaWRhcml1QGxpbmdv…oZXIgb24gb3RoZXIgcHJvamVjdHMuCgpXYXJtIHJlZ2FyZHMsCkl1bGlhCg==.
"
Comment 2 Laurent Montel 2017-09-26 04:55:17 UTC 
Fixed in 5.6.1