Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Why has Thunderbird stopped decoding base64 encoded .json files that are attached to emails?

  • 2 Antworten
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von tsssys

tsssys
tsssys
more options

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?

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?

Alle Antworten (2)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

> 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/  ?

tsssys
tsssys Fragesteller
more options

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.