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.

Sign up for GitHub

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

Jump to bottom

Supports non UTF-8 encodings #1

Open

mooyoul opened this issue Apr 18, 2016 · 0 comments

Labels

bug

Owner

mooyoul commented Apr 18, 2016

Currently, we only supports utf-8 encoding.
If charset in Content-Type header is not UTF-8, It should be converted to UTF-8 via iconv.

Unfortunately, mailin not provides contents as Buffer.
so we cannot convert non UTF-8 encodings to UTF-8 via iconv.

I just submitted related issue into mailin project, Keep in touch with this issue.

mooyoul added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment