-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sometimes email is parsed badly #9
Comments
To fix it, I suppose example (redacted) messages would need to be provided for anyone to try and fix these exceptions you found. You're probably right that it's quoted-printable-related.
|
Hi pajousek. Thanks a lot for you bug reporting. As appastair is suggesting, can you provide some email sample (that we can even place in our directory of tests) and, potentially, also the fix/patch - that would be awesome. Thanks, |
If I could show you the emails, I would. But the emails can't be published. Maybe I could try to "reproduce" that screwed mail (forward via the same client etc. they have used)? Hope it will work. Or maybe someone else will stumble upon such email when using this parser and be able to share it? |
Hi Pavel. I see. Can you provide them after editing the sensible information? Or even Thanks, On Thu, Oct 11, 2012 at 10:07 PM, Pavel Kouřil notifications@github.heygears.comwrote:
|
Hello,
I've stumbled upon few examples, where email is badly parsed (mostly its charset).
I got two notices, first was that the encoding 3DUTF-8 can't be converted to UTF-8//TRANSLIT (probably there wasn't mentioned double-quotable in encoding)?
And second time i got notice that "UTF-8; " can't be converted. The " " after ; wasn't space, but some weird whitespace character that even trim() couldn't get rid of.
Btw. i like your parser, I really really do! Just please fix those issues, if you can.
The text was updated successfully, but these errors were encountered: