From 0690591048ba1ea7a09abad952b7b626a1856b1e Mon Sep 17 00:00:00 2001
From: rswindell <>
Date: Sat, 2 Jun 2007 19:03:30 +0000
Subject: [PATCH] Added specific notes about requiring sysops give Guest
 accounts the 'P' or 'N' restrictions (though the 'P' restriction should
 normally already be there).

---
 docs/dove-net.txt | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/dove-net.txt b/docs/dove-net.txt
index 9e82f2b5dc..2b866db33d 100644
--- a/docs/dove-net.txt
+++ b/docs/dove-net.txt
@@ -97,6 +97,9 @@ years ago.
 DOVE-Net is not a democracy. You are not guaranteed "free speech" or
 "equal opportunity". DOVE-Net access is a privilege, not a right.
 
+The sysops of DOVE-Net Node BBSes are expected to enforce the "Access
+Requirements" of DOVE-Net, as specified later in this document.
+
 
 Instructions
 ============
@@ -420,6 +423,16 @@ The "DOVE-Net Sysops Only" conference MUST NOT be publicly accessible. This
 message area is for discussion among DOVE-Net Sysops ONLY. This is the
 correct message area to use for "test messages".
 
+If you have a Guest/Anonymous user account on your BBS, it MUST NOT have
+posting privilages to *any* of the DOVE-Net conferences. This can most
+easily be achieved in Synchronet by giving the "Guest" account the 'P'
+(posting) or 'N' (networked sub-board) restrictions. When the "Guest"
+account is created using the stock Synchronet 'makeguest.js' script, it will
+already have the 'P' restriction applied.
+
+If a DOVE-Net QWKnet node (BBS) does not follow these Access Requirements,
+it can, without warning or notice, lose some or all of its DOVE-Net access.
+
 
 Gateways
 --------
-- 
GitLab