Hello Gary, On Mon, 23 May 2005 16:04:26 -0500 GMT (24/05/2005, 04:04 +0700 GMT), Gary wrote:
G> now the RECOMMENDED part G> The message identifier (msg-id) itself MUST be a globally unique G> identifier for a message. The generator of the message identifier G> MUST guarantee that the msg-id is unique. Hm. Do MUST sentences in the RFCs refer to recommendations? OK. The point with the unique message ID was the usenet, and it makes sense there. It doesn't make sense for email (as used in mailing lists), IMHO. So Tony is safe in my opinion, but I am not sure whether the RFCs agree. G> This document occasionally uses terms that appear in capital letters. G> When the terms "MUST", "SHOULD", "RECOMMENDED", "MUST NOT", "SHOULD G> NOT", and "MAY" appear capitalized, they are being used to indicate G> particular requirements of this specification. A discussion of the G> meanings of these terms appears in [RFC2119]. -- Cheers, Thomas. I know that the work cycle is not plan/start/finish, but is wait/plan/plan. Message reply created with The Bat! 3.5 under Windows XP 5.1 Build 2600 Service Pack 2 ________________________________________________________ Current beta is (none) | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
