dougb at dougbarton
Jul 10, 2012, 1:58 AM
Post #3 of 4
On Tue, 10 Jul 2012, Hauke Laging wrote:
Re: Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0
[In reply to]
> I was just pointed at the problem that for the last months all of my
> signatures are supposed to be bad. I use KMail which shows both the emails I
> have sent and those I receive via this list as correctly signed. I just used
> Thunderbird (13.0) to check and TB claims even (most but not all) of the
> emails in my IMAP sent folder to have bad signatures. TB doesn't even
> recognize the received emails as signed (just shows an "attachment").
> The problem seems to be newline-related. I do not waste time by filing a bug
> report for the wrong software... Thus maybe one of the MIME experts here can
> tell me who's wrong. The KMail behaviour seems to have changed from KMail to
> KMail2. KMail2 successfully verifies the TB emails.
There is a difference in how KMail deals with EOL whitespace, I have an
exception for it in my PGP filters for Alpine. I don't know what's
different between KMail 1 and 2, but I'm glad you raised this. I can use
my filters to verify your KMail 1.x messages, but Enigmail refuses to
recognize that they contain valid signed messages. However I cannot
verify your latest message using KMail 2, so clearly there is something
> Thunderbird puts one more empty line between the body and the MIME seperator:
I'm not sure it's Thunderbird, I think it's Mailman (at least that was
the consensus from previous discussion). Have you compared the raw
message in your Sent mail folder to the one from the list? Also, if you
look at your message in the archives, it seems to be similarly
> I can manually successfully verify emails from both clients. So obviously one
> of them feeds the wrong data into gpg (during signing or verification).
Don't rule out "all of the above." :)
Seriously though, can you do me a favor and send me copies of the _raw_
messages from your Sent mail folder, and the message you received from
the list (the one I'm responding to is fine)? Please compress them
somehow (tgz is fine) so that they don't get molested in transit.
That'll help me sort out how whitespace is being handled differently in
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
Gnupg-users mailing list
Gnupg-users [at] gnupg