Dave Thomas <Dave / PragmaticProgrammer.com> wrote:

> > it doesn't do it. I found a few other posts through Gooja of people asking
> > this question -- none had any replies, so it seems as though Outlook is a
> > problem here.
> 
> OK - in that case, I suggest that we ask for the mailing list to be
> changed to move the [ruby-talk:nnnn] out of the subject line. Although
> I personally like it (and it causes no problem when threading with my
> mail reader (gnus)), I know it stops others from threading correctly.
> 
> Perhaps we could move it into an X-ruby-talk header, or append it to
> the end of the message.
> 
> Any thoughts?

I think problem still exists except for mail/news reader which
doesn't set In-Reply-To/References header appropriately.
Client software without threading mechanism of 'Subject' header
comparing will be confused because of *replaced* 'Message-Id'.

(This drawing is valid for fixed pitch font.)

-----------------------------------------------------------
*case 1.  Good for both folks.  No one is troubled.
   NET-NEWS  <--------->  GATEWAY  <-------> MAILING-LIST
   mid:<AAA>               --->    mid:<AAA>
    |                               |
    +- mid:<BBB>           --->     +- mid:<BBB>
       ref:<AAA>                       ref:<AAA>
        |                               |
        +- mid:<CCC>       --->         +- mid:<CCC>
           ref:<AAA> <BBB>                 ref:<AAA> <BBB>
-----------------------------------------------------------
*case 2.  Bad for NN folks.  ML folks don't notice.
   NET-NEWS  <--------->  GATEWAY  <-------> MAILING-LIST
   mid:<aaa>               <---    mid:<AAA>
                                    |
    ?- mid:<bbb>           <---     +- mid:<BBB>
       irt:<AAA>                       irt:<AAA>
       ref:<AAA>                       ref:<AAA>
                                        |
        ?- mid:<ccc>       <---         +- mid:<CCC>
           irt:<BBB>                       irt:<BBB>
           ret:<AAA> <BBB>                 ref:<AAA> <BBB>
-----------------------------------------------------------
*case 3.  Good for first reply.  Second fails on ML.
   NET-NEWS  <--------->  GATEWAY  <-------> MAILING-LIST
   mid:<AAA>               --->    mid:<AAA>
    |                               |
    +- mid:<bbb>           <---     +- mid:<BBB>
       irt:<AAA>                       irt:<AAA>
       ref:<AAA>                       ref:<AAA>
        |
        +- mid:<CCC>       --->         ?- mid:<CCC>
           ref:<AAA> <bbb>                 ref:<AAA> <bbb>
-----------------------------------------------------------
*case 4.  First fails on ML.  Second succeed consequently.
   NET-NEWS  <--------->  GATEWAY  <-------> MAILING-LIST
   mid:<aaa>               <---    mid:<AAA>
    |
    +- mid:<BBB>           --->     ?- mid:<BBB>
       ref:<aaa>                       ref:<aaa>
        |                               |
        +- mid:<ccc>       <---         +- mid:<CCC>
           irt:<BBB>                       irt:<BBB>
           ref:<aaa> <BBB>                 ref:<aaa> <BBB>
-----------------------------------------------------------

-- 
Shusaku