[Mailman-Users] Inappropriate nesting of threads.

[Mark Sapiro]

Chris Malme wrote:
>
>I've discovered that for every "-" in the MessageID, that message is moved
>one place across in the nesting of threads. As his MessageID can contain up
>to 5 "-" characters, this means any thread he participates in gets messed up
>somewhat.


Good work. It took me quite a bit of effort to figure that one out,
even after I knew which bad Debian patch caused it.

[...]
>Before I do so, or begin to experiment, I thought I would ask if this is a
>known problem with a existing solution?


It is a known problem caused by another bad Debian patch. See some of
the gory details in the post at
<http://mail.python.org/pipermail/mailman-users/2009-July/066610.html>
and related posts.

The cure is to replace the debian patch with the one at
<http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1186>.

(That URL is currently returning "internal server error". This is
generally a temporary Launchpad condition which will correct itself.
If you can't get the patch, let me know and I'll send it.)

The bad Debian patch takes statements similar to

            myThreadKey = parent.threadKey + article.date + '-'

in five places in pipermail.py and replaces "article.date + '-'" with
"article.date + '/' + article.msgid + '-'".

The correct fix is to replace "article.date + '/' + article.msgid +
'-'" in the Debian patch with "article.date + '.' +
str(article.sequence) + '-'".

Or, you can go to
<http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head%3A/Mailman/Archiver/pipermail.py>
and look at the 5 groups of one or two lines marked revision 1186.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan