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
It's because the email has LF line endings, not CRLF, and we can't detect that it's safe to automatically convert them LF → CRLF.
Highly recommend switching to CRLF line endings if you can. This mostly affects test fixtures that have been saved with UNIX line endings (\n) instead of DOS line endings (\r\n). CRLF is required, but Mail has long attempted to support LF for convenience. But that results in sometimes mangling binary values, no good.
create email file mail.msg
create example file:
Actual output:
[#<Mail::Part:47308565129460, Multipart: false, Headers: <Content-Type: text/plain; charset=UTF-8>, <Content-Transfer-Encoding: 8bit>>]
Expected output:
[#<Mail::Part:47220814372500, Multipart: false, Headers: <Content-Type: text/plain; charset=UTF-8>, <Content-Transfer-Encoding: 8bit>>, #<Mail::Part:47220814403800, Multipart: false, Headers: <Content-Type: text/html; charset=UTF-8>, <Content-Transfer-Encoding: quoted-printable>>]
Due to ’ in the text/plain part of the mail, gem doesn't parse email correctly
The text was updated successfully, but these errors were encountered: