 | | Nasty 'Reference' header chopping —Todd Lehman
|
| | | Hmm... I just noticed something alarming in the 'References' header in Tom McDonald's recent post <lugnet.admin.general:823>. The last message ID is truncated after the first 3 characters...(not Tom's fault)... ---...--- References: (...) (26 years ago, 15-Jan-99, to lugnet.admin.general)
|
| | | |
| | | | | Re: Nasty 'Reference' header chopping —Tom McDonald
|
| | | | | (...) <snip> Todd, once again, let me say how thankful I am that someone who knows what he's doing (or least 97% of what he doing(1)) is taking care of little blood- sucking lymed forest ticks like that that inhabit a place that I really like. (...) (26 years ago, 15-Jan-99, to lugnet.admin.general)
|
| | | | | |
| | | | | | | Re: Nasty 'Reference' header chopping —Terry Keller
|
| | | | | | (...) Dang! I was thinking the same thing as a I (painfully) read thru Todd's post, valiantly trying not to let my eyes glaze over. 3 cheers for Todd! (...) :-) That was a clever one. -- Terry K -- (26 years ago, 15-Jan-99, to lugnet.admin.general)
|
| | | | | | |
| | | | | Re: Nasty 'Reference' header chopping —Alex Wetmore
|
| | | | Todd Lehman wrote in message <369e97d3.13486202@l...et.com>... (...) after (...) This makes sense... somewhere in the RFC977bis draft it says that the maximum length of a line going over the NNTP protocol is 512 bytes. The client picked the wrong (...) (26 years ago, 15-Jan-99, to lugnet.admin.general)
|
| | | | |
