You are correct. This was SuSE Linux 10.1, which appears to be 2.1.7 with a lot of patches.
I went ahead and installed 2.1.9 and it seemed to resolve the issue. I'm guessing the problem was RFC-2231 file names that spanned multiple lines. The outbound message had REALLY long file names. Once I installed 2.1.9, the person was able to send the message. Mark Sapiro wrote: > Tokio Kikuchi wrote: > >> George Sexton wrote: >> >> >>> When the IncomingRunner dies, the new message appears in the qfiles/in >>> folder with an extension of .bak. I've tried deleting and re-creating >>> the list and it still dies. If I remove the .bak message and re-start >>> Mailman, then any queued messages are sent or discarded. >>> >> I've filed a bug report and a patch in the sourceforge tracker. >> http://sourceforge.net/tracker/index.php?func=detail&aid=1598087&group_id=103&atid=100103 >> >> It may not apply cleanly to the 2.1.7 version but the point is deleting >> lines starting from 'except...' and to the next 'try:' line. >> >> The errorneous messages should be shunted and you can check them in >> qfiles/shunt directory. >> > > > Two things: > > If this is really 2.1.7, it is someones package with 2.1.9 backports, > because .bak files in qfiles directories were only implemented in > 2.1.9. > > I disagree with Tokio about how to fix this. I have attached a comment > and an alternative patch to Tokio's bug report. > > -- George Sexton MH Software, Inc. Voice: +1 303 438 9585 URL: http://www.mhsoftware.com/ ------------------------------------------------------ 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
