My guess is that it has something to do with the fact that this list (bizarrely, IMO) uses reply to sender by default rather than reply to list. Some MUAs may mangle the Message ID in such a case (when the list email is manually specified).
Just a guess. David 2010/12/12 Łukasz Stelmach <[email protected]> > Hello. > > I've noticed that Gmane's doing something evil to message-ids in this > group. I read several other groups via Gmane and this is *the only* that > has such broken threading. > > E.g. > > Hank Ivy started the "Protecting IDs at a keysigning party" thread with > e message > > <[email protected]> > > which has been mangled at Gmane to > > <201012081420.14986.hankivy__6874.93589143759$1291842486$gmane$ > [email protected]> > > David Shaw's reply refers to the original non-gmane ID. Even though my > MUA (Gnus) puts David's message somewhere near Hank's (they share the > subject) it can't put it completely right. BTW David's message-id is > mangled to. > > I assume it's because of some strange settings specific to this > particular group. Is there anyone who could, please, fix this? > > PS. I send this message via Gmane with an ID: > > <874oaiocpp.fsf%[email protected]<874oaiocpp.fsf%[email protected]> > > > -- > Miłego dnia, > Łukasz Stelmach > > > _______________________________________________ > Gnupg-users mailing list > [email protected] > http://lists.gnupg.org/mailman/listinfo/gnupg-users > -- David Tomaschik, RHCE, LPIC-1 GNU/Linux System Architect GPG: 0x [email protected]
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
