Hi Alexis,
thank you, but unfortunately the typo is just in my email.
The config file is fine.
Just looked around a bit and found out that the smime_keys script fills
this value using `neomutt -Q smime_keys`
When executing this with neomutt, it returns `set
smime_keys="~/.smime/keys"` while `mutt -Q smime_keys` just returns
`smime_keys="~/.smime/keys` without the set in front.
So probably more a problem of neomutt.
Kind regards,
David
Am 2026-02-24 22:30, schrieb Alexis:
David Wienecke <[email protected]> writes:
"Couldn't look up the value of the neomutt variable "smime_keys".
You must set this in your neomutt config file. See contrib/smime.rc
for
an example."
As my setup was a bit more complex, I added seti
smime_keys="~/.smime/keys"
to .config/neomutt/neomuttrc, but the error still appears.
While using neomutt, signing/encrypting/decrypting S/MIME works fine!
Can you confirm the above is a typo in your email, and that what you
actually had in your neomuttrc was "set smime_keys ...", not "seti
smime_keys ..."? neomuttrc(5):
https://man.archlinux.org/man/neomuttrc.5.en
doesn't list 'seti' as a command ....
Alexis.
