Allie, Thanks for the reply, quite informative (and my compliments on the document in the link you gave me at landscreek.net, it helped me a lot).
On Monday, July 21, 2003, 9:15:57 AM, you wrote: AM> Was it an in-line encryption/signature or was it PGP/MIME? I probably didn't make this clear, and I'm probably not using the right terminology: What I'm trying to do is verify the signature on a message that was created by someone else, which was "Encrypted AND signed" by the author. I have his public key. Eudora, in this situation, lets me verify that the signature is valid, i.e. that I have a key in my keyring, with the fingerprint of the key that the author used to encrypt and sign. I was looking for the same functionality in TB. It seems that all TB does is issue a "gpg --verify" which produces the error I mentioned. From your description and everything else I've read, it looks like that is only good for checking a signature in a .sig file, a detached signature, not embedded in the encrypted message. Sorry for the confusion. AM> You can exported message text and then, through a batch script have AM> external programs process the text. If TB lets me actually launch an external program or batch file, to which I can pass parameters like the To: From: and contents of the message, I should be able to roll my own and write a program that performs this verification, until Ritlabs does it right. Thanks again and best regards ________________________________________________ Current version is 1.62r | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
