That sounds very much like a problem I just corrected. The receiving end was behind a Cisco PIX firewall and a bug in the PIX causes this. Search Google groups for sendmail + multiple +pix for the complete story.
Al At 04:40 PM 3/13/2002 -0500, James Madill wrote: >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[ ====|____ |[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/> _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
