https://bugs.kde.org/show_bug.cgi?id=368694
Bug ID: 368694
Summary: mailto url body lost for unknown reasons
Product: kmail2
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-bugs@kde.org
Reporter: sit...@kde.org
kgpg can sign and send a key by mail. it does so via qdesktopservices::openurl
to which it passes an url of the form
mailto:sit...@kde.org?subject=Your%20key%20asfadfafadsf&body=-----BEGIN%20PGP%20MESSAGE-----%0AVer
The body part of this url is subsequently lost in kmail for unkown reasons and
doens't display in the editor window at all. Subject works as expected.
this doesn't work:
kmail
'mailto:gr...@kde.org?subject=Your%20key%207FEA3DA6169C77D6&body=-----BEGIN%20PGP%20'
this works:
kmail
'mailto:gr...@kde.org?subject=Your%20key%207FEA3DA6169C77D6&body=-----BEGIN%20PGP'
Parsing in kmkernel works correctly, it passes the string as expected to
::action to ::openComposer where the body is still correct before it is put in
a KMime::Message and handed to KMail::makeComposer which in turn goes to
KMComposerWin::KMComposerWin where it goes into
MessageComposer::ComposerViewBase::setMessage. Unfortunately I couldn't build
all the necessary stuff, so that's where I gave up.
Working theory is that the composer eats the body for unknown reasons. It can't
be decryption problems though since from what I can tell in all my tests the
relevant bool argument was false. Nevertheless it could be that invalid pgp
messages get rejected (if so it should still put a warning or something in the
body).
If so, it's conceivable that somewhere along the line the fairly long body
constructed by kgpg (encrypted message blob) would get truncated resulting in
no body in kmail due to invalid pgp block.
Reproducible: Always
--
You are receiving this mail because:
You are the assignee for the bug.
