Bug 167877 - Squirrelmail and UTF-8 errors
Summary: Squirrelmail and UTF-8 errors
Keywords:
Status: CLOSED DUPLICATE of bug 162852
Alias: None
Product: Fedora
Classification: Fedora
Component: squirrelmail
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-09 06:19 UTC by jørgen nørgaard
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-09 22:29:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jørgen nørgaard 2005-09-09 06:19:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412.7 (KHTML, like Gecko) Safari/412.5

Description of problem:
Full user names encoded in UTF-8 (default on the system) is not encoded correctly by squirrelmail.

It becomes something like:

"From: Jørgen Nørgaard <jnp>"



Version-Release number of selected component (if applicable):
squirrelmail-1.4.6-0.cvs20050812.1.fc4

How reproducible:
Always

Steps to Reproduce:
1. Make sure fedora is using UTF-8 (LANG=UTF-8 ?)
2. Create user name with for example '�' in full name
3. Send mail via squirrelmail on this system to this system.
4. read the mail with squirrelmail
  

Actual Results:  Full name of sender is inserted UTF-8 encoded.

Squirrelmail, however, when reading the mail does interpret full sender name properly. Some clients do
interpret reasonably, though probably using guess work part of the way.

Expected Results:  Either convert full name to iso-8859 (or what ever the webserver uses) or encode the mail header so it will 
be decoded or use a heuristic to detect encoding used.

Additional info:

Comment 1 jørgen nørgaard 2005-09-09 06:22:36 UTC
The '?' in step 2 should be 'ø' (decimal 216 in iso8859-1, &oslash;)

Comment 2 Warren Togami 2005-09-09 22:29:59 UTC

*** This bug has been marked as a duplicate of 162852 ***


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