Barry Finkel wrote:

The bug report (dated 4 Nov 2002) states:

Hi, pipermail screws up threading in case that two messages
which were sent at the same time both start a new thread.
New messages to either thread are then only listed below.

The problem is that threadKey in a thread starting message
is only a function of message Date, nothing else.

It may not happen that often in human communication that
two messages are written at the very same time, but it
happens with a lot of cron generated output here.

Does this problem exists in the SourceForge distribution?

Debian bug #167758 quoted above does exist in the SourceForge distribution, and the Debian patch 'fixes' it, but the cure may be worse than the disease.

I will be looking at finding a fix that doesn't mess up indentation.

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

Barry Finkel wrote:

The bug report (dated 4 Nov 2002) states:

Hi, pipermail screws up threading in case that two messages
which were sent at the same time both start a new thread.
New messages to either thread are then only listed below.

The problem is that threadKey in a thread starting message
is only a function of message Date, nothing else.

It may not happen that often in human communication that
two messages are written at the very same time, but it
happens with a lot of cron generated output here.

Does this problem exists in the SourceForge distribution?

Debian bug #167758 quoted above does exist in the SourceForge distribution, and the Debian patch 'fixes' it, but the cure may be worse than the disease.

I will be looking at finding a fix that doesn't mess up indentation.

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