Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-09-02 Thread Brad Knowles
At 2:04 PM -0400 2004-09-02, David Relson quoted Brad Knowles: For Mailman 2.1.5, you need Python 2.3 or higher. See . AFAICT, Rimgaudaus is reporting that subject "=?windows-1257?Q?=E0=FEe=E1=F8=EB=E6=FB?=" worked fi

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-09-02 Thread David Relson
On Thu, 2 Sep 2004 15:40:13 +0200 Brad Knowles wrote: > At 5:16 PM +0200 2004-09-01, Rimgaudas Laucius wrote: > > > But now i see that it is related only to windows encoding (with > > other encodings: ISO, UTF is all right) and i guess it is not > > python problem because i have installed 2.2.

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-09-02 Thread Brad Knowles
At 5:16 PM +0200 2004-09-01, Rimgaudas Laucius wrote: But now i see that it is related only to windows encoding (with other encodings: ISO, UTF is all right) and i guess it is not python problem because i have installed 2.2.1 version. For Mailman 2.1.5, you need Python 2.3 or higher. See

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-09-01 Thread Mark Sapiro
Rimgaudas Laucius wrote: > >i am sorry i was not very consistent describing problem because i was >looking at the problem from the user point at first. That is why i said that >mailman does not pass letters with national characters in subject line. I >was not talking about encoded letter's source.

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-09-01 Thread Rimgaudas Laucius
Hello, i am sorry i was not very consistent describing problem because i was looking at the problem from the user point at first. That is why i said that mailman does not pass letters with national characters in subject line. I was not talking about encoded letter's source. After i investigeted se

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-08-30 Thread Tokio Kikuchi
Hi, We have tested source text of the message sent from our MUA. The subject field was =?windows-1257?Q?=E0=FEe=E1=F8=EB=E6=FB?= So, all characters in ASCII and this mesaage did not go through Mailman. So the problem is not in MUA. What version of Python are you using ? In Python2.1, 'windows-12

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-08-30 Thread Larry Stone
On 8/30/04 7:31 AM, Brad Knowles at [EMAIL PROTECTED] wrote: > At 3:24 PM +0200 2004-08-30, Rimgaudas Laucius wrote: > >> It only an example with windows-1275 cp. The same result if i code letter >> with iso-8859-13. (i tried to switch on quoted printable and Base 64 >> coding but it does not

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-08-28 Thread Mark Sapiro
Rimgaudas Laucius wrote: > >i installed mailman 2.1.5 on Linux (rh9). >The problem is with letters where are used national characters (8 bit >[#128..#255] from baltic cp Windows 1257 or ISO-13) in subject line. >Mailman does not pass such letters (discards them without any message). >Earlier ve

Re: [Mailman-Users] mailman 2.1.5 subject line problem

2004-08-28 Thread Mark Sapiro
Mark Sapiro wrote: > >RFC2822 section 2.2 says in part: > > Header fields are lines composed of a field name, followed by a colon > (":"), followed by a field body, and terminated by CRLF. A field > name MUST be composed of printable US-ASCII characters (i.e., > characters that have values bet

[Mailman-Users] mailman 2.1.5 subject line problem

2004-08-28 Thread Rimgaudas Laucius
Hello, i installed mailman 2.1.5 on Linux (rh9). The problem is with letters where are used national characters (8 bit [#128..#255] from baltic cp Windows 1257 or ISO-13) in subject line. Mailman does not pass such letters (discards them without any message). Earlier version (2.0.14) had not s

[Mailman-Users] mailman 2.1.5 subject line problem

2004-08-28 Thread Rimgaudas Laucius
Hello, i installed mailman 2.1.5 on Linux (rh9). The problem is with letters where are used national characters (8 bit [#128..#255] from baltic cp Windows 1257 or ISO-13) in subject line. Mailman does not pass such letters (discards them without any message). Earlier version (2.0.14) had not s