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: [imagem] 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

Product Support

zogstrip 30 Abril , 2019 08:14 4

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

Tópico		Respostas	Vistas
Incorrect incoming email parsing case (Ukrainian language) Bug	2	848	31 Agosto , 2016
Incoming emails trimmed despite trimming disabled Bug	5	724	18 Julho , 2023
Import_mbox.sh not working with e-mails from Samsung phone sent via a listserv server Product Support	8	941	9 Maio , 2022
URLs being dropped from Thunderbird-generated replies Product Support	27	3604	28 Abril , 2022
Proposed plugin to improve reply-by-email accuracy Feature	2	846	26 Dezembro , 2023

Cannot parse email correctly: another case

Related topics