utf8-encoded mails do not work properly

[dpeuscher]

When trying to send utf8-mails the =?utf8-Prefix is not interpreted and the whole mail looks broken in the web interface (see screenshot)

[ian-kent]

Go-MailHog doesn't currently have support for RFC2047

It should be relatively simple to add - I'll have a look as soon as I have time!

[ian-kent]

Should be supported in v0.05

[dpeuscher]

Tanks for the quick fix.
The quoted-printable Content-transfer-encoding is still not applied (RFC2047 4.2)

[ian-kent]

Would have expected it to work but I'll have another look, could you give an example if you have one?

[dpeuscher]

I copied the plain-text part of the source of a mail. Again I removed sensitive information (also in the screenshot), but it should work and you get the idea.

Content-Type: multipart/related; boundary="=_5568e411f788fcdf459e23c74d8edcb1"
Date: Mon, 03 Nov 2014 14:51:53 +0100
From: =?utf-8?Q?CHECK24=20Vergleichsportal=20Fl=C3=BCge=20GmbH?= <[sender-mail]>
MIME-Version: 1.0
Message-ID: 5457888483f9576ef9000001@flug.c24
Received: from  by flug.c24 (Go-MailHog)
          id 5457888483f9576ef9000001@flug.c24; Mon, 03 Nov 2014 13:52:04 +0000
Reply-To: =?utf-8?Q?CHECK24=20Vergleichsportal=20Fl=C3=BCge=20GmbH?= <[sender-mail]>
Return-Path: <[sender-mail]>
Subject: =?utf-8?Q?Dominik=20empfiehlt:=20Flug=20=20Frankfurt=20-=20?= =?utf-8?Q?M=C3=BCnchen=20(04.11.14=20-=2007.11.14)=20f=C3=BCr=20266=2C30=E2=82=AC?=
To: [receiver-mail]

This is a message in Mime Format.  If you see this, your mail reader does not support this format.

--=_5568e411f788fcdf459e23c74d8edcb1
Content-Type: multipart/alternative;
 boundary="=_dd660fc148b4c2388d23415b8501c7b6"
Content-Transfer-Encoding: 8bit


--=_dd660fc148b4c2388d23415b8501c7b6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

=0ADominik empfhielt Ihnen ein Angebot auf flug.check24.de=0A=0ADominik=
 sagt: Test123=0AMit einem Klick auf die =E2=80=9EAngebot pr=C3=BCfen=E2=
=80=9C-Url k=C3=B6nnen Sie jederzeit komfortabel und unverbindlich das A=
ngebot aufrufen.=0ANeben dem aktuellen Angebot zeigen wir Ihnen zahlreic=
he weitere verf=C3=BCgbare Flug-Angebote zum aktuellen Preis=0A=0APreis:=
 266,30  Euro=0A=0AFlugverbindung:=0AFrankfurt - M=C3=BCnchen am 04.11.2=
014 14:15h - 15:15h mit Lufthansa=0AM=C3=BCnchen - Frankfurt am 07.11.20=
14 21:00h - 22:05h mit Lufthansa=0A=0AAngebot pr=C3=BCfen: =0A=0A=0AStand 03.11.2014 14:51Uhr; Achtung: Flugpreise k=C3=
=B6nnen sich kurzfristig =C3=A4ndern.=0ADieser Angebotsservice wurde an=
 [receiver-mail] gesendet.    Sie erhalten diesen Angebotsse=
rvice von CHECK24, weil Ihnen das Angebot mobil empfohlen wurde.=0A=0ACH=
ECK24 Vergleichsportal Fl=C3=BCge GmbH=0ANikolaistrasse 28-32=0A04109 Le=
ipzig=0AGesch=C3=A4ftsf=C3=BChrer: =0A=0AE-Ma=
il: [sender-mail]=0ASitz der Gesellschaft: Leipzig=0A=0AHRB 27688=0AUs=
t. IdNr.: DE282585516=0A=0A=0AAGB der CHECK24 Vergleichsportal Fl=C3=BCg=
e GmbH: =0ADatenschutzhinweise CHECK24 Vergleichsportal Fl=C3=BCge GmbH

[ian-kent]

Thanks @dpeuscher - I think that's covered in RFC2045, RFC2047 refers to the message headers.

It should be fairly straightforward, I'll have a look when I get a chance!

[ian-kent]

Will be fixed with #9