Re: msgid
  By: Alexander S. Aganichev to Maurice Kinal on Fri May 07 2004 11:52 am

 > Maurice,
 > 
 > Not so long ago (06 May 04) you wrote to Joe:
 >  JD>> The MSGID is fine and follows the FTS-9 specification as well as
 >  JD>> later MSG-ID definitions. The "serialno"
portion is repeated twice to
 >  JD>> generate *more* unique strings for those programs that store the
 >  JD>> *entire* message-ID (and not just the serialno).
 >  MK> Hm.  I am cutting and pasting what I have from FTS-0009 and am
 >  MK> assuming that most, if not all, tossers follow:
 > 
 >  MK>           ^AMSGID: origaddr serialno
 > 
 > ^AMSGID: 1:249/303 05002dca 533.fidohusk 05002DCA
 >          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~
 >          origaddr in "syncronet network" serialno
 > 
 >  MK>      The originating address should be specified in a form that
 >  MK>      constitutes a valid return address for the originating network.
 >  MK>      If the originating address is enclosed in double-quotes,  the
 >  MK>      entire string between the beginning and ending double-quotes is
 >  MK>      considered to be the orginating address.  A double-quote
 >  MK> character
 >  MK>      within a quoted address is represented by by two consecutive
 >  MK>      double-quote characters.  The serial number may be any eight
 >  MK>      character hexadecimal number,  as long as it is unique - no two
 >  MK>      messages from a given system may have the same serial number
 >  MK>      within a three years.  The manner in which this serial number is
 >  MK>      generated is left to the implementor.
 > 
 >  MK> According to what I see above there are only two fields and not four.
 > 
 > There's no requirement that origaddr should be enclosed in quotes if it
 > contains spaces. It may be assumed, but it is not said explicitly, so above 
 > valid unless it is specified somewhere else 8-)

Sorry, I realize this is an old thread.

The break-down would be more like:

 ^AMSGID: 1:249/303 05002dca 533.fidohusk 05002DCA
          ~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          origaddr           serialno

or:

 ^AMSGID: 1:249/303 05002dca 533.fidohusk 05002DCA
          ~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
          origaddr  serialno      

The reason for the extra message-specific text (particularly,
"533.fidohusk" in
this example) is that it's been proven time and again that a 32-bit
"serialno"
is not a sufficient amount of unique data to denote a specific message from a
specific system. And Fido MTAs that store the entire MSG-ID (or a digest
thereof) will get a truely unique MSG-ID for each message generated by a
Synchronet system. The repeated, altered-case "serialno" is just to provide
more unique data for a "digest" algorithm, if one is used. If
Fido MTA can't
handle the additional message-specific data (e.g. "533.fidohusk")
then it won't
be able to handle the repeated serialno either.

-Rob

                                                  digital man

Snapple "Real Fact" #73:
The average person spends 2 weeks of it's life waiting for a traffic light to change.
--- SBBSecho 2.10-Win32