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
Next revision
Previous revision
faq:misc [2018/07/06 14:17]
digital man [SBBSList] Updated for sbbslist v4
faq:misc [2019/01/29 02:36] (current)
digital man [SBBSList] Updated with links to dynamically generated HTML versions of the list
Line 5: Line 5:
   * [[#​deleted_msgs|Why is it that deleted messages still appear in message bases]]?   * [[#​deleted_msgs|Why is it that deleted messages still appear in message bases]]?
   * [[#​new_user_feedback|How do I disable the New User Feedback requirement]]?​   * [[#​new_user_feedback|How do I disable the New User Feedback requirement]]?​
 +  * [[#​no_guest|How do I disable the Guest user account]]?
   * [[#​sbbslist|How do I get my BBS listed on the Synchronet BBS List]]?   * [[#​sbbslist|How do I get my BBS listed on the Synchronet BBS List]]?
   * [[#​time_stamp_error|Why am I getting a "Daily stats time stamp" error]]?   * [[#​time_stamp_error|Why am I getting a "Daily stats time stamp" error]]?
Line 45: Line 46:
 enter that user's number here. enter that user's number here.
  
 +===== No Guest =====
 +:?: **Question:​**\\
 +How do disable the Guest user account on the BBS?
 +
 +
 +:!: **Answer:​**\\
 +You don't have to have a Guest (G-[[access:​restrictions|restricted]] user) account. If you don't create a Guest account to begin with, you won't have one. If you created a Guest account and you don't want it, then simply deleting the user account from the user base will work. However, without a Guest account, anonymous FTP access will not be available and some web UI elements may not function as is normally expected. To keep the Guest account but disallow logins to the Terminal Server (the traditional BBS user experience),​ set [[util:​SCFG]]->​Nodes->​Node 1->Logon Requirements->​Requirement String to:
 +  NOT GUEST
 +
 +Doing this will cause terminal logons as "​Guest"​ to be rejected with the following (configurable) message:
 +  You do not have sufficient access for this node.
 +
 +**Note:​**\\  ​
 +You do not have to configure the other nodes (Node 2, 3, etc.) in [[util:​SCFG]] so long as they fall within the range of the ''​FirstNode''/''​LastNode''​ key values from the [[config:​sbbs.ini#​BBS|[BBS]]] section of your ''​[[dir:​ctrl]]/​[[config:​sbbs.ini]]''​ file.
  
 ===== SBBSList ===== ===== SBBSList =====
Line 54: Line 69:
 ([[module:​sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should ([[module:​sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should
 be automatically exported to the DOVE-Net SYNCDATA echo which will then be be automatically exported to the DOVE-Net SYNCDATA echo which will then be
-propagated to [[bbs:​Vertrauen]] and every other BBS on DOVE-Net. The ''​sbbslist.html''​+propagated to [[bbs:​Vertrauen]] and every other BBS on DOVE-Net. The ''​[[http://​synchro.net/​sbbslist.html|sbbslist.html]]''​
 page is automatically generated on Vertrauen every night at midnight page is automatically generated on Vertrauen every night at midnight
-(Pacific time), so wait a day or so for your entry to appear on the list.+(Pacific time), so wait a day or so for your entry to appear on the list. You can also check a dynamically generated HTML BBS list [[http://​cvs.synchro.net/​sbbslist.ssjs|here]] or [[http://​web.synchro.net/?​page=More/​999-sbbslist.xjs|here]].
 If it doesn'​t appear, verify that that your BBS entry was properly If it doesn'​t appear, verify that that your BBS entry was properly
 exported (as a message) to the SYNCDATA message area. The timed events exported (as a message) to the SYNCDATA message area. The timed events
Line 172: 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