some escaping issue?

[huglester]

Hello again :)

I have spotted one more problem.
For example I get this email to mailhog:

to reset your password, please click <a href=3D"http://sentinel=
.app/change_password/13/2eVJjEic4h5oui6h2lJ8gzl9mdC4qzXQ">this link.</a>.=

it is the source. the soruce itself is the same in both mailcatcher and mailhog, but the HTML rendered in mailhog is currupt.

For example link ir not change_password but change password (without underscore)

Here are the headers from mailhog:

Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=utf-8
Date: Mon, 04 May 2015 09:53:14 +0000
From: CRM <[email protected]>
MIME-Version: 1.0
Message-ID: [email protected]
Received: from sentinel.app by mailhog.example (Go-MailHog)
          id [email protected]; Mon, 04 May 2015 12:53:14 +0300
Return-Path: <[email protected]>
Subject: Reset your account password.
To: [email protected]

Here are the headers from mailcatcher:

Message-ID: <[email protected]>
Date: Mon, 04 May 2015 09:53:40 +0000
Subject: Reset your account password.
From: CRM <[email protected]>
To: [email protected]
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Not sure what else I can post :(

Thanks!

[ian-kent]

Thanks @huglester - is this is the same as #41? I'll try to reproduce using your message content, haven't been able to so far.

[ian-kent]

I think this is fixed now - RFC2047 encoding was replacing a "_" with a " " before decoding, which is correct when applied to headers, but not the message body.

Please reopen if it hasn't been fixed 😄

[huglester]

Hello,

yes it is fixed now!:)