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:qwk [2020/12/24 15:29] – [Packet Naming] List the known synonyms for QWK-ID. digital manref:qwk [2023/12/12 20:54] (current) – [Original QWK format] Convert FTP links to HTTP digital man
Line 167: Line 167:
  
 == Character Set == == Character Set ==
-Header field values may each be up to 1024 US-ASCII characters length. When "high ASCII" characters are included in any header field values, the IBM CP437 character set is assumed unless there is an indication that the header fields are in UTF-8 format, in which case **all** header fields, for a particular message, with "high ASCII" characters must be in UTF-8 format. The indication of UTF-8 characters in the body text is done through the presence of either the ''X-FTN-CHRS: UTF-8 4'' header field or a ''Content-Type: text/*; charset=utf-8'' header field.+Header field values may each be up to 1024 US-ASCII characters in length. When "high ASCII" characters are included in any header field values, the IBM CP437 character set is assumed unless there is an indication that the header fields are in UTF-8 format, in which case **all** header fields, for a particular message, with "high ASCII" characters must be in UTF-8 format. As with FidoNet messages, the message body text and header fields must share the same encoding. If the "Utf8" ''HEADERS.DAT'' header field value for a message is set to "true", then all the headers fields and the body text of that message are to be interpreted as though they were UTF-8 encoded.
  
 == Example == == Example ==
Line 192: Line 192:
 | Utf8           | Header fields and body text use the UTF-8 character set (when ''true'') rather than CP437 (the default) | | Utf8           | Header fields and body text use the UTF-8 character set (when ''true'') rather than CP437 (the default) |
 | Message-ID     | RFC822-style unique message identifier | | Message-ID     | RFC822-style unique message identifier |
-| WhenWritten    | Date/time (in ISO-8601 format) and timezone (in hexadecimal [[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/smblib/smbdefs.h|SMB format]]) |+| In-Reply-To    | RFC822-style message ID of message that this message is a reply to, if relevant | 
 +| WhenWritten    | Date/time (in ISO-8601 format) and timezone (in hexadecimal [[https://gitlab.synchro.net/main/sbbs/-/blob/master/src/smblib/smbdefs.h|SMB format]]) |
 | WhenImported   | Date/time/zone message was imported into the originating system's message base | | WhenImported   | Date/time/zone message was imported into the originating system's message base |
 | WhenExported   | Date/time/zone message was exported from the originating system's message base | | WhenExported   | Date/time/zone message was exported from the originating system's message base |
Line 202: Line 203:
 | SenderProtocol | Name of protocol used by sender (e.g. "Telnet", "SSH", "RLogin", "SMTP, "NNTP", "HTTP", etc.) | | SenderProtocol | Name of protocol used by sender (e.g. "Telnet", "SSH", "RLogin", "SMTP, "NNTP", "HTTP", etc.) |
 | Organization   | Name of sender's organization (e.g. BBS) | | Organization   | Name of sender's organization (e.g. BBS) |
-| Reply-To       | Address to direct replies |+| Reply-To       | The network address to direct replies to this message |
 | Subject        | Message subject | | Subject        | Message subject |
 | To             | Message recipient name | | To             | Message recipient name |
Line 301: Line 302:
  
 ===== Original QWK format ===== ===== Original QWK format =====
-  * [[ftp://vert.synchro.net/main/BBS/QWKSPC11.ZIP]] +  * [[http://vert.synchro.net/filse/Main/BBS/QWKSPC11.ZIP]] 
-  * [[ftp://vert.synchro.net/modem.madness/SMMNETML/QWKINFO.ZIP]] +  * [[http://vert.synchro.net/files/modem.madness/SMMNETML/QWKINFO.ZIP]] 
-  * [[ftp://vert.synchro.net/modem.madness/SMMNETML/QWKLAY16.ZIP]] +  * [[http://vert.synchro.net/files/modem.madness/SMMNETML/QWKLAY16.ZIP]] 
-  * [[ftp://vert.synchro.net/modem.madness/SMMOLMRS/QWKDOCS.ZIP]] +  * [[http://vert.synchro.net/files/modem.madness/SMMOLMRS/QWKDOCS.ZIP]] 
-  * [[ftp://vert.synchro.net/modem.madness/SMMMAXIM/MXMS_161.ZIP]]+  * [[http://vert.synchro.net/files/modem.madness/SMMMAXIM/MXMS_161.ZIP]] 
 + 
 +==== Conference Names ==== 
 + 
 +The message area (conference) names included in the ''CONTROL.DAT'' file are only used for reader information/display purposes. The conference *numbers* are references used to identify specific message areas between the reader (or QWKnet node) and the host/hub BBS. 
 + 
 +=== Length === 
 +According to "QWK Mail Packet File Layout" (qwklay) by Patrick Y. Lee (version 1.6 - December 19, 1992), the conference names are limited to "13 characters or less". 
 + 
 +According to "The Mysterious QWK-File Format" by Jeffery Foy (April 25, 1991), the conference names are limited to "10 characters or less". 
 + 
 +According to "QWKE Specifications 1.02" by Peter Rocca, "conference area names are no longer limited to 13 characters, they are limited to 255 characters now [in QWKE]".
  
 ===== Extended QWK (QWKE) Format ===== ===== Extended QWK (QWKE) Format =====
-  * [[ftp://vert.synchro.net/main/BBS/qwke.txt]].+  * [[http://vert.synchro.net/files/main/BBS/qwke.txt]].
  
    
Line 315: Line 327:
   * [[network:DOVE-Net]]   * [[network:DOVE-Net]]
   * [[:ref:|Reference Library]]   * [[:ref:|Reference Library]]
 +  * [[https://www.theregister.com/2021/07/22/qwk_swatting_death/]]
  
 {{tag>qwk}} {{tag>qwk}}
  

Trace: