Hey Joe!

May 06 22:34 04, Joe Delahaye wrote to Maurice Kinal:

 JD> The MSGID is fine and follows the FTS-9 specification as well as 
 JD> later
 JD> MSG-ID
 JD> definitions. The "serialno" portion is repeated twice to generate
 JD> *more* unique
 JD> strings for those programs that store the *entire* message-ID (and 
 JD> not
 JD> just the
 JD> serialno).

Hm.  I am cutting and pasting what I have from FTS-0009 and am assuming
that most, if not all, tossers follow:

---------------cut 'n paste------------------
MSGID

     A MSGID line consists of the string "^AMSGID:" (where ^A is a
     control-A (hex 01) and the double-quotes are not part of the
     string),  followed by a space,  the address of the originating
     system,  and a serial number unique to that message on the
     originating system,  i.e.:

          ^AMSGID: origaddr serialno

     The originating address should be specified in a form that
     constitutes a valid return address for the originating network.
     If the originating address is enclosed in double-quotes,  the
     entire string between the beginning and ending double-quotes is
     considered to be the orginating address.  A double-quote character
     within a quoted address is represented by by two consecutive
     double-quote characters.  The serial number may be any eight
     character hexadecimal number,  as long as it is unique - no two
     messages from a given system may have the same serial number
     within a three years.  The manner in which this serial number is
     generated is left to the implementor.

------------------------------------------------------------

According to what I see above there are only two fields and not four.

Life is good,
Maurice

--- Msged/LNX 6.1.1