-
Notifications
You must be signed in to change notification settings - Fork 117
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
Header decoding issue. #130
Comments
@emersion Here is my attempt at getting a more tolerant reader, any issues you see with it It adds a new reader leaving the existing one intact to prevent breakage to existing users. |
The error message could be improved, but I don't think it's desirable to have this workaround upstream. |
@emersion This is not simply fixing an error message. This fixes messages that otherwise would not be parsed at all. |
Yes. I'd rather not parse these broken messages. |
If the message cannot be parsed, better give the caller a detailed error message for easy understanding. Otherwise it’s pretty confusing and may cause some more time to figure it out. |
Yeah. I agree the error message should be more descriptive. |
go-message seems to suffer an issue which was previously discovered in perl
Mail::Header
module.https://rt.cpan.org/Public/Bug/Display.html?id=113464
The issue involves crafted messages that are usually used to transmit malware bypassing content
scanners.
The header looks like this
go-message fails to parse this returning
unexpected EOF
The text was updated successfully, but these errors were encountered: