Version: 1.7 (using KDE KDE 3.3.0) Installed from: SuSE RPMs When the option "Always Sign Messages" is selected (from the Security/Composing section) sent messages are only signed if there is a signature key listed in the default identity. If there is a signature key listed in a non-default identity, and a message is sent using this identity and there is no signature key listed for the default key then no gpg signature is automatically applied, unless the "Sticky" option is used so that the non-default identity is already selected when beginning a mail. In essence this is similar to a previous bug (38841) whereby the (non-cryptographic) signature wasn't changed when the identity was changed. To reproduce: Have two identities, one with a signing key listed, one without The one without is default Have the "Automatically Sign Messages" option selected Start a new mail (check that indeed the default identity is selected) Notice that the "Sign Message" box is not ticked Switch to the identity that does have a signing key Notice that the "Sign Message" box does not become ticked
Having a similar problem: Creating a message with a "wrong" identity results in a mail left in the outgoing folder because the mail cannot be sent. After double klicking at this mail and switching the identity to the "right" identity I can now sent the message but the mail is not signed. The "right" identity is correctly configured to sign every message.
Oh, forgot to say : using KMail 3.4.1 under Gentoo Linux, build some days ago
*** This bug has been marked as a duplicate of 51410 ***