[Tickets #3302] NEW: IMAP Header Problem!!

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3302
-----------------------------------------------------------------------
 Ticket             | 3302
 Created By         | masud.sp at gmail.com
 Summary            | IMAP Header Problem!!
 Queue              | IMP
 Version            | 4.0.4
 State              | Unconfirmed
 Priority           | 3. High
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


masud.sp at gmail.com (2006-01-19 01:15) wrote:

Hi,

  Bestpratcile RT system generated mail header is not correctly parse by
IMP, First I though its RT issue then I sent the same header field to
gmail,hotmail,yahoo,squirrelmail but faced no problem. So here it goes

  /*This is the first header which IMP is unable to parce*/
Date: Wed, 18 Jan 2006 23:52:35 -0500
Managed-BY: RT 3.4.1 (http://www.bestpractical.com/rt/)
MIME-Version: 1.0
Subject: Re: [xxxx #1388] Test
In-Reply-To: <rt-1388 at xxxx>
RT-Ticket: xxx #1388
Precedence: bulk
Content-Type: text/plain; charset="iso-8859-1"
Reply-To: xxxxx at xxxxxxx.com
Message-ID: <rt-3.4.1-1388-20063-5.10.2604802650428 at xxxxxxx.com>
X-RT-Loop-Prevention: APDC
Content-Transfer-Encoding: 8-bit
RT-Originator: xxxxx at xxxxxx.com
From: "MM via RT" <xxxxx at xxxxxxx.com>
X-RT-Original-Encoding: utf-8
To: undisclosed-recipients:;


This email text is not visible in header.
.
/**************************************************/
 I we send this type of header in Mail, IMP consider is as type
[application/octet-stream] Thats quite strange to me, I tries adding
[application/octet-stream] in text/plain and show online and I though i
patched it some how but unfortunately I was wrong. As on clicking REPLY it
wount show the quoted text , And why should it show! as IMP is still not
considering it as [text/plan].

  I did a little digging and findout that IMP parser for header cannot parse
this 
Content-Transfer-Encoding: 8-bit
  If we make it 
Content-Transfer-Encoding: 8bit 
 omiting (-) between 8 and bit then it work fine so need fixing. (urgent) Me
my self try to achive this fixing and let see.

Masood