[Mailman-Users] Re: [Mailman-Developers] Mailman can't handle MIME: Content-transfer-encoding: quoted-printable?
James Madill
James.Madill@duke.edu
Fri, 15 Mar 2002 09:35:38 -0500
This is a multipart message in MIME format.
--=_alternative 004FFE6E85256B7D_=
Content-Type: text/plain; charset="us-ascii"
Notes, the originating Mailer of the message in question is also
ESMTP. My MTA, sendmail 8.12.1, is an ESMTP mailer, and able to correctly
handle a lone period on a line in the middle of an E-mail message. What
MTA does Mailman use when DELIVERY_MODULE is set to 'SMTPDirect'? Internal
code?
I think that what is happening is that the MTA that Mailman is
talking to is not told that ESMTP should be used. In doing so, when
Mailman writes out to the MTA, the MTA sees the EOM marker and stops
accepting data for that message.
-- James
o o o o o o o . . . _______________________ _______=======_T___
o _____ |James Madill | |Duke Univ Med Ctr|
>.][__n_n_| D[ ====|____ |james.madill@duke.edu| | (919) 286-6384 |
(________|__|_[____/____]_|_____________________|_|_________________|
_/oo O-O-O ` oo oo 'o^o^o o^o^o` 'o^o o^o`
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
<http://www.duke.edu/~madil001/>
barry@zope.com (Barry A. Warsaw)
Sent by: mailman-users-admin@python.org
03/14/02 18:30
To: "James Madill" <James.Madill@duke.edu>
cc: mailman-developers@python.org, Mailman-Users@python.org
Subject: [Mailman-Users] Re: [Mailman-Developers] Mailman can't handle MIME:
Content-transfer-encoding: quoted-printable?
>>>>> "JM" == James Madill <James.Madill@duke.edu> writes:
JM> Sendmail accepted the encoded document for Mailman, but on
JM> sending out, Mailman encountered what it thought was an EOM
JM> marker and stopped the processing of the message at that
JM> point. Unfortunately, there was still plenty of message left
JM> to send, so it was not removed from the queue, and Mailman
JM> kept on sending the first portion.
>>>>> "BG" == Ben Gertzfield <che@debian.org> writes:
BG> Mailman 2.1 has an entirely re-written infrastructure for MIME
BG> message handling, and likely has fixed this bug (the old
BG> quoted-printable module had some serious flaws and has been
BG> re-written).
BG> If you could send us a copy of the naughty message, we could
BG> test it with Mailman 2.1 from CVS and let you know if the bug
BG> has been fixed, but I'll bet that it has been fixed now.
I'd still be very surprised if this ends up being a Mailman problem.
Python strings don't care at all about end-markers, NULs, etc. so you
can't put something in a string that would cause Python to shorten
it. And Mailman just uses the file object's read() method to suck the
message in from disk, and that just reads the whole file. On writing,
Mailman will hand the whole string over to the smtplib module, which
itself just blasts the whole thing down the socket connection.
I'm much more suspicious of the MTA or some other intermediary
bolluxing something up.
-Barry
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
--=_alternative 004FFE6E85256B7D_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif"> Notes, the originating Mailer of the message in question is also ESMTP. My MTA, sendmail 8.12.1, is an ESMTP mailer, and able to correctly handle a lone period on a line in the middle of an E-mail message. What MTA does Mailman use when DELIVERY_MODULE is set to 'SMTPDirect'? Internal code?</font>
<br>
<br><font size=2 face="sans-serif"> I think that what is happening is that the MTA that Mailman is talking to is not told that ESMTP should be used. In doing so, when Mailman writes out to the MTA, the MTA sees the EOM marker and stops accepting data for that message.<br>
</font><font size=3><tt><br>
-- James<br>
<br>
</tt></font><font size=3 color=#b0b0b0><tt>o o o o o o o . . .</tt></font><font size=3><tt> </tt></font><font size=3 color=blue><tt>_______________________</tt></font><font size=3><tt> </tt></font><font size=3 color=red><tt>_______=======_</tt></font><font size=3><tt>T</tt></font><font size=3 color=red><tt>___</tt></font><font size=3><tt><br>
</tt></font><font size=3 color=#b0b0b0><tt>o</tt></font><font size=3><tt> _____ </tt></font><font size=3 color=blue><tt>|</tt></font><font size=3 color=#ff00ff><tt>James Madill </tt></font><font size=3 color=blue><tt>|</tt></font><font size=3><tt> </tt></font><font size=3 color=red><tt>|</tt></font><font size=3 color=#00aa00><tt>Duke Univ Med Ctr</tt></font><font size=3 color=red><tt>|</tt></font><font size=3><tt><br>
</tt></font><font size=3 color=#f0c02c><tt>></tt></font><font size=3><tt>.][__n_n_| D[ ====|____ </tt></font><font size=3 color=blue><tt>|</tt></font><font size=3 color=#ff00ff><tt>james.madill@duke.edu</tt></font><font size=3 color=blue><tt>|</tt></font><font size=3><tt> </tt></font><font size=3 color=red><tt>|</tt></font><font size=3 color=#00aa00><tt> (919) 286-6384 </tt></font><font size=3 color=red><tt>|</tt></font><font size=3><tt><br>
(________|__|_[____/____]_</tt></font><font size=3 color=blue><tt>|_____________________|</tt></font><font size=3><tt>_</tt></font><font size=3 color=red><tt>|_________________|</tt></font><font size=3><tt><br>
_/oo O-O-O ` oo oo 'o^o^o o^o^o` 'o^o o^o`<br>
</tt></font><font size=3 color=#b0802c><tt>-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-</tt></font><font size=3><tt><br>
<http://www.duke.edu/~madil001/></tt></font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>barry@zope.com (Barry A. Warsaw)</b></font>
<br><font size=1 face="sans-serif">Sent by: mailman-users-admin@python.org</font>
<p><font size=1 face="sans-serif">03/14/02 18:30</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: "James Madill" <James.Madill@duke.edu></font>
<br><font size=1 face="sans-serif"> cc: mailman-developers@python.org, Mailman-Users@python.org</font>
<br><font size=1 face="sans-serif"> Subject: [Mailman-Users] Re: [Mailman-Developers] Mailman can't handle MIME: Content-transfer-encoding: quoted-printable?</font></table>
<br>
<br>
<br><font size=2><tt><br>
>>>>> "JM" == James Madill <James.Madill@duke.edu> writes:<br>
<br>
JM> Sendmail accepted the encoded document for Mailman, but on<br>
JM> sending out, Mailman encountered what it thought was an EOM<br>
JM> marker and stopped the processing of the message at that<br>
JM> point. Unfortunately, there was still plenty of message left<br>
JM> to send, so it was not removed from the queue, and Mailman<br>
JM> kept on sending the first portion.<br>
<br>
>>>>> "BG" == Ben Gertzfield <che@debian.org> writes:<br>
<br>
BG> Mailman 2.1 has an entirely re-written infrastructure for MIME<br>
BG> message handling, and likely has fixed this bug (the old<br>
BG> quoted-printable module had some serious flaws and has been<br>
BG> re-written).<br>
<br>
BG> If you could send us a copy of the naughty message, we could<br>
BG> test it with Mailman 2.1 from CVS and let you know if the bug<br>
BG> has been fixed, but I'll bet that it has been fixed now.<br>
<br>
I'd still be very surprised if this ends up being a Mailman problem.<br>
Python strings don't care at all about end-markers, NULs, etc. so you<br>
can't put something in a string that would cause Python to shorten<br>
it. And Mailman just uses the file object's read() method to suck the<br>
message in from disk, and that just reads the whole file. On writing,<br>
Mailman will hand the whole string over to the smtplib module, which<br>
itself just blasts the whole thing down the socket connection.<br>
<br>
I'm much more suspicious of the MTA or some other intermediary<br>
bolluxing something up.<br>
<br>
-Barry<br>
<br>
------------------------------------------------------<br>
Mailman-Users mailing list<br>
Mailman-Users@python.org<br>
http://mail.python.org/mailman/listinfo/mailman-users<br>
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py<br>
</tt></font>
<br>
<br>
--=_alternative 004FFE6E85256B7D_=--