From: Dirk E. S. <ds...@ca...> - 2005-04-20 17:31:13
|
I am not sure if this is a Squirrelmail issue: I use squirellmail 1.4.4 with postfix, MailScanner, cyrus-imap, apache2 on SuSE 9.2. 1) Mails from certain mail clients don't include a Content-Type: header, characters get displayed wrong. 2) Mails from yahoo accounts show Content-Type:text/plain; charset=us-ascii and won't display correctly. 3) Mails sent from squirrelmail or kmail get displayed correctly. When I read the same mail with twig, another webmail-client, mails get displayed correct! (http://twig.screwdriver.net). I tried setting the default language to en_US, default charset to iso-8859-1 in config.php, doesn't change the bahaviour. Any help is appreciated. Enrique -- Dirk Enrique Seiffert CaribeNet S.A. - Cartagena - Colombia www.caribenet.com |
From: Tomas K. <to...@us...> - 2005-04-20 17:45:44
|
> I am not sure if this is a Squirrelmail issue: > > I use squirellmail 1.4.4 with postfix, MailScanner, cyrus-imap, apache2 on > SuSE 9.2. > > 1) Mails from certain mail clients don't include a Content-Type: header, > characters get displayed wrong. How are you suppose to transfer 8bit information? Ask certain email clients to follow rfc and inform about charset that is used for 8bit information. > 2) Mails from yahoo accounts show Content-Type:text/plain; > charset=us-ascii and won't display correctly. us-ascii is 7bit charset. it should not contain any 8bit information. If email states that it is in us-ascii, squirrelmail 1.4.4 treats it as ascii and ascii decoding function removes all 8bit information. > 3) Mails sent from squirrelmail or kmail get displayed correctly. > > When I read the same mail with twig, another webmail-client, mails get > displayed correct! (http://twig.screwdriver.net). > > I tried setting the default language to en_US, default charset to > iso-8859-1 > in config.php, doesn't change the bahaviour. $default_charset does not apply to emails. It applies only to interface charset and it is ignored in most of cases in order to avoid misconfiguration of interface. -- Tomas |
From: Dirk E. S. <ds...@ca...> - 2005-04-20 20:08:37
|
El Mi=C3=A9 20 Abr 2005 13:47, Tomas Kuliavas escribi=C3=B3: > > I am not sure if this is a Squirrelmail issue: > > > > I use squirellmail 1.4.4 with postfix, MailScanner, cyrus-imap, apache2 > > on SuSE 9.2. > > > > 1) Mails from certain mail clients don't include a Content-Type: header, > > characters get displayed wrong. > > How are you suppose to transfer 8bit information? Ask certain email > clients to follow rfc and inform about charset that is used for 8bit > information. > > > 2) Mails from yahoo accounts show Content-Type:text/plain; > > charset=3Dus-ascii and won't display correctly. > > us-ascii is 7bit charset. it should not contain any 8bit information. If > email states that it is in us-ascii, squirrelmail 1.4.4 treats it as ascii > and ascii decoding function removes all 8bit information. > I did some more testing: I have two mailservers running, both with=20 squirrelmail, twig, apache2 (and MailScanner). mail1 runs sendmail and UoW= =20 Imap. mail2 runs postfix and Cyrus-Imap. A mail sent from yahoo to accounts= =20 on both servers displays fine on mail1: In squirrellmail as well as twig. O= n=20 mail2 it displays body correctly in twig but not in squirrelmail. So this=20 doesn't seem to be a squirrelmail issue. Anyhow: Any idea where to find -o= r=20 even search- the solution is appreciated. Thanks Enrique =2D-=20 Dirk Enrique Seiffert CaribeNet S.A. - Cartagena - Colombia www.caribenet.com |
From: Tomas K. <to...@us...> - 2005-04-21 07:55:10
|
> El Mié 20 Abr 2005 13:47, Tomas Kuliavas escribió: >> > I am not sure if this is a Squirrelmail issue: >> > >> > I use squirellmail 1.4.4 with postfix, MailScanner, cyrus-imap, >> apache2 >> > on SuSE 9.2. >> > >> > 1) Mails from certain mail clients don't include a Content-Type: >> header, >> > characters get displayed wrong. >> >> How are you suppose to transfer 8bit information? Ask certain email >> clients to follow rfc and inform about charset that is used for 8bit >> information. >> >> > 2) Mails from yahoo accounts show Content-Type:text/plain; >> > charset=us-ascii and won't display correctly. >> >> us-ascii is 7bit charset. it should not contain any 8bit information. If >> email states that it is in us-ascii, squirrelmail 1.4.4 treats it as >> ascii >> and ascii decoding function removes all 8bit information. >> > I did some more testing: I have two mailservers running, both with > squirrelmail, twig, apache2 (and MailScanner). mail1 runs sendmail and UoW > Imap. mail2 runs postfix and Cyrus-Imap. A mail sent from yahoo to > accounts > on both servers displays fine on mail1: In squirrellmail as well as twig. > On > mail2 it displays body correctly in twig but not in squirrelmail. So this > doesn't seem to be a squirrelmail issue. Anyhow: Any idea where to find > -or > even search- the solution is appreciated. SquirrelMail version numbers? php version numbers? php mbstring.func_overload setting? any modifications made to vanilla SquirrelMail? message MIME-Version, Content-Type and Content-Transfer-Encoding headers? if message is multipart - message part headers? display html by default setting value? (Options -> Display Prefs) Used SquirrelMail translation? -- Tomas |
From: Dirk E. S. <ds...@ca...> - 2005-04-21 16:46:18
|
> > I did some more testing: I have two mailservers running, both with > > squirrelmail, twig, apache2 (and MailScanner). mail1 runs sendmail and > > UoW Imap. mail2 runs postfix and Cyrus-Imap. A mail sent from yahoo to > > accounts > > on both servers displays fine on mail1: In squirrellmail as well as twig. > > On > > mail2 it displays body correctly in twig but not in squirrelmail. So this > > doesn't seem to be a squirrelmail issue. Anyhow: Any idea where to find > > -or > > even search- the solution is appreciated. Sorry for not beeing more specific and thanks for your patience. > SquirrelMail version numbers? 1.4.4 > php version numbers? 4.3.8 > php mbstring.func_overload setting? ;mbstring.func_overload = 0 less /etc/php.ini |grep mbstring extension=mbstring.so [mbstring] ;mbstring.language = Japanese mbstring.internal_encoding = UTF-8 ;mbstring.http_input = auto ;mbstring.http_output = SJIS ; mbstring.internal_encoding setting. Input chars are ;mbstring.encoding_translation = Off ;mbstring.detect_order = auto ;mbstring.substitute_character = none; ; overload(replace) single byte functions by mbstring functions. ;mbstring.func_overload = 0 ; With mbstring support this will automatically be converted into the encoding ; given by corresponding encode setting. When empty mbstring.internal_encoding > any modifications made to vanilla SquirrelMail? I added some translations. > message MIME-Version, Content-Type and Content-Transfer-Encoding headers? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NO Content-Transfer-Encoding header > if message is multipart - message part headers? No multipart > display html by default setting value? (Options -> Display Prefs) Text, tested also with HTML > Used SquirrelMail translation? es_ES, some plugin translations are modified by me. I also tested with the default en_US. Did make no difference. My second Squirellmail instaltion (that encodes corectly) has the same configuration but squirellmail 1.4.3, no custom translations, no additional plugins. Thanks again for your ideas! Enrique > > -- > Tomas > > > ------------------------------------------------------- > This SF.Net email is sponsored by: New Crystal Reports XI. > Version 11 adds new functionality designed to reduce time involved in > creating, integrating, and deploying reporting solutions. Free runtime > info, new features, or free trial, at: > http://www.businessobjects.com/devxi/728 -- Dirk Enrique Seiffert CaribeNet S.A. - Cartagena - Colombia www.caribenet.com |
From: Tomas K. <to...@us...> - 2005-04-21 17:04:02
|
> >>> I did some more testing: I have two mailservers running, both with >>> squirrelmail, twig, apache2 (and MailScanner). mail1 runs sendmail and >>> UoW Imap. mail2 runs postfix and Cyrus-Imap. A mail sent from yahoo to >>> accounts on both servers displays fine on mail1: In squirrellmail as >>> well as twig. >>> On mail2 it displays body correctly in twig but not in squirrelmail. So >>> this doesn't seem to be a squirrelmail issue. Anyhow: Any idea where to >>> find >>> -or >>> even search- the solution is appreciated. > Sorry for not beeing more specific and thanks for your patience. >> SquirrelMail version numbers? > 1.4.4 >> php version numbers? > 4.3.8 >> php mbstring.func_overload setting? > ;mbstring.func_overload = 0 ... i have asked only about one mbstring thing that can break things. >> any modifications made to vanilla SquirrelMail? > I added some translations. >> message MIME-Version, Content-Type and Content-Transfer-Encoding >> headers? > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > NO Content-Transfer-Encoding header >> if message is multipart - message part headers? > No multipart >> display html by default setting value? (Options -> Display Prefs) > Text, tested also with HTML >> Used SquirrelMail translation? > es_ES, some plugin translations are modified by me. I also tested with the > default en_US. Did make no difference. > > My second Squirellmail instaltion (that encodes corectly) has the same > configuration but squirellmail 1.4.3, no custom translations, no > additional plugins. functions/decode/us_ascii.php remove that file or ask yahoo to mark messages with correct charset. "The only languages that can comfortably be written with the repertoire of US-ASCII happen to be Latin, Swahili, Hawaiian and American English without most typographic frills. It is rumoured that there are more languages in the world." http://czyborra.com/charsets/iso646.html -- Tomas |
From: Dirk E. S. <ds...@ca...> - 2005-04-21 19:31:53
|
El Jue 21 Abr 2005 13:05, Tomas Kuliavas escribi=C3=B3: This solved: > > functions/decode/us_ascii.php > > remove that file or ask yahoo to mark messages with correct charset. =46ollowed the first recomendation as I don't expect yahoo to be afraid of = me.=20 But they are aware of the problem. On their help site they say: "Certain=20 messages encoded with character sets other than US-ASCII don't display=20 correctly. Some characters which aren't used in English will appear correct= ly=20 because they are either part of the character set or are in a format called= =20 "quoted printable." Your outgoing messages are currently encoded with a=20 US-ASCII character set. We hope to add foreign character support in the nea= r=20 future." Thanks a LOT! Best wishes Enrique =2D- Dirk Enrique Seiffert CaribeNet S.A. - Cartagena - Colombia www.caribenet.com |