Hi, Bryan:

0) Thank you so much for coming to the rescue!!!

1) Basically trained as a radio frequency hardware engineer, I am only capable of using software as tools necessary for my work. For eMail, I have been using ThunderBird ever since its beginning. With my own time-stamping Subject line discipline, I never needed its threading function. When I received complaints last year, I experimented threading on it and found that it was doing just fine. Whether I prefixed or suffixed the timestamps to the Subject line could not break it. I requested counter examples from those who were having difficulties with my MSGs, but received none. Frustrated but not able to do anything, I went back to continue my EzIP work, leaving this subject in the back burner of my mind. This time around, the problem popped up again in the midst of large number of MSG exchanges. I am so relieved that you presented the threading on the NANOG eMail server that mirrors what I saw on my own PC. So, we now have a common reference for everyone to look at this phenomenon. (Why no one else knew about this facility?)

2) From the Wikipedia explanation of RFC5822, I as a ThunderBird user, really have nothing to do with the Message-ID that it puts on my MSGs nor how does it make use of such to display the threads. And, my Subject line style can't affect it either. So, why some colleagues are having difficulties with just my eMails, but seemly not from others? Could this be caused by the large number of MSGs within a short period of time that amplified this issue? From another feedback, I realized that some colleagues may be using plain text text editors or alike for eMail, because they could not see color nor italic emphasizing of my text. Could such be related to this issue?

I would appreciate very much if you could advance my education with some explanations after perhaps discussions with those offended by my MSGs.

Regards,

Abe (2024-01-13 17:37)