| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | A message identifier proposal for someone who cares to use. |
In a message to All Mark Kimes wrote: > Document: FSC-00?? > Version: 001 > Date: > Message identifiers > =================== > Your Name > FidoNet Your Address I assume it is you, Mark Kimes, who is the author of this document? ... > IMSGID > The IMSGID line gives the message a unique identifier. The > IMSGID may not be reused during the lifetime of any previous message > with the same IMSGID. (It is recommended that no IMSGID be reused > for at least two years.) IMSGID's have the syntax: Obviously IMSGID/IREPLY are used for message identification and reply-linking, in a nutshell. How does this offer a distinct advantage over FTS-9? Should IMSGID be used as a means of duplicate message detection, as per the current FTS-9 spec? Your proposal mentions nothing regarding dupe detection; I'm just wondering if this was your intention. ZeeYa... Andrew. ---* Origin: Blizzard of Ozz, Melbourne, Australia (3:635/727.4) SEEN-BY: 50/99 209/720 620/243 632/103 341 348 386 635/503 727 640/201 206 SEEN-BY: 640/217 297 305 820 822 823 690/660 711/409 410 413 430 431 807 808 SEEN-BY: 711/809 816 934 942 712/515 713/888 800/1 7877/2809 @PATH: 635/727 632/348 640/820 711/409 808 809 934 |
|
| 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™.