Differences

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

--- config_echomail_nodes [2019/03/16 17:55] – added ssl/tls for echomail nodes avon
+++ config_echomail_nodes [2019/03/16 18:12] – echomail secuity updates avon
@@ Line 272: / Line 272: @@
 The above would say that any echomail node that is a member of Echomail group 2, OR any node that has a security level of 255 OR any Echomail node that has flag H can hatch files to that file base.  The Echomail node with the ID of #10 can also hatch.
+The following commands are available within EACS:
+      s<level>  : Echomail node must have a Security Level greater than or
+                  equal to <level>
+      g<number> : Echomail node must be a member of Echomail group ID equal
+                  to <number>
+      f<flag>   : Echomail node must have flag <flag> which is a letter
+                  between A to Z.
+      u<number> : Echomail node must have a unique ID of <number>.  This
+                  allows security to be applied to specific nodes (ID is
+                  shown in echomail node editor).
+Just like user ACS, Echomail ACS can also use parenthesis and boolean evaulation.
+Echomail ACS has been activated for message base subscribing/reading. A new field in each Message base configuration called "List EACS" defines the ACS requires for an echommail node to be able to see, subscribe, or unsubscribe to the area via AreaFix.
+Hubs can still manually link a base to a node regardless of security, so for example if you wanted to force nodes to always carry a specific echo area, you would give them the base and then set the "List EACS" to an  access they do not have (or even use % which is "never" in ACS terms). With this setup in place, the node cannot add or remove the area, they can only perform rescans.
 This is a very powerful system for managing an Echomail network, and EACS strings will be added to various functions in the future as seen fit.