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[ ====|____ |[EMAIL PROTECTED]| | (919) 286-6384 |
(________|__|_[____/____]_|_____________________|_|_________________|
_/oo O-O-O ` oo oo 'o^o^o o^o^o` 'o^o o^o`
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
<http://www.duke.edu/~madil001/>
| [EMAIL PROTECTED] (Barry A. Warsaw)
Sent by: [EMAIL PROTECTED] 03/14/02 18:30
|
To: "James Madill" <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [Mailman-Users] Re: [Mailman-Developers] Mailman can't handle MIME: Content-transfer-encoding: quoted-printable? |
>>>>> "JM" == James Madill <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
