search

lavab / web

AngularJS web client of Lavaboom's email service
https://mail.lavaboom.com
38 stars 21 forks source link

Subject line sometimes not properly encoded #767

Closed jrselzer closed 9 years ago

jrselzer commented 9 years ago

Sorry, I have not found a way to reproduce this behaviour. Hope you have a chance to examine it anyway.

Sometimes even mails I wrote and sent with Lavaboom have broken subject lines like

=?utf-8?Q?Cryptoparty-Ank=C3=BCndigungstext?=

It actually should read "Cryptoparty-Ankündigungstext" (with a German u umlaut).

pzduniak commented 9 years ago

Here we go again, @let4be you implemented client-side encoding, right? 22 maj 2015 07:06 "jrselzer" notifications@github.com napisał(a):

Sorry, I have not found a way to reproduce this behaviour. Hope you have a chance to examine it anyway.

Sometimes even mails I wrote and sent with Lavaboom have broken subject lines like

=?utf-8?Q?Cryptoparty-Ank=C3=BCndigungstext?=

It actually should read "Cryptoparty-Ankündigungstext" (with a German u umlaut).

— Reply to this email directly or view it on GitHub https://github.com/lavab/web/issues/767.

let4be commented 9 years ago

not yet, still in todo

pzduniak commented 9 years ago

Is this a Lavaboom to Lavaboom email?

pzduniak commented 9 years ago

Ah yes, I finally understand it. lavab/web needs to support decoding of the subject lines.

let4be commented 9 years ago

Duplicate of https://github.com/lavab/web/issues/746

jrselzer commented 9 years ago

It only seems to affect Lavaboom mails going to external addresses, but I'll keep testing.