Signature in Attachment
Stewart V. Wright
swright at physics.adelaide.edu.au
Wed Dec 8 02:07:06 CET 2004
* Don Ferguson <Don.Ferguson at mitchell.com> [041207 18:51]:
> Thanks for the response. Unfortunately ditching MS Outlook isn't an
> option for me.
It really should be high on your priorities. Not only does it not
allow your preference with GPG/PGP but it also breaks threading in
replying to emails... Argh, it'd drive me mad! ;-)
[Oh and whilst I am bashing you TOFU (Text Over Full-quote Under)
makes reading replies difficult too... Is there anything else you do
that I can complain about??? :-> ]
> I will look at the possibility of routing a message
> received by Outlook into another application, but I am looking for an
> Outlook/ Windows solution if one exists.
There should be a Outlook plugin somewhere... Did you see this message?
> When I save the body of the message into a text file and use the
> gpg --verify option, the signature still fails. Perhaps it has
> something to do with the way Windows handles line breaks as opposed to
Possibly that's because the signature is for the _whole_ text message,
so when I view my last message I see something like...
Content-Type: multipart/signed; micalg=pgp-sha1;
Content-Type: text/plain; charset=us-ascii
You would need everything between the "--envbJBWh7q8WU6mo" lines.
I should clarify that I am guessing here.
Hope this helps.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 274 bytes
Desc: Digital signature
Url : /pipermail/attachments/20041207/ca1f61a6/attachment-0001.bin
More information about the Gnupg-users