On Tue, 2010-03-23 at 21:43 +0000, mike cloaked wrote:
On Tue, Mar 23, 2010 at 9:36 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
>> Maybe that last point is the important one - in Thunderbird I have the
>> option of sending PGP/mime - but I can't see how to do this in
>> Evolution? Is there a switch I am missing because I did not look deep
>> enough or is it that Evolution just can't do PGP/Mime??
>
> At the moment you can't. There's been a lot of resistance to it as it's
> non-standard, but apparently some work is being done on it, see
>
http://www.go-evolution.org/FAQ#Why_does_Evolution_attach_a_.asc-file_to_...
Thank you, that is useful - though I am now more confused - I have TB
set to use PGP/Mime and sign email - and it is received by either TB
or Evo and verifies just fine - but from the quote it says that
(concerning Evolution): "When you sign emails, the GPG signature is
embedded in a .asc file, this is called Outline PGP (or PGP/MIME). It
is not embedded in the header/footer of the email because Inline PGP
is currently not supported by Evolution" - I thought this (PGP/Mime)
was the same as what I am using for Thunderbird? If so why does
Thunderbird then not verify? Or have I got the wrong end of the stick?
I just sent myself a plain text signed message from Evo and verified the
signature using TBird. Looking at the raw file, it does indeed have
a .asc attachment containing the signature, as per spec. I haven't tried
it in HTML as I never use it.
Going back to the error message in your original post, it complains
about:
gpg: BAD signature from "xxxxxxxxx (New rsa key)
<mike(a)my-email-server.com>"
That looks to me like a problem with the signature itself rather than
the message (though I wouldn't swear to it). Are you sure that your
configurations of Evo and TB are using the same signature?
poc