Subject:
|
Re: Posting problem with the web-interface!
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Sat, 8 Jan 2000 05:33:16 GMT
|
Viewed:
|
384 times
|
| |
|
|
On Sat, 8 Jan 2000 04:45:50 GMT, jasper@janssen.dynip.com (Jasper
Janssen) wrote:
References: <Fnv9B7.H2D@lugnet.com> <387356CD.F163AA7@voyager.net>
<3882db17.91566531@lugnet.com> <38741821.9B62453@uswest.net>
<38741B3F.F8D3F7F6@voyager.net> <FnwDE9.Eos@lugnet.com>
<FnxEKG.Iz4@lugnet.com> <3874E642.D0715C15@voyager.net>
<Fny09J.L1o@lugnet.com> <Fny956 <slrn87c1ls.klj.mattdm@jadzia.bu.edu>
<FnzMpC.7Eu@lugnet.com> <FnzoAK.Erx@lugnet.com>
<FnzwuA.9BA@lugnet.com> <FnzxCq.BDx@lugnet.com>
<FnzytE.J5I@lugnet.com> <3876b20b.267719492@lugnet.com>
Incidentally... the left-half-of-a-msg-id results when a newsreader,
instead of simply adding a new Reference and it getting chopped off,
deliberately shortens the references: line (as it should..) to remain
well within the 512 char limit.
Guess what newsreader mentioned in the msg-id to the right of that
phenomenon exhibits _exactly_ that behavior by default..
Incidentally, does that msg-id having a hostname that isn't lugnet.com
mean anything? leafnode server? Reverse-DNS to something meaningful?
Jasper
|
|
Message has 2 Replies:
 | | Re: Posting problem with the web-interface!
|
| (...) Eeek, but it shouldn't *chop* at 512 characters, should it?! :-p What you said before -- keeping the first reference and eliminating some of the middle ones -- seems much more sane. That way they're all still <.*> . (...) slrn? (...) Dunno. (...) (25 years ago, 8-Jan-00, to lugnet.admin.general)
| | | Re: Posting problem with the web-interface!
|
| (...) No. See <URL:(URL) and <URL:(URL) The magic number seems to actually be 998. (...) Yes. From the GNKSA, above: <<Followup agents SHOULD not shorten References headers. If it is absolutely necessary to shorten the header, as a des- perate last (...) (25 years ago, 8-Jan-00, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Posting problem with the web-interface!
|
| (...) Yeah.. I asked a few times about the related problem where the end of References: and the other headers after it show up after a \n. I suspect that CNews always inserts a \n after truncating a References: line to 511 (why not 512 beats me), (...) (25 years ago, 8-Jan-00, to lugnet.admin.general)
|
16 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
