| 1 |
David W Noon wrote: |
| 2 |
> On Sat, 04 Jun 2011 05:40:01 +0200, Dale wrote about Re: [gentoo-user] |
| 3 |
> Threads changing Was: OT: website design: |
| 4 |
> |
| 5 |
> |
| 6 |
>> The thread "Cleaning redundant configuration files" is the worst. I |
| 7 |
>> just went back and looked. David W Noon is usually where it starts. |
| 8 |
>> David, what you got going on there my friend? You using a mobile |
| 9 |
>> device or something? ;-) Just curious. |
| 10 |
>> |
| 11 |
> I am using Claws-Mail under Xfce on a desktop system. |
| 12 |
> |
| 13 |
> However, I am polling this mailing list as a newsgroup through the |
| 14 |
> eternal-september NNTP server in Germany. This server sometimes |
| 15 |
> modifies the Message-ID: line in the headers, so that the References: |
| 16 |
> line in my follow-up has a different message id from the one that you |
| 17 |
> are seeing in the messages to which I reply. This happens only |
| 18 |
> sporadically, at least as I read the list -- but then it would, as the |
| 19 |
> message id's I see are the ones eternal-september likes. |
| 20 |
> |
| 21 |
> Exactly why the eternal-september server changes the Message-ID: line |
| 22 |
> is not immediately obvious. I suspect some mail and news readers |
| 23 |
> generate Message-ID's that are not RFC-compliant and eternal-september |
| 24 |
> corrects the problem, BICBW. |
| 25 |
> |
| 26 |
> |
| 27 |
>> Now watch him not read this message. lol |
| 28 |
>> |
| 29 |
> I'm reading it a bit late because I was doing a full system backup of my |
| 30 |
> own newsserver system (~40 gigs) with the cron jobs all stopped, |
| 31 |
> including the one that pulls messages from news.eternal-september.org. |
| 32 |
> So I was off the air for about 3½ hours today. |
| 33 |
> |
| 34 |
|
| 35 |
Well, something works now. This is threaded as it should be. So, |
| 36 |
whatever you are doing, keep doing it that away. lol |
| 37 |
|
| 38 |
I don't want you to think I was upset or anything. I just went back and |
| 39 |
noticed you was one of the ones that it was breaking the threads on. I |
| 40 |
was sort of figuring you were using a mobile device or something that |
| 41 |
was breaking it and it was not you choosing to break it. Someone |
| 42 |
noticed it was also doing the same with someone else's replies as well. |
| 43 |
I figured it was something about the senders "equipment" or maybe it was |
| 44 |
just me. That's why I asked and was trying to figure out why this was |
| 45 |
happening. |
| 46 |
|
| 47 |
Better late than never. lol Glad you got you backups done, I hope you |
| 48 |
never need them. ;-) |
| 49 |
|
| 50 |
Dale |
| 51 |
|
| 52 |
:-) :-) |
Archives