GPGME Dialog#
Introduction – Where am I?#
The GPGME Dialog is the key chooser used when NeoMutt relies on the GPGME library for cryptography. It can represent either OpenPGP or S/MIME keys, depending on what the current send operation needs. In other words, it is the modern, unified version of the backend-specific PGP Dialog and S/MIME Dialog.
1 u 4096/0x7224725C RSA es Jim Smith (backup) <jim@example.com> 2 u 4096/0x7224725C RSA es Jim Smith (backup) <jim@example.com> 3 f 4096/0x810582F5 RSA es James Smith (flatcap) <jim@example.com> 4 f 4096/0x810582F5 RSA es James Smith (flatcap) <jim@example.com> 5 f 4096/0x810582F5 RSA es James Smith (flatcap) <jim@example.com> PGP keys matching <jim@example.com>
What am I looking at?#
Each row is a candidate key or certificate, showing trust, key size, key ID, algorithm, capabilities, and user ID.
The highlighted row is the identity GPGME will use for the current send step.
The status line shows which address or lookup produced the candidate list.
What can I do?#
Choose the correct key or certificate for encryption or signing.
Verify key details before accepting them.
Inspect the selected identity’s displayed user name.
Cancel and return to the send workflow.
Full reference: Pgp Functions, Smime Functions.
Where can I go next?#
Selecting a key returns you to the Compose Dialog so sending can proceed.
Verifying a key can open one of the Simple Pagers.
Cancelling returns you to the compose/send flow without a final key choice.
Where did I come from?#
You typically arrive from the Compose Dialog during sending when
$crypt_use_gpgmeis enabled.The exact crypto mode may have started as a PGP choice or an S/MIME choice in compose.
How do I configure this?#
Start with Encryption Config and Send Config.
Common options include
$crypt_use_gpgme,$crypt_auto_encrypt,$crypt_auto_sign,$pgp_default_key, and$smime_default_key.Related commands include
:crypt-hookand generic:setconfiguration.Colours come from Colour Objects, especially
indicator,status,message, andnormal.