-
Notifications
You must be signed in to change notification settings - Fork 115
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
Gmail reply fails to parse #15
Comments
Mind posting the full input message? (Feel free to censor the private bits.) |
|
Thanks! |
Same issue here i guess
|
Has support for this project stopped? I am also unable to parse anything |
@sergioisidoro For me, the timestamp always begins with
which fits the test case specified here. @bryanhelmig I wonder if this issue is outdated and can be closed, or is specific to certain email clients. Any ideas? |
I think its client specific. I would be willing to accept a PR to handle On Tue, Nov 15, 2016 at 11:19 PM Sung Won Cho notifications@github.com
|
I'm using a Google Mail account and I get a parsing error on the third email (second reply). Here's my test: Email 1
Parsed reply (correct):
Email 2 (Reply 1)
Parsed reply (correct):
Email 3 (Reply 2)
Parsed reply (incorrect):
It's worth noting that GitHub's Ruby version has the same problem. |
Result of parsing a message
Last line is part of the reply header
The text was updated successfully, but these errors were encountered: