-
Notifications
You must be signed in to change notification settings - Fork 96
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
Incorrectly interpreted mail body #157
Comments
Yeah.. the eternal struggle goes on, sorry to hear it caused problems for you. The Mail gem (#127) would probably perform better, but we're not there yet. Maybe there is something we can tweak... or at least warn the user about the incorrectly parsed e-mail. Was this HTML? Or does the text you pasted above provide a full example? |
No problem, every crash solved leads to a bit more stable sup, which is a good thing. The original mail was longer, but the above snippet is the minimal mail I can reproduce the content with. I test by passing the above with some HELO etc to port 25 of my mail server. |
Great! minimal working example is the best. |
This seems to be related to how sup displays the line, the line is parsed alright by RMail. |
Properly handling different encodings really is a pain in the butt, here is another issue I ran into. This mail body is not interpreted right by sup.
There are two issues with this:
visible (thus only the text "still visible in the thread view.")
Unfortunately I now have an unhappy customer because I missed the first line
of his mail :)
The text was updated successfully, but these errors were encountered: