"xxx character set is not supported" errors may appear when you switch to some
translations. This usually means that your IMAP server does not support charset
that is used by translation.
Error can be disabled by setting following SquirrelMail options to false:
4. General Options -> 11. Allow server thread sort (it is not enabled by
default)
4. General Options -> 12. Allow server-side sorting (not enabled by
default)
4. General Options -> 13. Allow server charset search (enabled by
default)
There is one exception. If you are using Turkish translation, you can get
similar errors even when your IMAP server supports ISO-8859-9 charset. This
happens due to different small letters to capital letters conversion rules in
Turkish. See
SM bug No.690625 and
http://www.topolis.lt/squirrelmail/turkish.html for more details.
If you are using SquirrelMail on Linux RedHat v7.3 system, sometimes you can get
error:
Warning: Invalid range end in /usr/share/squirrelmail/functions/i18n.php on line
xx
Problem can be reproduced only on RedHat 7.3 or RedHat Advanced Server 2.0. It
happens only if UTF-8 enabled glibc locale is used. this means - ca_ES, cs_CZ,
da_DK, en_CA, es_ES, es_US, et_EE, fi_FI, hr_HR, is_IS, lt_LT, lv_LV, no_NO,
pl_PL, sl_SI are affected. Emails that produce warnings use other encoding than
is set in user's locale.
The problem is in broken glibc, apache or php patches used by RH. System doesn't
like regexp ranges at \237-\240 (octal numbers). decimal 159-160. Latest
SquirrelMail versions tries to avoid this error.