On 6/7/2007 9:03 AM Tokio Kikuchi said the following: > 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. Removing the Content-Transfer-Encoding header doesn't resolve the problem. Only removing the Content-Type header does. It's not that the mails suddenly changed. We have dozens of mailing lists with mbox files going back a couple of years. It's just that I've been looking into this recently and just noticed it.
-John -- John Reddy [EMAIL PROTECTED] (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs ------------------------------------------------------ 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
