Re: Re: Avoiding S/MIME
On 2023-09-01 16:15, Todd Zullinger wrote: > Hi, > > Jan Eden wrote: > > my configuration sets a PGP default key: > > > > set pgp_default_key = ... > > > > and outgoing messages are signed accordingly. But every time I reply > > to a message signed using S/MIME, mutt tries to add an S/MIME signature, > > too (which fails, as there is no S/MIME key available via GPGME). > > > > How can I prevent this behavior? > > You may want to check the crypt_auto* and crypt_reply* > variables to see how they are set. My first thought would > be disabling crypt_autosmime, e.g.: > > set crypt_autosmime=no Thanks, Todd, that worked. - Jan signature.asc Description: PGP signature
Re: Avoiding S/MIME
Hi, Jan Eden wrote: > my configuration sets a PGP default key: > > set pgp_default_key = ... > > and outgoing messages are signed accordingly. But every time I reply > to a message signed using S/MIME, mutt tries to add an S/MIME signature, > too (which fails, as there is no S/MIME key available via GPGME). > > How can I prevent this behavior? You may want to check the crypt_auto* and crypt_reply* variables to see how they are set. My first thought would be disabling crypt_autosmime, e.g.: set crypt_autosmime=no -- Todd signature.asc Description: PGP signature
Avoiding S/MIME
Hi, my configuration sets a PGP default key: set pgp_default_key = ... and outgoing messages are signed accordingly. But every time I reply to a message signed using S/MIME, mutt tries to add an S/MIME signature, too (which fails, as there is no S/MIME key available via GPGME). How can I prevent this behavior? Thanks, Jan signature.asc Description: PGP signature