Synchronet v3.17b-Win32 (install) has been released (Jan-2019).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
faq:misc [2018/10/31 01:52]
digital man Added a "No Guest" FAQ
faq:misc [2019/01/09 07:07] (current)
wkitty42 [FTN MSGID] by -> be
Line 187: Line 187:
 The result **is** a "//​valid return address for the originating network//",​ in that a FidoNet NetMail sent to this address will normally reach the sysop of the originating node (in the example case, me). But the //​originating//​ network might **not** be an FTN network. There is **nothing** in FTS-9 that specifies the form or content of the ''​origaddr''​ field. In fact, it mentions the use of "​double-quotes"​ and how they must be escaped if part of the address. When is the last time you saw quotes of any kind in an FTN address? Clearly the author was leaving this definition open to non-FTN addresses. And again, it's only a "​should"​ clause anyway. This field could only contain the GPS coordinates of my birthplace and would still be completely within the requirements of the specification. The result **is** a "//​valid return address for the originating network//",​ in that a FidoNet NetMail sent to this address will normally reach the sysop of the originating node (in the example case, me). But the //​originating//​ network might **not** be an FTN network. There is **nothing** in FTS-9 that specifies the form or content of the ''​origaddr''​ field. In fact, it mentions the use of "​double-quotes"​ and how they must be escaped if part of the address. When is the last time you saw quotes of any kind in an FTN address? Clearly the author was leaving this definition open to non-FTN addresses. And again, it's only a "​should"​ clause anyway. This field could only contain the GPS coordinates of my birthplace and would still be completely within the requirements of the specification.
   ​   ​
-The serial number (''​serialno''​) field generated by Synchronet and its utilities is a mathematical sum of the area-unique ''<​msgnum>''​ and a number derived from the date and time the message was created so as to maximize the use of the allocated 32-bits. The serial number will by unique among all the messages generated by a Synchronet-system in a single message area (echo), but is not guaranteed to be unique, by itself, among //all// the FTN-connected message areas of a single Synchronet-system. The ''​serialno''​ field //alone// does **not** constitute a unique message identifier, so don't try to use it as one!+The serial number (''​serialno''​) field generated by Synchronet and its utilities is a mathematical sum of the area-unique ''<​msgnum>''​ and a number derived from the date and time the message was created so as to maximize the use of the allocated 32-bits. The serial number will be unique among all the messages generated by a Synchronet-system in a single message area (echo), but is not guaranteed to be unique, by itself, among //all// the FTN-connected message areas of a single Synchronet-system. The ''​serialno''​ field //alone// does **not** constitute a unique message identifier, so don't try to use it as one!
  
 **But it doesn'​t //look// like other other FTN MSGID'​s!?​!** **But it doesn'​t //look// like other other FTN MSGID'​s!?​!**

In Other Languages