Bug 338488

Summary:	akonadi email-links do not open mail client window
Product:	[Frameworks and Libraries] Akonadi	Reporter:	ingot
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	j-kde_bts
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ingot 2014-08-22 22:58:32 UTC

When I drag a message in KMail to a "Plasmoid" folder then this link does not open the respective message window.

More generally speaking: drag and drop for email messages works, but the file with the link created does not lead  to the right action.

If I am doing something wrong please let me know. Maybe my system needs some configuration? Otherwise I would expect that both from my desktop from a Plasmoid folder I could start that link as well as from a file explorer like Dolphin. 

It should be also possible to launch such an aconadi - link from a HTML document like in LibreOffice.

Please do not hesitate to ask me, if it is not clear enough what I mean.

Thank you very much for helping!

Comment 1 ingot 2014-08-22 23:02:33 UTC

kubuntu 14.04 latest updates from standard repository

Comment 2 JHF2442 2015-12-28 16:57:20 UTC

Same here when drag/dropping into dolphin

created item has file name :
akonadi:?item=69866&type=message⁄rfc822&parent=53.desktop

and content :
[Desktop Entry]
Icon=unknown
Name=akonadi:?item=69866&type=message/rfc822&parent=53
Type=Link
URL[$e]=akonadi:?item=69866&type=message/rfc822&parent=53

when clicking on the file, error message is 
The file or folder No such collection. does not exist.

Software info (arch linux) :
kmail 5.1using 
KDE Frameworks 5.17.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Comment 3 JHF2442 2015-12-28 17:05:39 UTC

see also https://bugs.kde.org/show_bug.cgi?id=357265

Comment 4 Justin Zobel 2021-03-09 05:46:31 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.