Open WhyNotHugo opened 9 years ago
Well, I sort of got around this by using encrypt-to
in gpg.conf
, though I'd prefer to have this done by mutt by default (or with some simple setting), rather than to change the user-wide gpg config.
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 leage. But maybe it's not too hard for someone else?
Sorry, I wasn't thinking. The previous comment and patch refers to using encrypt-to-self with S/MIME.
gpgme is cool, because it simplifies configuration, works better with gpg-agent, and has nicer output, but, there seems to be no way to encrypt-to-self.
Would it be possible to add an option to encrypt-to-self using gpgme as well?