Allan Odgaard wrote: >On 18 Jun 2008, at 17:45, Mark Sapiro wrote: > >> Does a new list work OK? > >A new list show the same problem. > >> What does bin/cleanarch say about the mbox file? Did bin/arch report >> anything odd? > >I dont recall so. But since this happens both for new letters to this >list, and for a completely new list I created a few days ago, I dont >think the problem is the mbox. > >Ill see if I can get access to another Mailman version and generate >the archive from there. > >If I didnt state already, this is Mailman 2.1.9 under Ubuntu >(installed via aptitude).
I have never before seen a report like this. Since it occurs for a new list, there is apparently something wrong with the Mailman installation itself. If it were a problem with the Ubuntu package, I think it would have been seen elsewhere, so I think it's likely specific to your installation, but I have no idea what might cause it. Pipermail does threading by Message-ID and by In-Reply-To and References: headers, so assuming that those are normal and people aren't hijacking threads, I haven't a clue. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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