Wrong formatting - Githubissues

Emails received from Github are not formatted correctly. I have no problem with other emails. The content of email displayed is only --> -->. The same content is displayed if I open the email in a new window. Here's the email source :
Date: Sun, 10 Jan 2016 10:50:57 -0800
From: Klaus Post <notifications@github.com>
Reply-To: ncw/rclone <reply+00097f66d396c74578fdca44547b7bc6debfaf7e0dea4e2192cf0000000112aa6a1192a169ce0772f8e6@reply.github.com>
To: ncw/rclone <rclone@noreply.github.com>
Cc: Axtux <axtux__AT__hotmail.com>
Message-ID: <ncw/rclone/pull/277/c170381594@github.com>
In-Reply-To: <ncw/rclone/pull/277@github.com>
References: <ncw/rclone/pull/277@github.com>
Subject: Re: [rclone] Add support of multiple hash types per object. (#277)
Content-Type: multipart/alternative;
    boundary="--==_mimepart_5692a8114e49c_3d3f3fc9fe3e32a0798182";
    charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-MS-Exchange-Organization-Network-Message-Id: 66462cef-7ed8-4bad-4eee-08d319ef02f6
X-EOPAttributedMessage: 0
X-MS-Exchange-Organization-MessageDirectionality: Incoming
CMM-sender-ip: 192.30.252.197
CMM-sending-ip: 192.30.252.197
CMM-Authentication-Results: hotmail.com; spf=pass (sender IP is
 192.30.252.197; identity alignment result is pass and alignment mode is
 relaxed) smtp.mailfrom=noreply@github.com; dkim=pass (testing mode; identity
 alignment result is pass and alignment mode is relaxed) header.d=github.com;
 x-hmca=pass header.id=notifications@github.com
CMM-X-SID-PRA: notifications@github.com
CMM-X-AUTH-Result: PASS
CMM-X-SID-Result: PASS
CMM-X-Message-Status: n:n
CMM-X-Message-Delivery: Vj0xLjE7dXM9MTtsPTE7YT0xO0Q9MTtHRD0xO1NDTD0w
CMM-X-Message-Info: NhFq/7gR1vQRHV6jbdvQfsTNt0cTeuyZqTLW6AmJ6Y3apdeBVHl5DlqBJeAjVylVTOqebKhSh+AN7+4sWGcg+mizgxjDo01/PLdA50wrXihvWXgjRD7sbZlWcbgu7KEpRO4DckZNGr+L5mEdunUg2zRl03eUEbE6+mIB+nXxuy4bKiUnvH3c8cDX3jYW7crbDU5g0QZLqTX6DI0tXm5UcVLlPOqe0DqbPyX1/coozs05yr2KvHy82g==
X-MS-Exchange-Organization-PCL: 2
X-Forefront-Antispam-Report: CIP:25.152.0.56;CTRY:GB;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(98900002);DIR:INB;SFP:;SCL:1;SRVR:DB3PR04MB0844;H:SNT004-MC2F16.hotmail.com;FPR:;SPF:None;LANG:en;
X-Microsoft-Exchange-Diagnostics:
    1;DB3PR04MB0844;2:IgWh1r4aoXX3MCJKsgUJO/53HIR+JbwXTyFsjRLWyptenQ2LljO99d2oUP+KLw6p8Wfpo+YOLL3FEg1MkW9CVbjkFSOYLwrcKaaZKX3vZFG/HBlTp3u6mr1qgx8oFEuT518SriWVJdZbXJG0qQECicJ0E3NWGmDhR2mvsu2YPUPfSm+YQ7n++8dNJ535e/SJ;3:i0clmxPRJKjCvoDzfjkfsFHRMTDihtrbLwz5vtUPVh8wda2VWriHtKIO5gCAhHIDGjZ5R7m5v7GTajM8RpvUPlz5eUS5bQuFT1Wjyipdl7W5IaXQP8sCkE9MWh5je+nAxKj/kE8/fzgoFiVpn3wqJfE3LKVgbvd3dAerYwLqpgQDll6/OjN/1mIpA4gl86z5WkATEjXz8OgKaAg/zRNs8g==;25:yad5bGaWrchV/aFVclvChCCOErf8AeMQ3rT/pt4H91JcX5kLgD9YDQrRQetcFLwQuXlMlwYyixZxJRpEE9NT08OcIW3qGzDxD8JMQCqXvjW1+8mgj1jc7H0KepUPnm7NAVL0SeTZiNBhsYEnxrtT0XgDJf/p0u/oli7xmnvsTJniK9APUK3YXoZ1dhiPOB/vSFYiqKrPtWIULANK5MBNSQATeLXyrm3b6t9uB9sLAw78qs8vfL60CORjJL3gDPlc;4:Q5izjyEsWCNnnBUyn7m8Szmnox8qGnvNq22tTAIsCJkzh2jpRIs9V32w9t6tdgLM/oXwK902oDRaVUn06pSps1B7WRJqzzOmUibYeg3FSAYWSvxJwxos2ED3+KzXpZMYxhTGx7NWNEfNcgmHRlq0IChG6RbKqy4Ux9eJcHPUGagm+Mkw+bQWiS7QFF+qTqFs2K37QBBzOz5LKWtzDmxtK+eepQKWqqDW+VILRYd4h1aTIYKNKeWly4PLRzuhvFnpYnm/noIlei/mv3PQDb9RHg==
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(8291501001);SRVR:DB3PR04MB0844;
X-MS-Office365-Filtering-Correlation-Id: 66462cef-7ed8-4bad-4eee-08d319ef02f6
X-MS-Exchange-Organization-AVStamp-Service: 1.0
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(82015046);SRVR:DB3PR04MB0844;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB0844;
X-MS-Exchange-Organization-SCL: 1
X-Microsoft-Exchange-Diagnostics: 1;DB3PR04MB0844;23:+2rM28SR0N9rWv+wEw3+iFMEggO/lGgvumhC+untQoRrGMgWknjYcMPWtiFErrLi7psCUNfF31UQcfiYt5jU64urYkrX2J9kUtmmUIwKcz+iKPwcTWkmIhPooRCo1TayxPT5F3+TpjIYsLwaym9WmXBu8KS367FRAn1dcyJlsOaEG8saepIA5R1fBlDe6E/B;5:U2U2qO7Ix9nTtJG0naP3N2YEELRLplMYIEiSUUw0jd3ozPoc8nlj4gJHMSAJG1RasPjq/GFSYHPrWwSQnJanWSWbmtQ6704ddr+O22BHwMuAyeo42xBBmHpsOF1pobj7iN8cWZ6jDTWvm9HbzopDpw==;24:o+8zhj/QhRQ5sBxr9RZTuc/jjjuAOBpZFLcSkS6asxows43SeFwlEE3iNi2v0i2swzZSjQnAD4QQDVueZj+4SsNVZsTWbbJq8AauztK1oKs=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jan 2016 18:51:11.4289
 (UTC)
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR04MB0844
X-MS-Exchange-Organization-AuthSource: HE1EUR01FT009.eop-EUR01.prod.protection.outlook.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Transport-EndToEndLatency: 00:00:02.3890633
MIME-Version: 1.0

----==_mimepart_5692a8114e49c_3d3f3fc9fe3e32a0798182
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

>Hash calculation on these files couldn't even be done within 24h.

Hash calculation is done while the objects are being uploaded right now (even without this PR). If the destination supports hashing, the destination is checked. This functionality is kept as is. The only change is that SHA1 is also being calculated, so SHA-1 destination can check the hash.

The hash cache will not change any existing functionality. The only difference is that if the hash is calculated for a file, we store it, so if the hash is needed some time in the future we don't keep to recalculate. In effect this would allow you to use hashes (`--checksum`) for your backup without recalculating hashes for all your unmodified files.

---
Reply to this email directly or view it on GitHub:
https://github.com/ncw/rclone/pull/277#issuecomment-170381594
----==_mimepart_5692a8114e49c_3d3f3fc9fe3e32a0798182
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><blockquote>
<p>Hash calculation on these files couldn't even be done within 24h.</p>
</blockquote>

<p>Hash calculation is done while the objects are being uploaded right now (even without this PR). If the destination supports hashing, the destination is checked. This functionality is kept as is. The only change is that SHA1 is also being calculated, so SHA-1 destination can check the hash.</p>

<p>The hash cache will not change any existing functionality. The only difference is that if the hash is calculated for a file, we store it, so if the hash is needed some time in the future we don't keep to recalculate. In effect this would allow you to use hashes (<code>--checksum</code>) for your backup without recalculating hashes for all your unmodified files.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/ncw/rclone/pull/277#issuecomment-170381594">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AAl_ZvEJx8MDsJvXbpwEvoYwf3j4Sxc3ks5pYp-RgaJpZM4G-2Ni.gif" width="1"></p>
<div itemscope="" itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope="" itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/ncw/rclone/pull/277#issuecomment-170381594"><!-- </link> -->
  <meta itemprop="name" content="View Pull Request"><!-- </meta> -->
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"><!-- </meta> -->
</div>

----==_mimepart_5692a8114e49c_3d3f3fc9fe3e32a0798182--
RainLoop / rainloop-webmail

Wrong formatting #923
