Bug 194457 - squirrelmail cannot handle handle multibyte characters in attachment.
Summary: squirrelmail cannot handle handle multibyte characters in attachment.
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: squirrelmail
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Warren Togami
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-06-08 10:43 UTC by Issue Tracker
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: RHSA-2006-0668
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-09-26 12:26:39 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0668 0 normal SHIPPED_LIVE Moderate: squirrelmail security update 2006-09-26 04:00:00 UTC

Comment 1 Issue Tracker 2006-06-08 10:43:35 UTC
Description of problem:

After update squirrelmail to squirrelmail-1.4.6-5.el4, it can't handle
handle multibyte characters in the bese64 attachment correctly.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. accesss http://dhcp-82.brisbane.redhat.com/webmail/src/webmail.php

Actual results:
Please see Actual_results_01.png or Actual_results_02.png

Expected results:
Please see Expected_results.png

Additional info:
squirrelmail-1.4.3a-9.EL4 works fine, but the latest version can not 
treat multibyte characters in the bese64 attachment.

It seems that a bug in formatBody() of functions/mime.php.
It passes the wrong args against translateText(). 
Or $body_message->header->getParameter('charset'), it may not
work correctly.

Kind regards,

This event sent from IssueTracker by jnansi  [Support Engineering Group]
 issue 95106

Comment 9 Warren Togami 2006-06-08 16:31:38 UTC
Copied Fuchi's mail to another RHEL4 server and tried to read it in both
versions of Squirrelmail, with Japanese language mode set for the interface, and
Firefox web browser.  The results that I'm seeing indicate that even the
previous version wasn't working properly.

The garbage text where the attachment text should be viewable is encoded in
UTF-8, while the rest of the Japanese text in both the interface and body are
EUC-JP.  If you view this in either Firefox or Konqueror, you can read the
attachment text *ONLY* if you force the encoding to UTF-8.  But then you can't
read anything else on the page, because everything else is EUC-JP encoded and it
becomes garbage.

In the case of the newer squirrelmail, it does fail to display UTF-8 where the
attachment text is.

Key questions here:
1) *WHY* has the Squirrelmail web interface always been in EUC-JP?  This doesn't
match the encoding of most incoming mail (ISO-2022-JP) and it isn't UTF-8 or
ASCII compatible.
2) It appears that the "Expected result" screenshot above is using Safari.  Does
Safari behave differently in your tests from Firefox in rendering different
parts of the page in different encodings?  In my tests the browsers cannot
handle this mixed encoding display that the old version of squirrelmail did.

Comment 10 Warren Togami 2006-06-08 16:39:43 UTC
To be clear, it seems to me that between 1.4.3a and 1.4.6, the view attachment
behavior went from one broken behavior to another broken behavior.  Is this not
the case?

Comment 11 Issue Tracker 2006-06-14 04:51:16 UTC
translateText() is added new arg in test5.patch. It is not good,
since translateText() is called the other main php, like view_text.php. 

This event sent from IssueTracker by fuchi 
 issue 95106

Comment 13 Warren Togami 2006-07-10 17:24:57 UTC
Believed to be fixed in FC and this test package.

Comment 30 Red Hat Bugzilla 2006-09-26 12:26:39 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.