Here is the email contents that fails parsing correctly: Delivered-To: forum.kozovod.com+d2087a39fd926dc770fc69ad642a5b35@gmail.com Received: by 10.28.132.66 with SMTP id g63csp2663084wmd; Wed, 1 Feb 2017 19:35:51 -0800 (PST) X-Received: by 10.223.129.163 with SMTP id 32mr5222217wra.140.14…

What happens with it? I note it has: [immagine] meglio: Content-Transfer-Encoding: binary on the text part. That’s legit, but obscure. Content-Transfer-Encoding: 8bit is more common for raw content in MIME. Edit: This is about NoBodyDetectedError issues, I take it.

Cannot parse email correctly: another case

Support

zogstrip 30 Aprile 2019, 8:14am 4

@meglio Are you still having issues with these kind of emails?

Argomento		Risposte	Visualizzazioni
Incorrect incoming email parsing case (Ukrainian language) Bug	2	839	Agosto 31, 2016
Incoming emails trimmed despite trimming disabled Bug	5	708	Luglio 18, 2023
Import_mbox.sh not working with e-mails from Samsung phone sent via a listserv server Support	8	926	Maggio 9, 2022
URLs being dropped from Thunderbird-generated replies Support	27	3528	Aprile 28, 2022
Proposed plugin to improve reply-by-email accuracy Feature	2	828	Dicembre 26, 2023

Cannot parse email correctly: another case

Argomenti correlati