On 2018-11-24 15:52, Richard Damon wrote:
On 11/24/18 10:24 AM, André Rodier wrote:
On 2018-11-24 15:16, Richard Damon wrote:
On 11/24/18 9:41 AM, André Rodier wrote:
Hello,
I have a program (SOGo), installed on my mail server, that send
emails
using the quoted-printable encoding for From/To headers.
Unfortunately, none of the email clients I use seems to display them
correctly:
-------------------------------------------------------
From =?utf-8?q?Andr=C3=A9?= Rodier <[email protected]>
To =?utf-8?q?Andr=C3=A9?= Rodier <[email protected]>
-------------------------------------------------------
Is there any reason for that ?
is a header missing:
Thanks for your help
André Rodier
First, are your clients compliant with the RFC that define encoding
of
headers (which are later/less supported than those that define the
encoding of the body)?
For example, RFC 2047 (I think the latest RFC that defines this
encoding). I don't think you need any header to enable this support,
just a compliant MUA.
Thanks for your answer.
I would think it is a bug in the SOGo software, because other emails
are using quoted-printable too, but are displayed correctly, for
instance this one:
------------------------------------------------------------------------
Return-Path: <[email protected]>
Received: from osaka.rodier.me
by osaka.office.pmc with LMTP id 0P2UH/1p+VvAFAAAnYgw/w
; Sat, 24 Nov 2018 15:10:53 +0000
Received: from osaka.rodier.me (localhost [127.0.0.1])
by osaka.rodier.me (Postfix) with ESMTP id 6406A2063B
for <[email protected]>; Sat, 24 Nov 2018 15:10:53 +0000 (GMT)
Received: by osaka.rodier.me (Postfix, from userid 132)
id 431B720662; Sat, 24 Nov 2018 15:10:53 +0000 (GMT)
Content-Type: text/html; charset="utf-8"
To: =?utf-8?q?Andr=C3=A9_Rodier?= <[email protected]>
MIME-Version: 1.0
Date: Sat, 24 Nov 2018 15:10:53 +0000
Subject: The event =?utf-8?q?=22Hello=22?= was created
Message-ID: <1403-5bf96a00-5-79d0b280@98295310>
From: =?utf-8?q?Andr=C3=A9_Rodier?= <[email protected]>
X-AV-Checked: ClamSMTP (Client IP: 127.0.0.1)
------------------------------------------------------------------------
Fortunately, Thunderbird, Evolution and Roundcube are behaving the
same.
I use Thunderbird myself, and your message displays fine. The one
difference I see is that the character set and encoding in your mail
client is coming in upper case, while the example has it in lower case.
I thought the RFC said that this was case insensitive, but maybe some
implementations are case sensitive.
I forgot to mention something important. The first copied line are a
copy as they are displayed in the email client.
The raw headers:
------------------------------------------------------------------------
Return-Path: <[email protected]>
Received: from osaka.rodier.me
by osaka.office.pmc with LMTP id mE3/EPJu+VtmHgAAnYgw/w
; Sat, 24 Nov 2018 15:32:02 +0000
Received: from osaka.rodier.me (localhost [127.0.0.1])
by osaka.rodier.me (Postfix) with ESMTP id 2CE4920664
for <[email protected]>; Sat, 24 Nov 2018 15:32:02 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by osaka.rodier.me (Postfix) with ESMTP id 0E6432063B
for <[email protected]>; Sat, 24 Nov 2018 15:32:02 +0000 (GMT)
To: =?utf-8?q?=3D=3Futf-8=3Fq=3FAndr=3DC3=3DA9=3F=3D_Rodier?=
<[email protected]>
X-Priority: 1
Subject: test
Importance: high
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <25d7-5bf96ef1-1-7d77729b@234960090>
Content-Type: text/plain; charset="utf-8"
From: =?utf-8?q?=3D=3Futf-8=3Fq=3FAndr=3DC3=3DA9=3F=3D_Rodier?=
<[email protected]>
Date: Sat, 24 Nov 2018 15:32:01 +0000
User-Agent: SOGo Alarms Notifier/1.0
X-AV-Checked: ClamSMTP (Client IP: 127.0.0.1)
------------------------------------------------------------------------
So, yes, the message is encoded twice...
--
https://github.com/progmaticltd/homebox
--
[email protected]
https://inverse.ca/sogo/lists
