When invoked from mutt 1.2.5, pgp 6.5.8 fails when trying to encrypt to an untrusted (it works with a trusted key) key with the message: =================================================================== Pretty Good Privacy(tm) Version 6.5.8 (c) 1999 Network Associates Inc. Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc. Export of this software may be restricted by the U.S. government. WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "xxx xxxx <[EMAIL PROTECTED]>". Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. Press any key to continue... ================================================================== But if pgp is invoked from the command line, it prompts: ================================================================== WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "xxx xxxx <[EMAIL PROTECTED]>". Are you sure you want to use this public key (y/N)? ================================================================== A "y" response encrypts properly, but the default "N" response gives: ================================================================== Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. ================================================================== So the failure appears to be that mutt uses the default response of "N" instead of "y". I tried adding "+force" to the encryption line in pgp6.rc, because the pgp 6.5.8 Guide claims this will always force a "y" response. It does in some cases, but not to the above prompt. I searched the archives and found only the thread that Rod Pike started. He ultimately gave up on 6.5.8, but for a different reason. Are there any fixes to make mutt allow the user to respond to the prompt instead of hiding it and responding with the default? TIA -rex
