We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently it's not possible to tell mutt(-kz) to also encrypt to the default key with S/MIME.
There's this patch: https://www.mandarb.com/mutt/patch-1.5.19-ow.smime-encrypt-self.1, which applies with little adjustments (adjusted here: https://gist.github.com/duckdalbe/49f1b0171db662074dcc). But apparently it fails to properly add the default-key to the keylist: when running mutt with the option it core-dumps while encrypting saying
error adding recipient `0xREALRECIPIENT0xDEFAULTKEY?': End of file?
Fixing this is out of my league. But maybe it's not too hard for someone else?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently it's not possible to tell mutt(-kz) to also encrypt to the default key with S/MIME.
There's this patch: https://www.mandarb.com/mutt/patch-1.5.19-ow.smime-encrypt-self.1, which applies with little adjustments (adjusted here: https://gist.github.com/duckdalbe/49f1b0171db662074dcc). But apparently it fails to properly add the default-key to the keylist: when running mutt with the option it core-dumps while encrypting saying
Fixing this is out of my league. But maybe it's not too hard for someone else?
The text was updated successfully, but these errors were encountered: