db262fa81f
this bump includes a change to show line ending characters are treated when processing mail. standard email line ending is \r\n and prior to 2.7.0, this was automatically converted back to \n when decoding a message part. however, in some cases this could corrupt images, and so that conversion is no longer happening. see: https://github.com/mikel/mail/pull/1113 this means that message replies that become discussion or conversation replies will have the \r\n line ending in them. we could restore the previous behavior be manually calling `::Mail::Utilities.to_lf` in incoming mail processor when we pull the decoded message parts, but everything should work just fine with the different line ending. closes COMMS-620 test plan: - regression test incoming mail processing - smoke test outgoing mail Change-Id: I349c3e70b08ecb84ef92e597762c48708d52e800 Reviewed-on: https://gerrit.instructure.com/136259 Reviewed-by: Rob Orton <rob@instructure.com> Tested-by: Jenkins QA-Review: Aaron Kc Hsu <ahsu@instructure.com> Product-Review: Simon Williams <simon@instructure.com> |
||
|---|---|---|
| .. | ||
| fixtures | ||
| incoming_mail_processor | ||
| spec_helper.rb | ||