Menu
▾
▴
#2476 charset bugs
As of 1.4.5 sometimes "text/html" is misspelled as "html/plain". But the bigger issue is that when I send a "text/plain" message in UTF-8 charset then it's ok, but if I change the mime type to "text/html" (leaving the message untouched) I got junk characters. It doesn't matter wheter I use "<META...charset=utf-8;'>" in the html or not, Squirrelmail displays html UTF-8 mail wrong.
Please fix it, it's very very annoying...
Logged In: YES
user_id=285765
Originator: NO
Can you provide an example of such a message please?
I've fixed the html/plain issue, that was indeed a weird mistake. Thanks.
Logged In: YES
user_id=1638756
Originator: YES
Yes, of course. Here you are:
<HTML><HEAD><META http-equiv="Content-Type" content="text/html; charset=utf-8"></HEAD><BODY>Árvíztűrő tükörfúrógép (hungarian characters)</BODY></HTML>
And of course, in the mail header there's also a
Content-Type: text;html\n charset=utf-8\r\n
part. I will send you the full message with headers on monday, I'm not in my office today.
Logged In: YES
user_id=225877
Originator: NO
http://www.faqs.org/rfcs/rfc2045.html
5. Content-Type Header Field
Email documents are not html pages. They need correct content-type in order to display information correctly. HTML Meta header is not used in emails.
Logged In: YES
user_id=225877
Originator: NO
> Content-Type: text;html\n charset=utf-8\r\n
One more comment.
Invalid content-type header. Subtype is required and you are not setting it. Plus you mix bare linefeeds with CRLF and use html parameter which does not mean anything.
Correct message header should be.
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
If it is multipart message, message part should contain
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
Is this still an issue?
Your report was filed against an old version of SquirrelMail. We have several new releases out which have fixed many issues. Can you please test the most recent version - or even better the latest snapshot - and report if this issue still exists? Remember to include the file name of the snapshot.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).