#3846: Use crypt_opportunistic_encrypt with other encryption settings
----------------------+----------------------
Reporter: Pynsent | Owner: kevin8t8
Type: defect | Status: reopened
Priority: major | Milestone:
Component: crypto | Version: 1.6.1
Resolution: | Keywords:
----------------------+----------------------
Comment (by kevin8t8):
Sorry about that. I misread your ticket, and somehow thought you were
using GPGME.
There are two backends used for encryption. By default Mutt will use the
"classic" backend, which invokes gpg using the various $pgp_*_command
settings. If you set $crypt_use_gpgme, then it will use a different
backend, but that one doesn't support inline PGP.
So first, please make sure you don't have $crypt_use_gpgme set. (I'm
guessing you don't since you say it works otherwise).
$crypt_opportunistic_encrypt should work fine for either backend, and
shouldn't interfere with inline pgp. When you say "the following setting
now does nothing", would you be more specific? Does it give an error, or
send using PGP/MIME, or send unencrypted?
Also, would you confirm that you are using version 1.6.1. There was an
issue fixed between 1.6.0 and 1.6.1 related to INLINE settings.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3846#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
