[Mailman-Developers] Mailman can't handle MIME: Content-transfer-encoding: quoted-printable?

James Madill James.Madill@duke.edu
Wed, 13 Mar 2002 16:40:02 -0500


This is a multipart message in MIME format.
--=_alternative 0076DBCC85256B7B_=
Content-Type: text/plain; charset="us-ascii"

Users of one of my mailing lists got a nasty surprise when a posted 
message was repeatedly sent to them.

I traced the problem down to an instance of the standard End-Of-Message 
marker (a lone period on a line) in the middle of the posted message.

The posted message contained extended ASCII characters encoded using the 
MIME Content-transfer-encoding: quoted-printable format.  There was what 
appeared to be soft returns at column 72.  This message happened to have a 
paragraph that ended on column 73, so the "soft return" resulted in the 
period alone on the next line.

Sendmail accepted the encoded document for Mailman, but on sending out, 
Mailman encountered what it thought was an EOM marker and stopped the 
processing of the message at that point.  Unfortunately, there was still 
plenty of message left to send, so it was not removed from the queue, and 
Mailman kept on sending the first portion.

The smtp daemon is sendmail 8.12.1.  Mailman is version 2.0.8 with 
DELIVERY_MODULE = 'SMTPDirect' in Defaults.py.

Am I missing some Mailman switch to tell it to recognize messages with the 
Content-transfer-encoding: quoted-printable tag?

-- 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/>
--=_alternative 0076DBCC85256B7B_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Users of one of my mailing lists got a nasty surprise when a posted message was repeatedly sent to them.</font>
<br>
<br><font size=2 face="sans-serif">I traced the problem down to an instance of the standard End-Of-Message marker (a lone period on a line) in the middle of the posted message.</font>
<br>
<br><font size=2 face="sans-serif">The posted message contained extended ASCII characters encoded using the MIME Content-transfer-encoding: quoted-printable format. &nbsp;There was what appeared to be soft returns at column 72. &nbsp;This message happened to have a paragraph that ended on column 73, so the &quot;soft return&quot; resulted in the period alone on the next line.</font>
<br>
<br><font size=2 face="sans-serif">Sendmail accepted the encoded document for Mailman, but on sending out, Mailman encountered what it thought was an EOM marker and stopped the processing of the message at that point. &nbsp;Unfortunately, there was still plenty of message left to send, so it was not removed from the queue, and Mailman kept on sending the first portion.</font>
<br>
<br><font size=2 face="sans-serif">The smtp daemon is sendmail 8.12.1. &nbsp;Mailman is version 2.0.8 with DELIVERY_MODULE = 'SMTPDirect' in Defaults.py.</font>
<br>
<br><font size=2 face="sans-serif">Am I missing some Mailman switch to tell it to recognize messages with the Content-transfer-encoding: quoted-printable tag?<br>
</font><font size=3><tt><br>
-- James<br>
<br>
 &nbsp; &nbsp; &nbsp;</tt></font><font size=3 color=#b0b0b0><tt>o o o o o o o . . .</tt></font><font size=3><tt> &nbsp; </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>
 &nbsp; &nbsp;</tt></font><font size=3 color=#b0b0b0><tt>o</tt></font><font size=3><tt> &nbsp; &nbsp; &nbsp;_____ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</tt></font><font size=3 color=blue><tt>|</tt></font><font size=3 color=#ff00ff><tt>James Madill &nbsp; &nbsp; &nbsp; &nbsp; </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>&gt;</tt></font><font size=3><tt>.][__n_n_| D[ &nbsp;====|____ &nbsp;</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 &nbsp;</tt></font><font size=3 color=red><tt>|</tt></font><font size=3><tt><br>
 &nbsp;(________|__|_[____/____]_</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 &nbsp;O-O-O &nbsp;` &nbsp;oo &nbsp; &nbsp; oo &nbsp;'o^o^o &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; o^o^o` 'o^o &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; o^o`<br>
</tt></font><font size=3 color=#b0802c><tt>-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-</tt></font><font size=3><tt><br>
&lt;http://www.duke.edu/~madil001/&gt;</tt></font>
--=_alternative 0076DBCC85256B7B_=--