https://bugs.kde.org/show_bug.cgi?id=332368
--- Comment #11 from Rolf Eike Beer <k...@opensource.sf-tec.de> --- determineType() should identify it properly, maybe the caller just has wrong checks of the return code? While looking at it prepareMessageForDecryption() just below is also a bit too aggressive when trying to find something to decrypt, maybe it should call out to a variant of determineType() and properly look on the return code? -- You are receiving this mail because: You are the assignee for the bug.
