Martin Sebald wrote:
Hello Tomas!
>> after I turned on lossy encoding in SquirrelMail configuration the
>> umlaut problem was solved for most mails. But I experienced that in some
>> mails it does not work. Instead of scambled umlauts like ?? instead of ?
>> I now see questionmarks instead of every umlaut in the reply field.
>> I noticed that in the original mail the header just shows:
>>> Content-type: text/plain
>> and not like in other mails where it works something like this:
>>> Content-Type: text/plain;
>>> charset="iso-8859-1"
>>> Content-Transfer-Encoding: quoted-printable
>>> Content-Language: de
>> Is it possible that the missing of a charset (I don't think that it
>> makes a difference if the charset is iso-8859 or utf-8) and the other
>> information given screws up SquirrelMail?
> Are these emails displayed correctly?
Yes. I see all umlauts when opening these mails in SquirrelMail. The
questionmarks just appear when replying or forwarding.
Are you sure that we are talking about some plain text emails and not about html formated emails?
Have you installed view_as_html plugin?
Martin Sebald wrote:
> Do they have a MIME-Version header?
No. Nothing.
Most of those mails are mails from robots like contact forms so I believe
that the authors of those programs did not care about correct mail headers.
Though most mail clients like TheBat! are able to reply without crambling
the umlauts. So it seems to be possible.
There you go. One of the most common RFC 2045 violations. If MIME-Version header is not set, RFC 2045 complaint software should ignore Content-Type headers.
Most email clients have their own email structure parsers and some of them apply incorrect default charset or ignore RFC2045 chapter 4 violation. SquirrelMail asks IMAP server to parse email structure. Any sane parser would check for MIME-Version before reading whole email and wouldn't waste time in processing of email structure, when this header is missing. RFC 2045 says that header is required. If header is missing, email is not formated according to RFC 2045 and should be handled as plain text email in US-ASCII charset.
Ask developers of those buggy web forms to fix their scripts.
--
Tomas
