But it doesn't sort over multiple threads as those
messages not in a same thread have no relation on which an ordering
decision can be made.

Netscape 7.2 (which I use) cannot sort threads by subject line. (by
this I don't mean messages within a thread, which should be in thread
order, but rather, the group of threads themselves)

Of course, since threads are not defined by subject line, this is
understandable, nonetheless, threads are usually closely correlated with
subject line, and when I remember a thread I want to look at (or avoid),
it is usually by subject line.

=Messages= can be sorted by subject line, but then the OT colon bug
shows up.

The Internet isn't bug-free yet?

It was bug free the day before it was born.

From what you're describing, it sounds like Netscape's news reading
capability is broken in several different ways.

No, actually it is probably working as designed, since threads are not
defined by subject line. That is, subject lines can change within a
thread, so which subject line should be used?

Why not simply use
something else?

I could, I suppose, but that's not the point. My point is that I have
(re)discovered an (admittedly small but vexing) adverse consequence of
people using a colon after a prepend. With this knowledge, those that
care about this adverse consequence to others may wish to avoid
following prepends with a colon.

That is all.

Jose
--
There are two kinds of people in the world. Those that just want to
know what button to push, and those that want to know what happens when
they push the button.
for Email, make the obvious change in the address.