4 Commits

Author	SHA1	Message	Date
Guo Xiang Tan	c7c8f38eac	Use proper encoding for email fixtures.	2018-02-21 17:06:35 +08:00
Sam	e456ae1b6c	Revert "Upgrade mail gem to drop dependency on mime-types." ... This reverts commit 498cc15aa9. Noticed a certain amount of extra allocations due to this upgrade, reverting to confirm if this is the case	2018-02-16 07:04:22 +11:00
Guo Xiang Tan	498cc15aa9	Upgrade mail gem to drop dependency on mime-types. ... Boot Memory Usage ``` Total allocated: 225695379 bytes (1990663 objects) Total retained: 32795116 bytes (291607 objects) ``` ``` Total allocated: 218342892 bytes (1897350 objects) Total retained: 30123426 bytes (261198 objects) ```	2018-02-15 16:24:26 +08:00
Claus Strasburger	e9bb9a167b	Fix reply-by-mail for 8-bit transfer encodings ... The mail class seems to handle mails sent with Content-Transfer-Encoding: 8bit somewhat weirdly: It decodes them (to utf-8), changes the raw source to base64, and does not modify the Content-Type:charset= header. This leads to Discourse trying the message encoding (in my example ISO-8859-1) first, and if that does not contain any unparseable characters, it uses that. Sadly, in ISO-8859-1, every byte sequence is valid. Fix this by always trying to decode as UTF-8 first. The probability of someone using another encoding that cleanly (but wrongly) decodes as UTF-8 should be fairly low.	2017-04-30 23:30:40 +02:00