Fix screenshot link from previous comment, sorry for the trouble.
This ticket has been created in response to #420. It's not a priority since PGP needs to be implemented and stable first.
aerc's own keyring should add support for smartcards. Importing the "reference" to a private key stored on a smartcard should be allowed.
Thanks for your answer. Is smartcard support planned then? As it was my original issue I could reopen a ticket for this specific use case.
IMO relying on existing and established tools such as
gpgwould be the best way to provide support for these features without requiring too much development effort (I guess) and without having to reinvent the wheel.
Also, users with existing keyrings would have a much nicer experience since it would allow them to use what they already have and not have a separate tool to manage when importing keys and trusting them.
I did more testing about the HTML forwarding and came to the conclusion that in fact we can't at all forward the HTML part of an email. I updated the ticket accordingly.
Here's what the recipient sees as filename when I sent the attachment with the accent and the file wouldn't open:
See this screenshot.
There are some issues when sending an email with accents in the filename of an attachment. I received this error message in the status bar (bottom of the screen):
imap: size of Literal is not equal to Len() (97934 != 97932)
The recipient was unable to open the attachment and there were. A workaround was to rename the attachment to remove the accents and resend it.
The offending character was "é" but I suspect any character outside the ascii space will fail.
I faced it both on master and 0.4.0.