John Reddy wrote: >> What exactly was the Content-Type header line ? > Here's the snippit of message header. I don't see any problem with the > line as is, this is how it exists in the message header. The mbox is > readable by mutt (my text email reader of choice). > > Content-Transfer-Encoding: binary > Content-Type: multipart/alternative; > boundary="_----------=_1136314441199510" > MIME-Version: 1.0 > > If I delete these lines from the mbox, the process will continue to the > next entry in the mbox and then it will fail with the same set of error > messages again:
How about deleteing the first line (Content-Transfer-Encoding: binary) and leave the rest. > > Content-Transfer-Encoding: binary > Content-Type: multipart/alternative; > boundary="_----------=_1136319711206230" > MIME-Version: 1.0 > > Doesn't make much sense to me why it's having trouble ingesting MIME. I believe CTE should not be in the main section of message header if Content-Type is multipart. > > -John > -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ------------------------------------------------------ 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
