Skip to content
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

Some HTML messages fail to be parsed #168

Open
asfaltboy opened this issue Mar 3, 2014 · 1 comment
Open

Some HTML messages fail to be parsed #168

asfaltboy opened this issue Mar 3, 2014 · 1 comment

Comments

@asfaltboy
Copy link

This occurred for me with html messages from JIRA. I tried setting VMAIL_HTML_PART_READER to lynx, elink and w3m but all just displayed unparsed html. I will attach an example in a short while

@asfaltboy
Copy link
Author

The interesting thing is, that running the command manually on the html output works fine. So if I run: w3m -dump -T text/html -I utf8 -O utf8 < /home/pavel/.vmail/default/jira.html I see the correctly parsed output. This might be related to issue #163 (not sure)

This leads me to believe that the problem is with detecting where the html content starts and ends. If this is done by expecting the email headers/content-type/structure, here is the meta data that appears in vmail in addition to the html:

<[email protected]_company.com> 27k Seen 
- text/html; charset=UTF-8 
- image/png 
- image/png 
- image/png 
- image/png 
----------------------------------------------
from: "Some Person (JIRA)" <jira@my_company.com>
date: Sun, Mar 02 04:21 PM +00:00 2014
to: pavel@my_company.com
subject: [JIRA] (XXX-500) Recovery feature should be hidden

------=_Part_33_2038450303.1393777289047
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html
...
</html>
------=_Part_33_2038450303.1393777289047
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-Disposition: inline
Content-ID: <jira-generated-image-avatar-person-eba3e9a5-f974-4a6b-9776-d75c1fd13225>

iVBORw0KGgoAAAANSUhEUgAAACAAA
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant