pgp Sign as: <default> config

Kevin J. McCarthy kevin at 8t8.us
Mon Apr 11 17:33:57 UTC 2022


On Mon, Apr 11, 2022 at 06:09:01PM +0200, Orm Finnendahl wrote:
>when replying to a signed Email, my response Mail is automatically set 
>to be signed by me.

Are you doing that via $crypt_replysign or via some other method?  Are 
you replying to a PGP-signed message to an S/MIME message?  The behavior 
you are describing below is not normal, so I suspect something more is 
going on.

>The pgp line concerning my key says
>
>"sign as: <default>"

The compose menu will display this when $pgp_sign_as is unset.  In that 
case, Mutt will use the value in $pgp_default_key, or what is configured 
in your gpg.conf.  If neither of those are set, then I'm guessing this 
is the error returned by GPGME when it tries to sign with no key 
defined.

>Unsetting and then resetting Security to "sign" results in the line
>
>"sign as: 0xA1XXXXXX"
>
>with the value of my Hex pgp Key configured in my .muttrc as
>
>"set pgp_sign_as = 0xA1XXXXXXX"
>
>and everything works as expected.

That's the part that makes no sense to me.  Simply unsetting and 
resetting "sign" will just display the value of $pgp_sign_as.  Did 
something else happen in your workflow?

Also, what version of Mutt are you using?

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20220411/c6f2fbe7/attachment.asc>


More information about the Mutt-users mailing list