Google| Subject | Re: nospam still not admitting to an error (was: The closest we'll get to nospam admitting to an err |
| From | Sandman |
| Date | 01/26/2016 10:28 (01/26/2016 10:28) |
| Message-ID | <sandman-4e2bf48b863479ef96f68bab039edd4f@individual.net> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Eric Stevens |
| Followups | Eric Stevens (17h & 27m) > Sandman |
In article <vnbeab56tu2m7d836k3mocqjcmnj5085f6@4ax.com>, Eric Stevens wrote:
Eric StevensHere is your irrelevant verbiage re-insterted:
Quote my text you deleted and see if you can still justify your bluster.
See https://tools.ietf.org/html/rfc5256#ref-THREADINGThis is an irrelevant RFC, hence it was snipped. It pertains mainly to a IMAP sorting extension (command) called "THREAD", which is a version of the SEARCH command, where the IMAP server can respond to a THREAD command and give the mail program messages sorted as they pertain to each other in a conversation.
"The ORDEREDSUBJECT threading algorithm is also referred to as "poor man's threading". The searched messages are sorted by base subject and then by the sent date. The messages are then split into separate threads, with each thread containing messages with the same base subject text. Finally, the threads are sorted by the sent date of the first message in the thread."The above quote, again, is only relevant to a parameter to the THREAD command to a IMAP server, and has exactly nothing to do with NNTP.
I.e., in short, an IMAP client can issue a THREAD command as such:
THREAD <algorithm><charset><search phrase>
So, issuing it as such:
THREAD ORDEREDSUBJECT UTF-8 Eric has problems with RFC's
Would search the mailbox on the server for everything that contains "Eric has problems with RFC's" and return the search result in subject order and then date order.
Again, this has NOTHING to do with NNTP (usenet) where messages are fetched from the server using either the XOVER or XHDR commands.
Your software will not enable you to construct threads like this and for that reason you seem to think it is wrong.The above is irrelevant to your explicit claim:
Eric Stevens 01/23/2016 <mig5abdjtuoep0eln74jdkmik4jr0v30l6@4ax.com>
"As far as the reader is concerned, you have changed the subject and it's now a different thread"
I have never said that something is "wrong". I have correctly pointed out that your news client of choice displays threads in a non-standard way, where it not only displays a change of subject as a new thread, it also deletes the references in any followups to it, thereby breaking the thread.
Agent says of this:
"Check this box to have Agent include messages with the same subject under the same thread, even if the follow-up message doesn't contain a valid reference to the original. People frequently mis-post responses and this helps match follow-ups with the message to which they are responses.
Checking this box will also cause Agent to thread your email messages."
As you say, not many news reader will enable this but my first quote shows that this does not mean that Agent is wrong to do so. Threading on subject is permitted and can be a good idea.Agent is doing it in a non-standard way, which I have shown. Also, it is in violation of the RFC, which I have also shown. You, on the other hand, have failed to support your *explicit* claims about what "the reader" thinks is a new thread or not.
Since it has been shown that the majority of news clients shows posts as threaded by the References header, then it is clear that "the reader" would most certainly see the post as part of the ongoing thread, regardless of subject.
So, just stop making explicit claims about what a thread is based on how your non-standard news client present it to you. Usenet has been around for decades and what is and what isn't a "thread" is already firmly established
-- Sandman
01/06/2016-
