Why has Thunderbird stopped decoding base64 encoded .json files that are attached to emails?
I now get this message:
"This attachment appears to be empty. Please check with the person who sent this. Often company firewalls or antivirus programs will destroy attachments."
Yet when I view the message source, the attachment is there:
--===============6698689683868226577== Content-Type: application/json MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="abcdefg_data.json"
(file name changed, of course)
The mime encoding visible in the source decodes just fine in an external service.
This used to work just fine and only stopped working in the last few months. I have tbird set to auto update, and am currently on 52.5.2 (32-bit) on a Windows 10 platform. Anyone have any clues about this?
ప్రత్యుత్తరాలన్నీ (2)
> This used to work just fine and only stopped working in the last few months 1,2,4,6 ?
Any better with beta? http://www.mozilla.org/en-US/thunderbird/channel/ ?
Wayne:
Thanks for the suggestion, but it seems now it was Windows 10 related. I discovered I didn't have the same problem on a Win7 machine (that I don't use as often). When I came back and tried it again yesterday on the Win10 machine - after deleting the content-type "json" under attachments - I was able to get it working again.
Something with the Win10 updates? Something corrupted in the attachments action? I don't know, but it's OK again.
Thanks again for the link. I'll probably try out the beta; didn't think about that before.