Hey Pascal!

May 04 21:58 04, Pascal Schmidt wrote to Maurice Kinal:

 PS> I wasn't aware of the length requirements.

If I recall correctly a "proper" MSGID contains two fields or
columns, the first the originating address and the second an eight
character field that should be unique within that area.

 PS> Well, for dupe checking, you only need to do a full string compare, 
 PS> no parsing of the MSGID required. If I were to write a tosser, I 
 PS> wouldn't look at the structure of MSGID lines at all.

That is fine for your specific tosser but what about the ones that exist
and fully expect that a MSGID as per the documented specs?  If any tosser
up or down stream from/to you then your tosser in all probably will never
have to need to deal with it since these will be filtered out.  Right?

Life is good,
Maurice

--- Msged/LNX 6.1.1