time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

List Threading Behavior?

DC
Doug Calvert
Tue, Oct 25, 2011 5:29 AM

Hello,
Am I the only one whose email client has trouble putting threads
together for this list? All of my other lists appear to be working
correctly. Am I missing something?

Hello, Am I the only one whose email client has trouble putting threads together for this list? All of my other lists appear to be working correctly. Am I missing something?
AK
Attila Kinali
Tue, Oct 25, 2011 9:10 AM

On Tue, 25 Oct 2011 01:29:07 -0400
Doug Calvert dfc-list@douglasfcalvert.net wrote:

Am I the only one whose email client has trouble putting threads
together for this list? All of my other lists appear to be working
correctly. Am I missing something?

This is not an issue of the mailinglist itself, but of mail clients
that do not conform to the RFC's. Especially webclients and MS stuff
are known to miss the "In-Reply-To" and "References" header fields
which are needed to get threading working correctly.

Ie if someone with an incorrectly working mailclient replies to a
mail you will get a "split" thread, because the In-Reply-To field is
missing.

		Attila Kinali

--
The trouble with you, Shev, is you don't say anything until you've saved
up a whole truckload of damned heavy brick arguments and then you dump
them all out and never look at the bleeding body mangled beneath the heap
-- Tirin, The Dispossessed, U. Le Guin

On Tue, 25 Oct 2011 01:29:07 -0400 Doug Calvert <dfc-list@douglasfcalvert.net> wrote: > Am I the only one whose email client has trouble putting threads > together for this list? All of my other lists appear to be working > correctly. Am I missing something? This is not an issue of the mailinglist itself, but of mail clients that do not conform to the RFC's. Especially webclients and MS stuff are known to miss the "In-Reply-To" and "References" header fields which are needed to get threading working correctly. Ie if someone with an incorrectly working mailclient replies to a mail you will get a "split" thread, because the In-Reply-To field is missing. Attila Kinali -- The trouble with you, Shev, is you don't say anything until you've saved up a whole truckload of damned heavy brick arguments and then you dump them all out and never look at the bleeding body mangled beneath the heap -- Tirin, The Dispossessed, U. Le Guin
DC
Doug Calvert
Tue, Oct 25, 2011 7:00 PM

On 10/25/2011 05:10 AM, Attila Kinali wrote:

On Tue, 25 Oct 2011 01:29:07 -0400
Doug Calvertdfc-list@douglasfcalvert.net  wrote:

Am I the only one whose email client has trouble putting threads

together for this list? All of my other lists appear to be working
correctly. Am I missing something?

This is not an issue of the mailinglist itself, but of mail clients
that do not conform to the RFC's. Especially webclients and MS stuff
are known to miss the "In-Reply-To" and "References" header fields
which are needed to get threading working correctly.

Ie if someone with an incorrectly working mailclient replies to a
mail you will get a "split" thread, because the In-Reply-To field is
missing.

		Attila Kinali

Thanks that makes sense. Most of the other mailing lists I am on are
mainly populated by n*x users.

On 10/25/2011 05:10 AM, Attila Kinali wrote: > On Tue, 25 Oct 2011 01:29:07 -0400 > Doug Calvert<dfc-list@douglasfcalvert.net> wrote: > >> Am I the only one whose email client has trouble putting threads >> together for this list? All of my other lists appear to be working >> correctly. Am I missing something? > > This is not an issue of the mailinglist itself, but of mail clients > that do not conform to the RFC's. Especially webclients and MS stuff > are known to miss the "In-Reply-To" and "References" header fields > which are needed to get threading working correctly. > > Ie if someone with an incorrectly working mailclient replies to a > mail you will get a "split" thread, because the In-Reply-To field is > missing. > > > Attila Kinali > Thanks that makes sense. Most of the other mailing lists I am on are mainly populated by n*x users.
JP
Justin Pinnix
Tue, Oct 25, 2011 9:38 PM

Looking at recent instances of thread-breaking tells a different story:

X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929
Thunderbird/7.0.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.21)
Gecko/20110830 Thunderbird/3.1.13

While these mailers are all running on Microsoft OSes, none of them are
actual Microsoft products.

Thanks,
-JP
On Tue, Oct 25, 2011 at 3:00 PM, Doug Calvert
dfc-list@douglasfcalvert.netwrote:

On 10/25/2011 05:10 AM, Attila Kinali wrote:

On Tue, 25 Oct 2011 01:29:07 -0400
Doug Calvert<dfc-list@**douglasfcalvert.netdfc-list@douglasfcalvert.net>
wrote:

Am I the only one whose email client has trouble putting threads

together for this list? All of my other lists appear to be working
correctly. Am I missing something?

This is not an issue of the mailinglist itself, but of mail clients
that do not conform to the RFC's. Especially webclients and MS stuff
are known to miss the "In-Reply-To" and "References" header fields
which are needed to get threading working correctly.

Ie if someone with an incorrectly working mailclient replies to a
mail you will get a "split" thread, because the In-Reply-To field is
missing.

                    Attila Kinali

Thanks that makes sense. Most of the other mailing lists I am on are

mainly populated by n*x users.

_____________**
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/**
mailman/listinfo/time-nutshttps://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Looking at recent instances of thread-breaking tells a different story: X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.21) Gecko/20110830 Thunderbird/3.1.13 While these mailers are all running on Microsoft OSes, none of them are actual Microsoft products. Thanks, -JP On Tue, Oct 25, 2011 at 3:00 PM, Doug Calvert <dfc-list@douglasfcalvert.net>wrote: > On 10/25/2011 05:10 AM, Attila Kinali wrote: > >> On Tue, 25 Oct 2011 01:29:07 -0400 >> Doug Calvert<dfc-list@**douglasfcalvert.net<dfc-list@douglasfcalvert.net>> >> wrote: >> >> Am I the only one whose email client has trouble putting threads >>> together for this list? All of my other lists appear to be working >>> correctly. Am I missing something? >>> >> >> This is not an issue of the mailinglist itself, but of mail clients >> that do not conform to the RFC's. Especially webclients and MS stuff >> are known to miss the "In-Reply-To" and "References" header fields >> which are needed to get threading working correctly. >> >> Ie if someone with an incorrectly working mailclient replies to a >> mail you will get a "split" thread, because the In-Reply-To field is >> missing. >> >> >> Attila Kinali >> >> Thanks that makes sense. Most of the other mailing lists I am on are > mainly populated by n*x users. > > > ______________________________**_________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/** > mailman/listinfo/time-nuts<https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts> > and follow the instructions there. >
Z
Ziggy
Wed, Oct 26, 2011 5:53 PM

The other way that threads get broken is by thread 'hijacking'. If I
were to hit reply to any message on this thread, change the subject and
delete the body, I could write a 'new' message. Threaded clients would
see that new message as part of the existing thread, but others would
simply see a new message with a new subject. It's  bad form to use
'reply' and change the subject. If you're going to change the subject,
start with a new and blank message.

Ziggy

On 10/25/2011 05:38 PM, Justin Pinnix wrote:

Looking at recent instances of thread-breaking tells a different story:

X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929
Thunderbird/7.0.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.21)
Gecko/20110830 Thunderbird/3.1.13

While these mailers are all running on Microsoft OSes, none of them are
actual Microsoft products.

The other way that threads get broken is by thread 'hijacking'. If I were to hit reply to any message on this thread, change the subject and delete the body, I could write a 'new' message. Threaded clients would see that new message as part of the existing thread, but others would simply see a new message with a new subject. It's bad form to use 'reply' and change the subject. If you're going to change the subject, start with a new and blank message. Ziggy On 10/25/2011 05:38 PM, Justin Pinnix wrote: > Looking at recent instances of thread-breaking tells a different story: > > X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 > User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 > Thunderbird/7.0.1 > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.21) > Gecko/20110830 Thunderbird/3.1.13 > > While these mailers are all running on Microsoft OSes, none of them are > actual Microsoft products. >
JS
jim s
Wed, Oct 26, 2011 11:24 PM

If one is using thunderbird as below, it is just as easy to right click
the time nuts address element at the top of the message and reply do a
"compose message"

If using web based email, the reply-to and change the subject is
probably the easiest since there is no way to do the above action.  It
is interesting that the examples below are from thunderbird.
Jim

On 10/26/2011 10:53 AM, Ziggy wrote:

The other way that threads get broken is by thread 'hijacking'. If I
were to hit reply to any message on this thread, change the subject
and delete the body, I could write a 'new' message. Threaded clients
would see that new message as part of the existing thread, but others
would simply see a new message with a new subject. It's  bad form to
use 'reply' and change the subject. If you're going to change the
subject, start with a new and blank message.

Ziggy

On 10/25/2011 05:38 PM, Justin Pinnix wrote:

Looking at recent instances of thread-breaking tells a different story:

X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929
Thunderbird/7.0.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.2.21)
Gecko/20110830 Thunderbird/3.1.13

While these mailers are all running on Microsoft OSes, none of them are
actual Microsoft products.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

If one is using thunderbird as below, it is just as easy to right click the time nuts address element at the top of the message and reply do a "compose message" If using web based email, the reply-to and change the subject is probably the easiest since there is no way to do the above action. It is interesting that the examples below are from thunderbird. Jim On 10/26/2011 10:53 AM, Ziggy wrote: > The other way that threads get broken is by thread 'hijacking'. If I > were to hit reply to any message on this thread, change the subject > and delete the body, I could write a 'new' message. Threaded clients > would see that new message as part of the existing thread, but others > would simply see a new message with a new subject. It's bad form to > use 'reply' and change the subject. If you're going to change the > subject, start with a new and blank message. > > Ziggy > > On 10/25/2011 05:38 PM, Justin Pinnix wrote: >> Looking at recent instances of thread-breaking tells a different story: >> >> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 >> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 >> Thunderbird/7.0.1 >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; >> rv:1.9.2.21) >> Gecko/20110830 Thunderbird/3.1.13 >> >> While these mailers are all running on Microsoft OSes, none of them are >> actual Microsoft products. >> > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > >