You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dealing with spam you find lots of malformed messages like some missing the final boundary in multipart messages.
In cases like this the parser returns an encapsulated EOF error like so multipart: NextPart: EOF from
That is hard to detect in the calling code. It would be better to have a named error instead like missing boundary which can be detected in calling code because the message is actually parsed so the error should not fail the whole process
The text was updated successfully, but these errors were encountered:
When dealing with spam you find lots of malformed messages like some missing the final boundary in multipart messages.
In cases like this the parser returns an encapsulated EOF error like so
multipart: NextPart: EOF
fromgo-message/textproto/multipart.go
Line 262 in b27fd96
That is hard to detect in the calling code. It would be better to have a named error instead like missing boundary which can be detected in calling code because the message is actually parsed so the error should not fail the whole process
The text was updated successfully, but these errors were encountered: