 | | Re: Broken mailers which mess up threading
|
|
(...) Ya, that Larry! :-) Lemme see if I can conjur it up again. OK, here it is: (2 URLs) [...] (...) According to the NNTP headers, ya, it was posted via email. --Todd (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) This Larry? Can you post the URL, I will take a look at it and tell you what the circs were. I make it a practice not to reply via email EVER but always use the web (or very rarely, NNTP via NS comm 4.7 from my home PC) to reply. (...) I don't (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) I really don't think it's worth the time to work around it -- only to weed out non-compliant mailers in a consistent and reliable way. If someone is using a broken newsreader or mailer that doesn't put in the right headers, tough cookies for (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Posting cancel request
|
|
Hello Todd, Could you please cancel my message Marketplace/Buy/Sell/Trade/8315 ? In this post I gave an example of using the partsref and using the direct links to the part images, but due to a relocation of partsef, the example links became (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Incorrect group posting [was RE: cartoonnetwork.com is having an online contest]
|
|
(...) So what're you waiting for? Steve (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) that's one place where we have a choice to make... does re-subjecting make a new thread, or is it still a child of the current thread? most of the time, by the time someone re-subjected a post, it's 3-4 posts AFTER the subject has been (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) the problem is, we're dealing with mailers that are just not RFC compliant. Which is why they don't have the references: header in the first place... and we're trying to cludge something around their shortcomings, just so the pretty threading (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) It sounds like if the References: header is used to trace threads, then the Subject: header should begin with "Re: ". I suppose the original intent was that new threads would be started if the Subject: was changed (but that's pure conjecture (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) Except cases where you do the "(was: ...)" thing, right? --Todd (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
| |
| | Re: Broken mailers which mess up threading
|
|
(...) I'd say that's perfectly in line with with RFC 850, Section 2.2.6. It clearly says that a References: headers is "required for all follow-up articles" and that the first four characters of the Subject: header should be changed to "Re: " if (...) (24 years ago, 10-Oct-00, to lugnet.admin.nntp)
|
