6.0.0-beta1
7/26/25

[#14493] IMP not display messages with Content-Transfer-Encoding: 8bit
Summary IMP not display messages with Content-Transfer-Encoding: 8bit
Queue IMP
Queue Version 6.2.16
Type Bug
State Not Reproducible
Priority 1. Low
Owners
Requester alex (at) sinitsyn (dot) ru
Created 10/21/2016 (3200 days ago)
Due
Updated 02/01/2017 (3097 days ago)
Assigned 10/26/2016 (3195 days ago)
Resolved 02/01/2017 (3097 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/01/2017 09:35:11 AM Jan Schneider State ⇒ Not Reproducible
 
10/31/2016 09:48:54 AM Jan Schneider Comment #4 Reply to this comment
This doesn't add any information and doesn't change anything to what I said.
10/30/2016 07:21:38 AM alex (at) sinitsyn (dot) ru Comment #3
New Attachment: q1.png Download
Reply to this comment
IMP works perfectly fine with those messages. There must be some 
other factor that causes this problem.
Ok. Some test. Here is two screenshot. On first I select non 8 bit 
content-transfer-encoding message. Message loaded and displayed.
On other, I select 8 bit content-transfer-encoding message. Message 
not loading, on message view I see previously selected message, and 
"loading icon" always spin.
Headers from messages included.

-- Message 1
Return-Path: <sinitsa@olma.ru>
Delivered-To: <sinitsa@olma.ru>
Received: from mx.olma.ru
        by mx (Dovecot) with LMTP id vbSwNQR7Cli6WAAAG/5Uzw
        for <sinitsa@olma.ru>; Fri, 21 Oct 2016 23:33:03 +0300
Return-path: <sinitsa@olma.ru>
Received: from klms.olma.ru ([10.123.123.156])
        by mx.olma.ru with esmtp (Exim 4.63)
        (envelope-from <sinitsa@olma.ru>)
        id 1bxgUx-0006B1-Nz
        for sinitsa@olma.ru; Fri, 21 Oct 2016 23:33:03 +0300
Received: from [109.197.29.67] (helo=XelasMac.local)
        by mx.olma.ru with esmtpsa (TLSv1:AES128-SHA:128)
        (Exim 4.63)
        (envelope-from <sinitsa@olma.ru>)
        id 1bxgUx-0006At-FH; Fri, 21 Oct 2016 23:33:03 +0300
To: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0KHQuNC90LjRhtGL0L0=?= <alexey@sinitsyn.ru>
From: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0KHQuNC90LjRhtGL0L0=?= <sinitsa@olma.ru>
Subject: test
Message-ID: <0aeebc52-8a5e-d68a-f1af-7738fda51170@olma.ru>
Date: Fri, 21 Oct 2016 23:33:03 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
  Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

-- Messsage 2
Return-Path: <sinitsa@olma.ru>
Delivered-To: <sinitsa@olma.ru>
Received: from mx.olma.ru
        by mx (Dovecot) with LMTP id jZw9D/oZB1hJJgAAG/5Uzw
        for <sinitsa@olma.ru>; Wed, 19 Oct 2016 10:00:35 +0300
Return-path: <sinitsa@olma.ru>
Received: from klms.olma.ru ([10.123.123.156])
        by mx.olma.ru with esmtp (Exim 4.63)
        (envelope-from <sinitsa@olma.ru>)
        id 1bwkrb-0002aF-OA
        for sinitsa@olma.ru; Wed, 19 Oct 2016 10:00:35 +0300
Received: from [10.123.123.129] (helo=xelasnote.local)
        by mx.olma.ru with esmtpsa (TLSv1:AES128-SHA:128)
        (Exim 4.63)
        (envelope-from <sinitsa@olma.ru>)
        id 1bwkrb-0002Zv-1x; Wed, 19 Oct 2016 10:00:35 +0300
To: Gleb <gleb@olma.ru>, Max Petrov <mxp@olma.ru>, dronin@olma.ru
From: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0KHQuNC90LjRhtGL0L0=?= <sinitsa@olma.ru>
Subject: =?UTF-8?B?INCb0L7Qs9C40L3Riw==?=
Message-ID: <f16bd312-6d8a-e978-29a7-cccb2316a520@olma.ru>
Date: Wed, 19 Oct 2016 10:00:34 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
  Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
10/26/2016 09:09:16 AM Jan Schneider Comment #2
Priority ⇒ 1. Low
State ⇒ Feedback
Reply to this comment
IMP works perfectly fine with those messages. There must be some other 
factor that causes this problem.
10/21/2016 08:45:01 PM alex (at) sinitsyn (dot) ru Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ IMP not display messages with Content-Transfer-Encoding: 8bit
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
IMP not display messages with Content-Transfer-Encoding: 8bit.
If select another message with, for example, 
Content-Transfer-Encoding: base64, then message displaing properly.

Saved Queries