[Mailman-Users] mailman 2.1.5 subject line problem

[Mark Sapiro]

Rimgaudas Laucius wrote:
>
>Exactly!!! Mailman has nothing to do with message. It gets correct coded message with only ASCII characters and it needs only forward it to mailing list participants, but it rejects. And problem is that it scans message subject and if finds ?windows goes madden. 
>I want to note that many people uses windows coding and you could not force them all to switch to ISO. 
>

Previously you wrote:
>
>It only an example with windows-1275 (sic) 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 work also.We still think problem is in Mailman and exclusively in 2.1.5 version because ealier version worked well. 
>

Now you seem to be saying that if you specify iso-8859-13 as the
characterset of your message, Mailman accepts and delivers it, but if
you specify windows-1257 Mailman discards the message.

Which is it?

If messages are being discarded solely because they specify
windows-1257 charset and not if they specify iso-8859-13, then this
would seem to be a Mailman bug.

I have done some testing with Mailman 2.1.4 (haven't upgraded to 2.1.5
yet) and I can't duplicate your problem. If I send a post with an
8-bit character in the subject (not encoded), the Bcc: I send myself
comes back with the raw 8-bit character in the subject and the list
post coms back with the subject encoded as:

Subject: [Test]
=?iso-8859-1?q?trying_to_screw_it_up_-=3E=C0=3C-_bad_char?=
	=?iso-8859-1?q?acter?=

I don't know if Mailman or some MTA along the way did this.

Likewise if I send a post with your example windows-1257 subject, i.e.

Subject: =?windows-1257?Q?=E0=FEe=E1=F8=EB=E6=FB?=

the Bcc: comes back the same, but the list post comes back with the
quoted-printable encoding changed to base64, i.e.

Subject: [Test] =?windows-1257?b?4P5l4fjr5vs=?=

and the subject appears to be properly rendered in Baltic characters in
the lists archive.

Have you looked at the Mailman error log to see if there is anything
there for the discarded posts?

If in fact, Mailman is discarding properly encoded messages, then this
would appear to be a bug that should be reported at
http://sourceforge.net/tracker/?group_id=103&atid=100103 (note that
there is already a possibly related bug report at
http://sourceforge.net/tracker/index.php?func=detail&aid=965706&group_id=103&atid=100103

--
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan