-
Notifications
You must be signed in to change notification settings - Fork 31
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
Handle RTF-encapsulated HTML #6
Comments
@granite-zero I'm pretty sure your issue is different: The problem with @kobeller's messages is that the HTML bodies are actually RTF, and the problem does occur on Linux. Can you open a new ticket please? |
I also have the same issue on linux when converting the html (as it sees RTF - and then add's the html part as rtf attachment). Is there a way to get round this? Perhaps being able to extract the html from the rtf part? |
These bodies are RTF-encapsulated HTML (who came up with that?), and there's a process for converting it back to HTML. |
@mvz I know this edge case is weird, but it arrived to me in as real complaint from the customer. So, should I follow the guide you linked or do you intend to implement it in the library? Also, any tips to deterministically identify those messages and distinguish them, for example, from plain RTF? |
@kobeller I'm considering implementing it in the library, but I'm still investigating whether there's a suitable RTF reader library in Perl that I can use as a base. |
The attached archive contains .msg files with HTML bodies encoded in base64.
The library fails to convert them correctly to .eml messages.
msg.zip
The text was updated successfully, but these errors were encountered: