No subject

an invalid signature, even if the sender using KMail did not change anything in
his GnuPG configuration, because:

1) There are clients which complain when the declared hash algorithm does not
match the hash algorithm that has been used. If I remember correctly I
encountered this problem with Sylpheed (and this is how I got aware of this bug
in the first place).

2) If a mail is both, encrypted and signed, GnuPG by default should use the
hash algorithm that is preferred according to the recipient's key preferences.
So if the recipient prefers SHA256 according to his key SHA256 should be used.
However, KMail will still declare it as SHA1.

With people moving away from SHA1, I think the priority of this bug should be
increased.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.