New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text of email is not properly decoded #86
Comments
Could you paste the entire message, otherwise i can't see if there is anything wrong with it or not. |
As soon as I get in front of a computer I will pass it on but for more info the account I'm checking is a Gmail account, and the emails that are not being decoded properly are being sent from another Gmail account, from the web interface. All emails being sent from the web interface are not being decoded properly for me. |
In getting you the contents of the email I inadvertently fixed my own problem. I was using node-imap in conjunction with mailparser. My fetch call was only requesting the to, from, date, and subject headers, along with the text. Apparently when requesting only some headers the body of the email is no longer able to be parsed. When I requested the email in its entirety it parsed correctly. |
Thank you, you saved my life ! |
I'm testing against a gmail account, I've received a few emails from other sources, and have sent myself both text and html emails. When I parse the emails my
text
property always comes back with boundaries in place, and if it's an email with both HTML and text the property contains both:Plain text:
HTML + Plain text:
Is this how the
text
property is supposed to behave? All other properties get properly parsed, just not the body.The text was updated successfully, but these errors were encountered: