From 198017d1a7f188b7735dcfe699f6aab24e4b2ea7 Mon Sep 17 00:00:00 2001
From: Yury Michurin <yury@nix.co.il>
Date: Tue, 28 Oct 2014 15:03:32 +0200
Subject: [PATCH] Workaround for outlook, who doesn't like quoted-printable
 encoding

For example, outlook 2013 plus would not interpert the following html
(encoded via quoted-printable encoding):
<a href=3D=22http://engineering=
.como.com/ghost/signup/MTQxNTcwNzM5MTYwN3x5dXJ5QG5peC5jby5pbHx3NVBmUUN4RGZr=
cGhKc3FPOElybXNZNWtzR0FMTU9tRFI5UlNyRWQ4SGJZPQ=3D=3D/=22 style=3D=22color:
=

The workournd forces node-mailer to user base64, which outlook understands
well.
---
 core/server/mail.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/core/server/mail.js b/core/server/mail.js
index 51a9a23f37..e729400204 100644
--- a/core/server/mail.js
+++ b/core/server/mail.js
@@ -76,7 +76,8 @@ GhostMailer.prototype.send = function (message) {
     message = _.extend(message, {
         from: self.from(),
         to: to,
-        generateTextFromHTML: true
+        generateTextFromHTML: true,
+	encoding: 'base64' // Outlook doesn't like default 'quoted-printable' encoding inside links when the url is splited with '='
     });
 
     return new Promise(function (resolve, reject) {