-
Notifications
You must be signed in to change notification settings - Fork 25
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
ResponseParseError in envelope
: unknown token - #{???}
#191
Comments
nevans
changed the title
unknown token - ""Fwd:"
Net::IMAP::ResponseParseError: unknown token - ""Fwd:"
Oct 3, 2023
nevans
changed the title
Net::IMAP::ResponseParseError: unknown token - ""Fwd:"
Net::IMAP::ResponseParseError: unknown token - "\"Fwd:"
Oct 3, 2023
nevans
changed the title
Net::IMAP::ResponseParseError: unknown token - "\"Fwd:"
ResponseParseError in Oct 3, 2023
envelope
: unknown token - #{???}
I'm actually using a forked version which has several workarounds for servers that send buggy quoted strings (containing NULL chars). This might even be an error in my forked version... or it might be that these responses were already failing to parse and I'm only now noticing them because I removed some deviations from my forked version! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parse errors in
envelope
fields. I'll add more details about these later. Right now I only have the stacktraces and the error message. These might be bugs in our code, or they might be server errors that we need to handle more gracefully.Net::IMAP::ResponseParseError: unknown token - ""Fwd:"
Net::IMAP::ResponseParseError: unknown token - "=E2=80=9DStar_Action_Shots""
Net::IMAP::ResponseParseError: unexpected token NUMBER (expected SPACE)
The text was updated successfully, but these errors were encountered: