-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Wrong html santitization for search column #30
Comments
Thanks for the information @kzaitsev. We can't rely on the envelope The best solution is still to manually convert the HTML (if set) to text, but I'll need to dig much deeper as to exactly why it is happening, and if it is an issue with html2text then that will need to be reported there to fix. Unfortunately I'm just heading off for a short holiday today, so it will be two weeks before I can probably look into this. I also see I am stripping out |
@axllent thank you for your quick response, I understand. I do some investigation and it seems https://github.com/jhillyerd/enmime uses https://github.com/jaytaylor/html2text to convert HTML to text in the case of HTML-only emails. |
Thanks again for reporting this. I found an option I could pass to html2text to include anchor content in the returned output, so this should now be solved in the latest v.1.3.5 release. Please feel free to re-open this if it does not solve your issue! |
Hello, it seems something is wrong with HTML sanitization when you build the
search
column. it looks like some tags were ignored and not unwrapped to text. As a result, when you try to find the email by word in the body, you can't get it.To reproduce, I'll attach a zipped eml file. In this case, the text "massmailgoodhost" will be dropped, and the "search" field will not contain it.
It seems like a bug of https://github.com/k3a/html2text, but instead of it, why not use the
Text
field of the envelope structure, which returns the eml parser (github.com/jhillyerd/enmime)?d80e6ca4-fb3c-4dcb-a6f8-030af2f8278f.eml.zip
The text was updated successfully, but these errors were encountered: