Version: (using KDE 4.3.0) OS: Linux Installed from: Unlisted Binary Package With DKIM the sending mailserver adds a signature to the email headers, similiar to a GPG signature. The receiving mailserver then validates the signature with a public key published in the DNS record of the sending domain, on success, a header is added to the email. It would be cool, if KMail could mark messages, that passed DKIM similiar to the way GPG-Messages are marked! dkim-milter produces following header: Authentication-Results: mx.rcpt.domain; dkim=pass (1024-bit key) header.i=@sender.domain; dkim-asp=none Google uses the following header (first SPF, then DKIM): Authentication-Results: mx.google.com; spf=pass (google.com: domain of sender@sending.domain designates xxx.xxx.xxx.xxx as permitted sender) smtp.mail=sender@sending.domain; dkim=pass header.i=@sending.domain KMail could also do the signing and verification on its own, but imho this is the job of the mta, not the mua.
RFC5451 (http://tools.ietf.org/html/rfc5451) defines a standard for Authenticated-Results headers to parse in a validation mechanism agnostic manner.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
I think it should still be a valid feature request for kmail2. (In reply to comment #3) > Instead of creating a new feature request, please confirm here if the > wishlist is still valid for kmail2.
It could be added to the message header similar to Spamassassin