Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

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 revisionPrevious revision
Next revision		Previous revision
ref:qwknet [2012/07/19 19:58] – [Examples] Replaced CP437 lines with ASCII chars digitalmanref:qwknet [2021/06/28 09:53] (current) – [Examples] BoonDock
Line 19: Line 19:
  
 QWK IDs (AKA BBSID) consist of between two and eight valid DOS characters and the first character must be alphabetic. QWK IDs must not contain the '@' character. It is extremely beneficial if all QWK IDs are unique in a given network of systems. QWK IDs that do not match this format may work for basic QWK IDs (AKA BBSID) consist of between two and eight valid DOS characters and the first character must be alphabetic. QWK IDs must not contain the '@' character. It is extremely beneficial if all QWK IDs are unique in a given network of systems. QWK IDs that do not match this format may work for basic
-QWKnet functions, but many features may not work. QWK IDs are always considered case insensitive. The strings "SYSOP" and "NETMAIL" must are not valid QWK IDs.+QWKnet functions, but many features may not work. QWK IDs are always considered case insensitive. The strings "SYSOP" and "NETMAIL" are not valid QWK IDs.
  
 A QWKnet node on a Synchronet BBS must be created specifically for QWK networking. This is done by using the node's QWK ID as the user name on the BBS and the sysop must give the account the 'Q' restriction. This restriction allows the uploaded REP packets to come from any user name (AKA Net Status) and automatically eliminates non-QWK networked sub-boards from the QWK packets. The 'Q' restriction causes the QWK menu to immediately come up at logon (rather than the normal "user" logon procedure), taglines are added to locally created messages being exported to REP packets, as well as other behavior differences from normal "user" accounts. Synchronet creates a NETFLAGS.DAT file for 'Q' restricted accounts that haven't disabled CONTROL files in the QWK packets, though Synchronet itself does not ever use the NETFLAGS.DAT - it's created for compatibility with non-Synchronet QWKnet nodes. A QWKnet node on a Synchronet BBS must be created specifically for QWK networking. This is done by using the node's QWK ID as the user name on the BBS and the sysop must give the account the 'Q' restriction. This restriction allows the uploaded REP packets to come from any user name (AKA Net Status) and automatically eliminates non-QWK networked sub-boards from the QWK packets. The 'Q' restriction causes the QWK menu to immediately come up at logon (rather than the normal "user" logon procedure), taglines are added to locally created messages being exported to REP packets, as well as other behavior differences from normal "user" accounts. Synchronet creates a NETFLAGS.DAT file for 'Q' restricted accounts that haven't disabled CONTROL files in the QWK packets, though Synchronet itself does not ever use the NETFLAGS.DAT - it's created for compatibility with non-Synchronet QWKnet nodes.
Line 26: Line 26:
 When calling a Synchronet BBS for QWK packets, conference numbers will start When calling a Synchronet BBS for QWK packets, conference numbers will start
 at 0 (for E-mail) and then jump to 1001 or 2001 or a similar number. at 0 (for E-mail) and then jump to 1001 or 2001 or a similar number.
-The thousands place represents the message Group number and the hundreds place +The thousands and more significant places represent the message Group number and the less significant places 
-represents the Sub-board number within that group. Conference numbers are+represent the Sub-board number within that group. Conference numbers are
 not necessarily consecutive, though they are (at this time) always sequential. not necessarily consecutive, though they are (at this time) always sequential.
 The CONTROL.DAT file will contain a list of all the conferences (and numbers) The CONTROL.DAT file will contain a list of all the conferences (and numbers)
Line 126: Line 126:
 Note: Set message pointers for all conferences Note: Set message pointers for all conferences
  
-Subj: FREQ <filename>+Subj: FREQ &lt;filename>
 Note: File Request from file transfer database (not attachments) Note: File Request from file transfer database (not attachments)
  
Line 309: Line 309:
 Yellow     Y 3 Yellow     Y 3
 Blue     B 4 Blue     B 4
-Magenta     M  5+Magenta     M 5
 Cyan     C 6 Cyan     C 6
 White     W 7 White     W 7
Line 433: Line 433:
 03/20/95 WILDHARE:NITEMOVE/TLOC 03/20/95 WILDHARE:NITEMOVE/TLOC
 </file> </file>
 +[[https://elgato.synchronetbbs.org/netmaps/ELGATO-NodeMap.html|Larger Sample]]{{:ref:qwknetmap.png?400|QWK Node Map}}
  
 Mail originating on VERT would NOT contain an @VIA: line when sent to the Mail originating on VERT would NOT contain an @VIA: line when sent to the

Trace: