David T-G ([EMAIL PROTECTED]) muttered: > Shawn, et al -- > > ...and then Shawn McMahon said... > % > % Well, it's not unusual to have an occasional unverifiable mail, but for > % it to be so consistent for you, it almost has to be somewhere in your > % MTA path, not your MUA, since nobody else is seeing it with this > % frequency. > > I don't know that I'd say that. I cannot verify my own messages in my > own =mutt-users fcc folder. > > % everything but one of the messages you can't verify, then pump that > % message through gpg and see what happens. If it still doesn't verify, > % it's not Mutt. > > I had previously tried saving the body and the signature of a given > message and found that the signature was valid but not verified. > > I tried this method, using my editor to write everything from the last > ^From_ line down to the bottom of the folder out to a file, but couldn't > get gpg to do anything with it: > > [zero] [9:39am] ~> cat /tmp/m | gpg --verify > gpg: no signed data > gpg: can't hash datafile: file open error > [zero] [9:39am] ~> gpg --verify /tmp/m > gpg: no signed data > gpg: can't hash datafile: file open error > [zero] [9:39am] ~> gpg --verify < /tmp/m > gpg: no signed data > gpg: can't hash datafile: file open error
If those are pgp/mine it's sure that gpg can't verify anything. David I know you use several keyrings. If I uncomment all keyring lines in my options file I can verify any mail just fine. Without those lines the gpg output shows that the sigs are verified, but mutt says they can not be verfied. HTH, Michael -- "Whip me. Beat me. Make me maintain AIX." (By Stephan Zielinski) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
msg27244/pgp00000.pgp
Description: PGP signature
