Differences

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

--- config_echomail_nodes [2019/03/16 18:12] – echomail secuity updates avon
+++ config_echomail_nodes [2022/09/26 01:38] – reset stats avon
@@ Line 34: / Line 34: @@
                                E EchoMail Exports
                                F FileBone Exports
+                               R Reset Stats
 Send AreaFix
 Send FileFix
@@ Line 46: / Line 47: @@
 The 'Filebone Exports' option allows you to define which file bases you want to link to the EchoMail Node.
+The 'Reset Stats' option lets you reset the Echomail Node stats that Mystic tracks when traffic is sent to / received from the node.
 The next three options allow you to quickly and easily contact an EchoMail node to communicate with the SysOp or to add/remove message and file bases or anything else the Area/Filefix commands allow without having to fumble around with addresses and passwords!
@@ Line 70: / Line 73: @@
    Export Type    │ Crash
    Route Info     │ 21:*
+   Uplink         │ No
    Max PKT Size   │ 512
    Max ARC Size   │ 2048
@@ Line 156: / Line 160: @@
 the Route Info.
-If there is no direct match, Mystic will then look at the Route Info for each Echomail node (starting at the first entry) until it finds a match and redirect netmail through that system.
+If there is no direct match, Mystic will then look at the Route Info for each Echomail Node (starting at the first entry) until it finds a match and redirect Netmail through that system.
+=== Uplink ===
+This flag can either be set to Yes or No for each Echomail Node.  It works in tandem with MIS POLL UPLINK and is similar to the MIS POLL FORCED command, but instead will only force a poll of Echomail Nodes with the Uplink flag set to Yes.
 === Max PKT Size ===
@@ Line 265: / Line 273: @@
 === Echomail Node Security ====
-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).
+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 [[config_echomail_groups|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 [[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: