Hey @teejee2008 — thanks for reporting this! I don’t think I’ve seen this happen before. I appreciate you dong a second install on another system, that rules out the app being unable to write to the filesystem to save files, etc.
Could you try opening that email in Mailspring, and then clicking in the whitespace to the left of the Reply button?
There’s a small hidden menu there with an option to “Show Original”. If you click that, it’ll open the RFC2822 message (the raw MIME from your mail server).
Inside there, you should see a structure something like this:
Content-Type: multipart/related; boundary="000000000000b0e5ba05a3e7e21e"
Content-Type: multipart/alternative; boundary="000000000000b0e5b705a3e7e21d"
Content-Type: text/plain; charset="UTF-8"
<possible plaintext version of email>
Content-Type: text/html; charset="UTF-8"
<possible HTML version of email>
Content-Type: image/png; name="image.png"
Content-Disposition: attachment; filename="image.png"
If you could post the general shape you see in your email that’ll help me narrow this down and create a test case to reproduce it. It’d be super helpful if you could send me the entire text of that raw MIME message to email@example.com, but I understand the backup in this screenshot might be sensitive data so that’s fine!
Ahh one more question—is there any chance this attachment is a plain text file? We recently added support for plaintext message viewing / replying in Mailspring, and it’s possible that the app now thinks the plaintext is a separate “version” of the message body, not an attachment. I haven’t seen that happen, but if this didn’t occur until recently there’s actually a pretty narrow set of things that could cause it.
(Originally posted by bengotow on GitHub.)