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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: