| 1 |
David W Noon wrote: |
| 2 |
> Not a problem. In fact, it is not I (or Indi) who is causing the |
| 3 |
> breakage. |
| 4 |
> |
| 5 |
> A little further investigation has shown that the Message-ID: line of |
| 6 |
> all message posted through the Gentoo list server is rewritten, |
| 7 |
> regardless of its initial value. This is why correctly posted messages |
| 8 |
> have the Bastard Operator From Hell designation: the domain name of |
| 9 |
> Gentoo's list server is bofh.it. This also means that those who read |
| 10 |
> this list's messages via email will always see a valid Message-ID: line. |
| 11 |
> |
| 12 |
> Now, one other possible cause of message id mismatch is people posting |
| 13 |
> directly to Usenet as well as through the list server. All NNTP |
| 14 |
> servers should have the newsgroup that is a reflection of this mailing |
| 15 |
> list marked as "no posting allowed"; certainly |
| 16 |
> news.eternal-september.org is configured that way. However, if a |
| 17 |
> misposted message gets through from another Usenet-registered NNTP |
| 18 |
> server, I will see it with the alternate Message-ID: line, not the one |
| 19 |
> generated by the Gentoo list server. It is messages such as this that |
| 20 |
> cause the breakage in threads when somebody (anybody) reading through |
| 21 |
> an NNTP server posts a follow-up to such a message. |
| 22 |
> |
| 23 |
> So, when you see a breakage in a message thread, it is the message that |
| 24 |
> is the tail-end of the original thread that is causing the breakage, |
| 25 |
> not the message that apparently starts the new thread. |
| 26 |
> |
| 27 |
> I hope all is clear now. |
| 28 |
> |
| 29 |
|
| 30 |
|
| 31 |
Oh, so when it gets broken, I need to find the message before that to |
| 32 |
see where it got messed up. Sorry to use the technical term "messed up" |
| 33 |
but it fits rather well. lol |
| 34 |
|
| 35 |
Dale |
| 36 |
|
| 37 |
:-) :-) |
Archives