On Wed, Oct 16, 2002 at 09:02:58PM +0100, Karl E. Jorgensen wrote: > On Wed, Oct 16, 2002 at 11:59:44AM -0500, David wrote: > > In an attempt to learn more about the workings of gpg, I've been trying > > to verify emails from the command line. > > > > When I try to verify a saved message - one which has been reported as > > "good" from Mutt, gpg returns a "BAD" signature. > > That's probably because the mail is encoded in e.g. quoted-printable. > > When you save an attachment from mutt, mutt de-codes it first (so you > end up with plain text). > > From mutt, try to (C)opy the message to /tmp/somefile, and look at it > there. You'll probably see things like "--=20" at the beginning of the > signature.
I was able to get a good report on this message to which I'm replying. I don't believe I was able to do any good with the attachment saves.. but by simply doing a straight <s>ave, then cutting the body out and then cutting the signature attachment, it worked.. but I had to do some playing around.. I had to leave in the "Content-*" lines, and on this message, I had to delete a blank line at the end of the body.. I've still not been able to do any good with other messages, though.. It appears that there may be a variation in the way they different mailers modify the bodies or something.. Another oddity.. I was able to capture the temporary files that mutt created in verifying, and for some reason, in the body, it translated the LF's to CR-LF, but that didn't affect gpg's verify, it worked on your mail either way.. It's probably not important, but I just thought it would be nice to be able to do it from the command line..
