On Sat, Jun 04, 2011 at 08:11:09PM +0200, Alan McKinnon wrote: > Apparently, though unproven, at 17:20 on Saturday 04 June 2011, Indi did > opine > thusly: > > > On Sat, Jun 04, 2011 at 09:54:11AM -0500, Dale wrote: > > > I suspected it was whatever device was being used. Sort of like top > > > posting. Some people have to top post because the device they are using > > > won't let them reply any other way. > > > > > > I just wonder if there is some setting that could be changed somewhere > > > to make it work correctly with usenet, or whatever you were using. > > > > As soon as Alan said it was me, I thought of the difference between > > usenet and email headers and that mail2news gateway. It actually > > shouldn't be hard to workaround, but having already worked around a > > couple of other issues with it I'm ready to just use the email like > > "normal folks" and be done fooling with it. :) > > FWIW, > > If I set kmail to display just routine ordinary threaded mail there's a lot > less thread breakage. It's not all gone, but it is considerably less. > > Setting kmail to display threads based on "activity" - whatever the blazes > that is - breaks things wholesale. I haven't managed to narrow it down at all > so I have no idea what the algorithm is. > > Looks like there's more to this than just usernet<->mail gateway brokenness >
I'd switch if *mutt* was breaking threading for other people, but I'm pretty sure it isn't. Now kmail and the other pointy-clicky-html-loving apps, *those* I don't trust... Tried 'em, found 'em wanting. ;) It would be good to hear from more people running different MUAs, but IMO mutt is the Gold Standard and is almost certaily doing what it's supposed to do. -- caveat utilitor ♫ ❤ ♫ ❤ ♫ ❤ ♫ ❤
