Thanks! You guys rock!

To reproduce:

1. Send a signed and encrypted email to yourself. The email should contain some body text and an attachment (I used a text file kek.txt as the attachment).
2. Open the email, you should see the message body (of text/plain content type).
3. Now do :open to open it in an external program.
4. Aerc tries to open a file named aerc-1111127589.gpg, even though the file itself is a .txt (the file contents are correct though).

This causes the text/plain email body to be open using a program for gpg files (Seahorse, in my case), and I'd expect it to be open with my viewer for text files.

When the email is not signed and encrypted at the same time, the name of the open file doesn't have the .gpg extension. Is there a way to get the same behavior with signed and encrypted emails too? A file with no extension at all should do fine, I think.

Thanks a lot for fixing this. I can't reproduce the bug anymore.

https://paste.sr.ht/~ph14nix/654fb1ca68771840713be8445cc48f74bcc34326

1. Open this PGP-signed email in Aerc.
2. Navigate using Ctrl+j to the attachment.txt.
3. Pipe it using |less.
4. Aerc opens new tab displaying

-----BEGIN PGP SIGNATURE-----
…
-----END PGP SIGNATURE-----

instead of the selected attachment. The same happens if you save the attachment instead of piping it. Normally, it should use the attachment contents.

I speculate something must be off with the index of the attachment that is being piped.

Some emails in my maildir cause Aerc to produce the following error (Gmail is my account name):

Gmail: could not get structure: could not parse child entity structure: could not parse content type: mime: no media type

It shows the error in the bottom of the screen in red.

Here's a sanitized version of the email headers that caused the error.

User konimarti on IRC gave a pointer to a possible cause of the error:

It seems that the mime.ParseMediaType function in go does not like quotes around the "application/pdf" content-type. Without the quotes, the parsing works for me.

I also used to experience rohan47's issue with profile failing to apply. But I can't reproduce it from sometime around commit 5267594b.

Maybe #70 is the right issue for profile failing to apply.

Why isn't it in the main repo? (What's the role of ~rjary/aerc for the project?)