Re: msgid
  By: Alexander S. Aganichev to Rob Swindell on Fri Aug 27 2004 10:37 am

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

It's been like this for almost 2 years now with no complaints of specific
incompatibilities. If someone has a specific example of an incompatibility with
the Sychronet FTN MSGID format, I'll look into adjusting the format to suit.

While something like:

  ^AMSGID: "1:249/303 533.fidohusk" 05002DCA

would more closely follow the FTS-9 as written, I seriously doubt it would
improve compatibility with programs that would attempt to parse the MSGID. But
who knows?

                                                  digital man

Snapple "Real Fact" #18:
A jellyfish is 95% water.
--- SBBSecho 2.10-Win32