Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!tale From: tale@cs.rpi.edu (David C Lawrence) Newsgroups: news.software.b Subject: Re: Sequence of header fields Message-ID: Date: 21 Dec 89 02:20:01 GMT References: <1452@ybbs.c.u-tokyo.ac.jp> Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 20 In <1452@ybbs.c.u-tokyo.ac.jp> kenji@ybbs.c.u-tokyo.ac.jp (Kenji Rikitake): > Bnews 2.11.19 requires following conditions to acceptable control messages: > 1. Subject: field should appear before Control: field. > 2. Approved: field should appear as the end of header fields > (i.e. after Lines: field). > Questions: do any implicit requirements exist on each header field? > If yes, why? And how? RFC 1036, the Standard for Interchange of USENET Messages, contains the information regarding headers. It does not make any mention of required header order. The C News authors point out that that processing of messages could be sped up even a little more if Control were required to be the first header line when present. Dave -- (setq mail '("tale@cs.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))