On Saturday 04 June 2011 15:46:49 Indi wrote: > On Sat, Jun 04, 2011 at 09:38:52PM +0200, Volker Armin Hemmann wrote: > > On Saturday 04 June 2011 11:59:52 kashani wrote: > > > On 6/4/2011 11:43 AM, Indi wrote: > > > > 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. > > > > > > Whatever you're using is breaking threading in Thunderbird and I > > > can't > > > think of anyone else lately I've had the problem with. Also mutt has > > > broken threading in the past and even between different versions of > > > itself... so calling it a gold standard may be an overstatement. > > > > it is golden brown, runny and smelly. Some call it 'gold'. > > I hate the way you beat around the bush. Just tell us how you *really* > feel, dammit! > > ;)
<diplomatic mode> I have a slightly adverse general opinion about the mail client called 'mutt'. I am not saying that this is the fault of its devs nor do I suggesst that there is anything wrong with its users. </diplomatic mode> Pine is slightly less gruesome.. Old kmail rocked. It even did well with threads where the thread id was mangled - threading by subject was an option. Haven't looked into the options with the kmail beta I am using at the moment. I am glad that it is more or less stable. -- #163933
