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
mime: expected slash after first token #140
mime: expected slash after first token #140
Conversation
Started getting emails from a particular source, that formats the inline attachment content-type like this: Resolved by just prepending a safe default mime type to it: |
Added - Inject a `application/octet-stream` as default content type when none is present (#140, thanks requaos) - Add support for content-type params to part & encoding (#148, thanks pzeinlinger) - UTF-7 support (#17) Fixed - Handle missing parameter values in the middle of the media parameter list (#139, thanks requaos) - Fix boundaryReader to respect length instead of capacity (#145, thanks dcormier) - Handle very empty mime parts (#144, thanks dcormier)
Hi guys, I also get this error Can you suggest me please how to avoid this problem ? Below is the example of mime which gives error:
|
Hey @miknaz - go ahead an open a new bug for this, I think this error is being caused by some header line continuation code, unrelated to this change. |
Found occurrences of a media parameter list without a mime type, this will inject a safe default mime type.