Re: [SM-USERS] which mail format

2007-07-03 Thread Res
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message On Sun, 1 Jul 2007, Paul Lesniewski wrote: >> Perhaps WV trained under DJB :) > > I'd actually give the silver medal to Sam Varshavchik (Courier). > Maybe the gold. Not had much conversation with

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Petr Hroudny
> > Now I hit reply or forward, Compose window appears and the HTML source > > shows this: > > > > test �ťĞť�ĞżýŞ > > > > Tested in both Firefox 2.0.0.4 and IE6. > > > > Definitely a Squirrelmail problem. > > Yes. But having unsupported characters in html form does not violate RFC > 2046.

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Tomas Kuliavas
>> > Nope. It's squirrelmail which is doing that (on replies and forwards). >> > Just try this: >> > >> > 1) send yourself email in UTF-8 >> > 2) try to reply/forward this email using Czech language settings >> > (iso-8859-2) >> > >> > At the moment when Compose window comes up, all the quoted text

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Petr Hroudny
> > Nope. It's squirrelmail which is doing that (on replies and forwards). > > Just try this: > > > > 1) send yourself email in UTF-8 > > 2) try to reply/forward this email using Czech language settings > > (iso-8859-2) > > > > At the moment when Compose window comes up, all the quoted text from >

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Tomas Kuliavas
> 2007/7/3, Tomas Kuliavas <[EMAIL PROTECTED]>: >> > Since Squirrelmail inserts characters from other charset into a >> > message body declared as being in iso-8859-2, it definitely violates >> > the RFC and causes problems to recipients of such emails. >> >> SquirrelMail does not insert characters

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Petr Hroudny
2007/7/3, Tomas Kuliavas <[EMAIL PROTECTED]>: > > Since Squirrelmail inserts characters from other charset into a > > message body declared as being in iso-8859-2, it definitely violates > > the RFC and causes problems to recipients of such emails. > > SquirrelMail does not insert characters from o

Re: [SM-USERS] Squirrelmail heavilly violating RFC2046

2007-07-03 Thread Tomas Kuliavas
> After yesterday's discussion and some tests it's now clear that > Squirrelmail heavily violates RFC2046 when left in default > configuration ($lossy_encoding = false). > > With this default setting, replies/forwards to messages with > non-identical charset are improperly formatted like this (exa

Re: [SM-USERS] Problem replying or forwarding for non-ISO-8859-2 mesages

2007-07-03 Thread Daniel Watts
Tomas Kuliavas wrote: >> I installed Squirrelmail 1.4.10a and selected Czech language. All >> incoming mail is displayed fine, but when I try to reply to or forward >> mail which is not in ISO-8859-2 codepage, the quoted text is broken. >> >> When the message is in ISO-8859-2, replying/forwarding i