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

Transfer encoding not preserved #87

Open
singpolyma opened this issue Jul 29, 2010 · 2 comments
Open

Transfer encoding not preserved #87

singpolyma opened this issue Jul 29, 2010 · 2 comments

Comments

@singpolyma
Copy link
Contributor

I have a hash representing a MIME message (headers and :body) and when I feed it to Mail.new() it mostly works, except that when I call .encoded on the new message, all the content-transfer-encodings get changed. I would be very very nice if the octets in the body of Mail.new(str).encoded were the same as the octets in the body part of str

@mikel
Copy link
Owner

mikel commented Sep 11, 2010

Can you please provide a failing spec for this with the expected behaviour?

@jeremy
Copy link
Collaborator

jeremy commented Jan 23, 2017

This would be really nice, but we're a ways off from that. By design, the library does a fair bit of normalization during parsing and we can't recall everything about the original message. Good target to pursue, but removing the milestone.

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