>> MSGID unique number = 32 bit crc number of the following:

>>            Towhom Name+
>>            Fromwhom Name+
>>            Subject Name+
>>            Asciiz Date+
>>            NetworkEchoTag

>> Using this METHOD, at the very LEAST, we can ALL, with a HIGH
>> degree of success, support a unique id system in fidonet.  The ODDS
>> are extremely low that you will get a duplication crc.

AC> No, if I post two messages with the same To, From, Subject, Date into
AC> the same conference, containing different message text, according to
AC> your CRC that will generate the same MSGID serial number.

and what are the ODDS that two people with the SAME NAME will write a
message to the SAME PERSON at the SAME TIME with the SAME SUBJECT in the
SAME ECHO?

>> We can probably add another factor:

>>            Towhom Name+
>>            Fromwhom Name+
>>            Subject Name+
>>            Asciiz Date+
>>            NetworkEchoTag+
>>            OriginatingAddress

AC> ???  But the originating address is included in the MSGID anyway.

Because this allows you to throw in another FACTOR into your DUPE
CHECKING design.  If by chance the TO/FROM/SUBJECT/DATE/ECHO is the same
as you say, the ADDRESS, indeed will break the duplicity.  If the
ADDRESS is the same, well, we do indeed have a DUPE!
--- Platinum Xpress/386/Wildcat! v1.2j