I had mutt-1.2.5i working fine with gpg-1.0.6. Today, i upgraded mutt to:
[mjbjr@localhost gnupg-1.0.7]$ mutt -v Mutt 1.3.99i (2002-05-02) Now, when I invoke pgp/gpg with 'p', then 'a(s)', then enter some text to specify a key, all I get is a beep. If a don't enter some text to specify a key, I get a mutt notification that seems to indicate it can't find gpg/pgp. Anything else pgp/gpg in mutt ( in regards to sending a msg) results in a beep. A check of docs and the list archives doesn't reveal anything significant. I don't find any config vars that would I would use to point to pgp/gpg binary. I did find a few semi-related things that implied that maybe I should update to the latest gnupg. I update to the latest, gnupg-1.0.7. Now, all mutt pgp actions in regards to sending a message result in a beep. Both, mutt and gnupg compiled and installed without problems. mutt was configured with: ./configure --enable-pop --enable-imap --with-ssl Other programs that use gpg/pgp continue to work with the new gnupg. Any ideas on how to solve this? Thank you. -- - Martin J. Brown, Jr. - - [EMAIL PROTECTED] - Public PGP Key ID: 0xB29EDDCADB184F7B keyserver: http://certserver.pgp.com/