User Tools

Site Tools


config_echomail_nodes

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
config_echomail_nodes [2019/03/16 17:39] – echomail secuity avonconfig_echomail_nodes [2019/03/16 17:41] – echomail secuity avon
Line 257: Line 257:
 === Security Level === === Security Level ===
  
-You can set ACS rules for this EchoMail node. +You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below.
  
 === Access Flags === === Access Flags ===
  
-You can set access flags for this EchoMail Node.+You can set access flags for this EchoMail Node. Refer to discussion info in the Echomail Node Security section below.
  
 === Echomail Node Security ==== === Echomail Node Security ====
  
-The beginning of Echomail node security is here!  The easiest way to think about how this system works is to relate an Echomail node to the way security works for a user in your BBS.  Each node will have a security   level, access flags, and can be a member of many Echomail groups (up to 65000 echomail groups can be defined).+The beginnings of Echomail node security is here!  The easiest way to think about how this system works is to relate an Echomail node to the way security works for a user in your BBS.  Each node will have a security   level, access flags, and can be a member of many Echomail groups (up to 65000 echomail groups can be defined).
  
-Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the user ACS strings that we're familiar with.  For example, you might have "Hatch File EACS" in a file base where you could say that you wanted only echomail nodes within a particular group to be able to hatch files, or a particular security level or access flag(s), or even by static echomail node ID.  For example:+Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the [[access_control|user ACS strings that we're familiar with]].  For example, you might have "Hatch File EACS" in a file base where you could say that you wanted only echomail nodes within a particular group to be able to hatch files, or a particular security level or access flag(s), or even by static echomail node ID.  For example:
  
      Hatch File EACS: g2|s255|fH|u10      Hatch File EACS: g2|s255|fH|u10
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki