Skip to content
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

Support Content-Transfer-Encoding or more MimeHeaders #75

Open
schmitch opened this issue Nov 9, 2015 · 2 comments
Open

Support Content-Transfer-Encoding or more MimeHeaders #75

schmitch opened this issue Nov 9, 2015 · 2 comments

Comments

@schmitch
Copy link
Contributor

schmitch commented Nov 9, 2015

Hello, currently it would be great if we would have more options in specifing Mime Data.

I think the only way to handle that as good as possible would be a more loose mime field which would just append the necessary Bytes.
Like a List[(String, String)] or something which will be appended without validation

@ggrossetie
Copy link
Member

Could you provide a use case for this ?

@schmitch
Copy link
Contributor Author

schmitch commented Dec 7, 2015

Mostly for Content-Transfer-Encoding. Currently It's not possible to specify base64 as a content-transfer-encoding, also I'm not sure if there are any more useful headers which couldn't be specified yet, so maybe a more "loose" would help here.

As I remember there way a MD5 Header and I think a alternative content header.

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

No branches or pull requests

3 participants