> 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.
The question marks are what the lossy encoding does when it finds encoding
that doesn't make sense in the context.
> 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?
SquirrelMail depends on the meta data specified in the RfCs to be there.
If it's not, SquirrelMail has to make a guess how the sender of the mail
intended the information to be structured. So yes, I think you've come to
the right conclusion.
Possible ways to go:
1. Fix the broken mailer.
2. Make a plugin with a great guessing algorithm and install it (and share
it with the rest of us).
Sincerely,
Fredrik
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects-----
squirrelmail-plugins mailing list
Posting guidelines:
http://squirrelmail.org/postingguidelinesList address:
squirrelmail-plugins@...
List archives:
http://news.gmane.org/gmane.mail.squirrelmail.pluginsList info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins
