Hi,



I can confirm, that the bug was fixed on Horde 3.1.2. Thanks Michael!

No - this is a different issue.
Probably.
Wait a few days, or try a snapshot of the FRAMEWORK_3 branch: 
http://snaps.horde.org/

I am sorry, but do you mean that if I upgrade to Horde 3.1.2 and IMP 
4.1.2, then that bug should be fixed? I checked changelogs for both 
Horde and IMP, it seems that only this could _maybe_ match to this bug:



(taken from Horde 3.1.2 changelog):



[mms] Fix setting default charset for non-MIME messages (Bug #3804).



Or maybe there was some fix, which isn't documented on changelogs.



Horde 3.1.2 isn't released yet, is there any place where I can download it?



Thanks

As mentioned previously in this ticket, this issue has already been 
fixed.  So unless you can reproduce using the current codebase, I am 
not quite sure what you want us to do about the issue.

No, i am using IMP 4.1.1 and Horde 3.1.1 (latest stable release).

And you are using IMP 4.1.2 and Horde 3.1.2, right?

Correct description to this bug should be: Reply and forward operation 
breaks ISO-8859-1encoded subject line, when default charset when 
reading messages preference is set to ISO-8859-1.



Screenshot from reply operation is attached.

Hi,



No this is _NOT_ duplicate of that old bug. This is new bug and has 
something to do with new feature which came in 4.1.1 (Added preference 
for default charset when reading messages.). Because if I set my 
default charset to UTF8, then subject is fine when i try to reply or 
forward a message. if I set my default charset to ISO-8859-1, then 
replying of forwarding the message breaks subject line. The message is 
fine when i am viewing it. I can sent screenshots of this, if you need 
them. The message is encoded with ISO-8859-1.



We set default charset to ISO-8859-1 when reading messages, because 
many messages has broken headers, but content of it is encoded with 
ISO-8859-1.

Verified that this works correctly in both HEAD and the latest 
FRAMEWORK_3 builds.  I remember fixing this somewhere a long time ago, 
but it is too late for me to try to figure out exactly where.  What is 
important is that it was fixed.  Marking as bogus and closing.

ISO-8859-1 encoded subject line breaks when I forward message from the 
IMP (with forward option).



Here is example of headers from working subject (so, it's not forwarded yet):



Return-Path: <xxxxxx@xxx.xx>

X-Original-To: xxxxx@security-mx.phnet.fi

Delivered-To: xxxxx@security-mx.phnet.fi

Received: from localhost (localhost [127.0.0.1])

        by security-mx2.phnet.fi (Postfix) with ESMTP id C28DD1437CC;

        Thu, 15 Jun 2006 08:06:06 +0300 (EEST)

X-Virus-Scanned: amavisd-new at security-mx2.phnet.fi

X-Spam-Score: -4.44

X-Spam-Level:

X-Spam-Status: No, score=-4.44 tagged_above=-999 required=5

        tests=[ALL_TRUSTED=-1.8, AWL=-0.793, BAYES_00=-2.599,

        HTML_MESSAGE=0.001, SARE_OBFU_ALL=0.751]

Received: from security-mx2.phnet.fi ([127.0.0.1])

        by localhost (security-mx2.phnet.fi [127.0.0.1]) (amavisd-new, port 10024)

        with LMTP id kxCnrcqDxMpP; Thu, 15 Jun 2006 08:06:03 +0300 (EEST)

Received: from inbound-mx3.phnet.fi (inbound-mx3.phnet.fi [62.165.128.110])

        by security-mx2.phnet.fi (Postfix) with ESMTP id 9E5F61437C3;

        Thu, 15 Jun 2006 08:06:03 +0300 (EEST)

Received: from mail.php.fi (mail.php.fi [62.165.176.3])

        by inbound-mx3.phnet.fi (Postfix) with ESMTP id 8789A35665B;

        Thu, 15 Jun 2006 08:06:02 +0300 (EEST)

Content-class: urn:content-classes:message

MIME-Version: 1.0

Content-Type: multipart/alternative;

        boundary="----_=_NextPart_001_01C69039.666639CD"

Subject: =?iso-8859-1?Q?VS=3A_Soittopyynt=F6_Saunalahden_ent=2E_asiakas?=

X-MimeOLE: Produced By Microsoft Exchange V6.5

Date: Thu, 15 Jun 2006 08:06:03 +0300

Message-ID: <57AC6E35AE4FA54B9891358CDFC7552F5EB876@posti5.php.fi>

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

Thread-Topic: =?iso-8859-1?Q?Soittopyynt=F6_Saunalahden_ent=2E_asiakas?=

Thread-Index: AcaN8KIi7sF4DfHxTZG6eP9a3HMApwAAGPzAAHGde5AAAmnZcAAeDnCQ

From: "Tuukka" <xxxxxx@xxx.xx>

To: "Kimmo" <xxxxx@xxxxx.xx>



Here is example of message headers from non-working subject (the 
message was forwarded from IMP):



Return-Path: <xxxxxx@xxx.xx>

X-Original-To: xxxxx@security-mx.phnet.fi

Delivered-To: xxxxx@security-mx.phnet.fi

Received: from localhost (localhost [127.0.0.1])

        by security-mx3.phnet.fi (Postfix) with ESMTP id 3BB4639E3E3

        for <xxxxx@security-mx.phnet.fi>; Thu, 15 Jun 2006 09:35:16 +0300 (EEST)

X-Virus-Scanned: amavisd-new at security-mx3.phnet.fi

X-Spam-Score: -1.314

X-Spam-Level:

X-Spam-Status: No, score=-1.314 tagged_above=-999 required=5

        tests=[AWL=-0.852, BAYES_00=-2.599, FORGED_RCVD_HELO=0.135,

        HTML_MESSAGE=0.001, RAZOR2_CHECK=1.25, SARE_OBFU_ALL=0.751]

Received: from security-mx3.phnet.fi ([127.0.0.1])

        by localhost (security-mx3.phnet.fi [127.0.0.1]) (amavisd-new, port 10024)

        with LMTP id 7++bMRWzZ7wG for <xxxxx@security-mx.phnet.fi>;

        Thu, 15 Jun 2006 09:35:14 +0300 (EEST)

Received: from inbound-mx1.phnet.fi (inbound-mx1.phnet.fi [62.165.128.128])

        by security-mx3.phnet.fi (Postfix) with ESMTP id F138139E365

        for <xxxxx@security-mx.phnet.fi>; Thu, 15 Jun 2006 09:35:12 +0300 (EEST)

Received: from outbound-mx3.phnet.fi (outbound-mx3.phnet.fi [62.165.128.248])

        by inbound-mx1.phnet.fi (Postfix) with ESMTP id 178832942EF

        for <xxxxx.liikonen@phnet.fi>; Thu, 15 Jun 2006 09:34:58 +0300 (EEST)

Received: from localhost (localhost [127.0.0.1])

        by outbound-mx3.phnet.fi (Postfix) with ESMTP id 63C80B3BD1

        for <xxxxx.liikonen@phnet.fi>; Thu, 15 Jun 2006 09:34:58 +0300 (EEST)

Received: from outbound-mx3.phnet.fi ([127.0.0.1])

  by localhost (outbound-mx3.phnet.fi [127.0.0.1]) (amavisd-new, port 10024)

  with LMTP id 13754-01-83 for <xxxxx.liikonen@phnet.fi>;

  Thu, 15 Jun 2006 09:34:58 +0300 (EEST)

Received: from webmail2.phnet.fi (webmail.phnet.fi [62.165.128.125])

        by outbound-mx3.phnet.fi (Postfix) with ESMTP id CE7A7B3BC2

        for <xxxxx.liikonen@phnet.fi>; Thu, 15 Jun 2006 09:34:57 +0300 (EEST)

Received: by webmail2.phnet.fi (Postfix, from userid 33)

        id 33DE9302920; Thu, 15 Jun 2006 09:35:03 +0300 (EEST)

Received: from dhcp-62-165-129-36.phnet.fi (dhcp-62-165-129-36.phnet.fi

        [62.165.129.36]) by webmail.phnet.fi (Horde MIME library) with HTTP; Thu,

        15 Jun 2006 09:35:03 +0300

Message-ID: <20060615093503.1qi1qtummnwgs4o8@webmail.phnet.fi>

Date: Thu, 15 Jun 2006 09:35:03 +0300

From: Kimmo <xxxxx@xxxx.xx>

To: xxxxx@xxxx.xx

Subject: Fwd: VS: =?iso-8859-1?b?U29pdHRvcHl5bnTDtg==?= Saunalahden 
ent. asiakas

MIME-Version: 1.0

Content-Type: multipart/mixed;

        boundary="=_g77mya9sfq0"

Content-Transfer-Encoding: 7bit

User-Agent: Internet Messaging Program (IMP) H3 (4.1.1)

X-Virus-Scanned: amavisd-new at outbound-mx3.phnet.fi