| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | msgid |
Hi Maurice! :-) MK> ^AMSGID: origaddr serialno [...] MK> 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. Note that it says "may be", there is no absolute requirement for this. In fact it goes on to say that an eight character hex number is *only* okay if it is unique over a three year period. Plus nothing in the working forbids spaces in the "serialno" field. It also doesn't specify that the "origaddr" should be a Fido address, because then they wouldn't need to allow quoting in case there were spaces in there. This standard isn't strict enough to allow any software making wild assumptions except from the one that there'll be one space somewhere in the middle of the MSGID. :) Apart from that, the claim from that SBBS (was it that?) author that repeating the same hex number in different casing makes a MSGID somehow *more* unique is clearly bogus - if both numbers are always the same. Ciao Pascal --- Msged/LNX 6.1.1* Origin: sed s/$(echo $HOME | sed 's/[[:punct:]]/\\&/g')/~/ (1:153/401.2) SEEN-BY: 633/267 270 @PATH: 153/401 307 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.