[2013-11-21 02:23 UTC] paul+mlmmj at fariello dot eu
Description:
------------
OpenSMTPD is masking data with 0x7f when mail are not coming with the
8BITMIME flag. And it seems that mlmmj is not using the 8BITMIME EHLO command when sending mail to the list. So it ends up with messy characters like "C'" instead of "ç".
Test script:
---------------
Delivered-To: mlmmj-test@example.org
Received: from example.org (example.org [192.168.0.1]);
by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e;
for <mlmmj-test@example.org>;
Tue, 28 Nov 2013 05:30:32 +0100 (CET)
Date: Tue, 28 Nov 2013 05:30:31 +0100
From: Paul Fariello <paul@example.org>
To: mlmmj-test@example.org
Subject: [Test] test
Message-ID: <20131105093031.GM11270@example.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20131105091721.GB11270@example.org>
ça va ?
Expected result:
----------------
Delivered-To: mlmmj-test@example.org
Received: from example.org (example.org [192.168.0.1]);
by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e;
for <mlmmj-test@example.org>;
Tue, 28 Nov 2013 05:30:32 +0100 (CET)
Date: Tue, 28 Nov 2013 05:30:31 +0100
From: Paul Fariello <paul@example.org>
To: mlmmj-test@example.org
Subject: [Test] test
Message-ID: <20131105093031.GM11270@example.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20131105091721.GB11270@example.org>
ça va ?
Actual result:
--------------
Delivered-To: mlmmj-test@example.org
Received: from example.org (example.org [192.168.0.1]);
by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e;
for <mlmmj-test@example.org>;
Tue, 28 Nov 2013 05:30:32 +0100 (CET)
Date: Tue, 28 Nov 2013 05:30:31 +0100
From: Paul Fariello <paul@example.org>
To: mlmmj-test@example.org
Subject: [Test] test
Message-ID: <20131105093031.GM11270@example.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20131105091721.GB11270@example.org>
C'a va ?
Description: ------------ OpenSMTPD is masking data with 0x7f when mail are not coming with the 8BITMIME flag. And it seems that mlmmj is not using the 8BITMIME EHLO command when sending mail to the list. So it ends up with messy characters like "C'" instead of "ç". Test script: --------------- Delivered-To: mlmmj-test@example.org Received: from example.org (example.org [192.168.0.1]); by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e; for <mlmmj-test@example.org>; Tue, 28 Nov 2013 05:30:32 +0100 (CET) Date: Tue, 28 Nov 2013 05:30:31 +0100 From: Paul Fariello <paul@example.org> To: mlmmj-test@example.org Subject: [Test] test Message-ID: <20131105093031.GM11270@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131105091721.GB11270@example.org> ça va ? Expected result: ---------------- Delivered-To: mlmmj-test@example.org Received: from example.org (example.org [192.168.0.1]); by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e; for <mlmmj-test@example.org>; Tue, 28 Nov 2013 05:30:32 +0100 (CET) Date: Tue, 28 Nov 2013 05:30:31 +0100 From: Paul Fariello <paul@example.org> To: mlmmj-test@example.org Subject: [Test] test Message-ID: <20131105093031.GM11270@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131105091721.GB11270@example.org> ça va ? Actual result: -------------- Delivered-To: mlmmj-test@example.org Received: from example.org (example.org [192.168.0.1]); by example.org (OpenSMTPD) with ESMTPSA id 2e35f84e; for <mlmmj-test@example.org>; Tue, 28 Nov 2013 05:30:32 +0100 (CET) Date: Tue, 28 Nov 2013 05:30:31 +0100 From: Paul Fariello <paul@example.org> To: mlmmj-test@example.org Subject: [Test] test Message-ID: <20131105093031.GM11270@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131105091721.GB11270@example.org> C'a va ?