Fwd: [econsensus] Doesn't cope with base64 encoded email (#204)

[Jo Paulger]

Hi Tom, Nate,

This shouldn't be too hard (not for base64 specifically anyway). I've created a new ticket in the kanban for it in New Tasks for Review column so it can be prioritised.

https://aptivate.kanbantool.com/boards/5986-econsensus#tasks-3040359

Jo

---------- Forwarded message ----------
From: Hamish Downer <notifi...@github.com>
Date: 12 February 2014 14:21
Subject: [econsensus] Doesn't cope with base64 encoded email (#204)
To: aptivate/econsensus <econs...@noreply.github.com>

Recently Martin Belcher sent an email from his phone using the android email client and we ended up with a load of nonsense (see issue 409 if you have access).

The source of another email from Martin's phone is below. The message itself is base64 encoded and the headers identify itself as such. So we need to do better at dealing with random email formatting.

Return-path: <martin...@aptivate.org>
Envelope-to: ham...@aptivate.org
Delivery-date: Wed, 12 Feb 2014 13:57:34 +0000
Received: from 82-69-179-35.dsl.in-addr.zen.co.uk ([82.69.179.35]
 helo=[10.0.158.174]) by lin-mail.aptivate.org with esmtpa (Exim 4.72)
 (envelope-from <martin...@aptivate.org>) id 1WDaJi-00082s-Dv
 for ham...@aptivate.org; Wed, 12 Feb 2014 13:57:34 +0000
Date: Wed, 12 Feb 2014 10:30:54 +0000
Subject: Test mail
Message-ID: <al43eshcj0mcmxakm5y...@email.android.com>
From: Martin Belcher <martin...@aptivate.org>
To: ham...@aptivate.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

Ci0tCk1hcnRpbiBCZWxjaGVyIChBcHRpdmF0ZSkKTSArNDQgMDc3OTUgNjgxMjk5LCBNICs0NiAw
NzAzIDEzMDM1OApTa3lwZTogbWFydGluYmVsY2hlcg==

—
Reply to this email directly or view it on GitHub.