>>>>> "F" == Fil <[EMAIL PROTECTED]> writes:
>> I see no double-encoding. You can see no double encoding in
>> this message's subject too!
F> We ought to compare what's in the qfiles/in/ directory. If it's
F> the same in both installations, but is spitted out bad by mine
F> and correctly by yours, it must be in 'email' (or in the way
F> Mailman calls 'email'). Am I right?
Yes. Let's start from a common starting point so we can eliminate
other tools. I'm using Python 2.2 here, and the following script to
inject the message into a mailing list:
-------------------- snip snip --------------------
import smtplib
MAILHOST = 'localhost'
MAILPORT = 25
MYLIST = 'CHANGEME'
ME = 'CHANGEME'
s = smtplib.SMTP()
s.connect(MAILHOST, MAILPORT)
s.sendmail(ME, [MYLIST], '''\
To: %s
Subject: =?iso-8859-1?B?6eA=?=
From: %s
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
���������
����������
�����������
��������
���������
��������
��������
��������
��������
��������
��������
''' % (MYLIST, ME))
s.close()
-------------------- snip snip --------------------
So I run this and I end up with a message in my qfiles/in with the
following Subject:
Subject: =?iso-8859-1?B?6eA=?=
Now I run "bin/qrunner -o -r Incoming" once and I end up with files in
qfiles/archive (ignore these) and two in qfiles/out. bin/dumpdb on
the qfiles/out/*.pck file and I get the following Subject: header:
Subject: [Postal] =?iso-8859-1?B?6eA=?=
Just as I expected.
Now run "bin/qrunner -o -r Outgoing", the message disappears from my
queue and shows up in my inbox, with the exact same Subject: as
expected.
What happens for you?
-Barry
_______________________________________________
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers
