https://bugs.kde.org/show_bug.cgi?id=340321
gigad...@revreso.de changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=340321
--- Comment #5 from hgee...@osso.nl ---
The manual python check was broken anyway since it did not convert newlines to
CRLF.
I think the fix in enigmail was commit
http://sourceforge.net/p/enigmail/source/ci/8d7fa201ba8bda6f33df348d83923ff0cc876958/tree
https://bugs.kde.org/show_bug.cgi?id=340321
--- Comment #4 from gigad...@revreso.de ---
Well, this adds to my confusion. I can't figure out wether the change in
Enigmail 1.8 is really a bugfix or only a compatibility feature for broken
clients.
So, is the kmail/gpgparsemail behaviour the right on
https://bugs.kde.org/show_bug.cgi?id=340321
--- Comment #3 from hgee...@osso.nl ---
I just tried to verify my mbox mail with
https://www.gnupg.org/documentation/manuals/gnupg/gpgparsemail.html and that
seems to succeed the signature check. Which gave me a reason to question the
manual method descr
https://bugs.kde.org/show_bug.cgi?id=340321
hgee...@osso.nl changed:
What|Removed |Added
CC||hgee...@osso.nl
--- Comment #2 from hgee...@os
https://bugs.kde.org/show_bug.cgi?id=340321
--- Comment #1 from gigad...@revreso.de ---
Created attachment 89310
--> https://bugs.kde.org/attachment.cgi?id=89310&action=edit
example of a PGP/MIME signed mail by kmail
--
You are receiving this mail because:
You are the assignee for the bug.
___
