config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
config_echomail_nodes [2019/03/16 17:06] – content updates avon | config_echomail_nodes [2023/01/03 01:33] – added more netmail logic info avon | ||
---|---|---|---|
Line 34: | Line 34: | ||
E EchoMail Exports | E EchoMail Exports | ||
F FileBone Exports | F FileBone Exports | ||
+ | R Reset Stats | ||
1 Send AreaFix | 1 Send AreaFix | ||
2 Send FileFix | 2 Send FileFix | ||
Line 46: | Line 47: | ||
The ' | The ' | ||
+ | |||
+ | 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/ | 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/ | ||
Line 70: | Line 73: | ||
| | ||
Route Info │ 21:* | Route Info │ 21:* | ||
+ | | ||
Max PKT Size │ 512 | Max PKT Size │ 512 | ||
Max ARC Size │ 2048 | Max ARC Size │ 2048 | ||
Line 82: | Line 86: | ||
=== Active === | === Active === | ||
- | A simple yes/now setting - unless you set this to ' | + | A simple yes/now setting - unless you set this to ' |
=== Description === | === Description === | ||
Line 105: | Line 109: | ||
* Binkp - Fidpoll will send/ | * Binkp - Fidpoll will send/ | ||
- | * FTP - Fidopoll | + | * FTP - MIS POLL will send/ |
- | * Directory - Fidopoll | + | * Directory - MIS POLL will send bundles to/from locally configured inbound and outbound directories instead of using BINKP or FTP. |
Depending on the option you choose here, pages 4, 5, or 6 of the configuration settings will need to be configured also. | Depending on the option you choose here, pages 4, 5, or 6 of the configuration settings will need to be configured also. | ||
Line 153: | Line 157: | ||
NetMail message bases do not need to be linked to any Echomail nodes in order for Mystic to attempt exporting. | NetMail message bases do not need to be linked to any Echomail nodes in order for Mystic to attempt exporting. | ||
- | Mystic, when routing | + | === Netmail |
- | the Route Info. | + | |
- | If there is no direct match, Mystic will then look at the Route Info for each Echomail | + | Netmail will first always try to route using the Route strings defined for each node. |
+ | |||
+ | If no route is found from the Route string then Mystic will now attempt to automatically route Netmail based on some basic address logic: | ||
+ | |||
+ | * First it will look for a direct address match in Echomail Nodes and if one is found it will route directly to the node. | ||
+ | |||
+ | * If there is no direct match then Mystic will perform some logic to select the best node that it can find. If your system gets a Netmail for 1:123/123.1 and there is no direct match, Mystic will look for a 1:123/123 node. If there isn't one, then it will look for a 1:123 node with priority given to the 1:123/1 if exists. | ||
+ | |||
+ | * If a node is still not found then Mystic will look for a zone match, and finally if no zone match is found then the Netmail will fail to route. | ||
+ | |||
+ | To further expand on the automatic Netmail routing logic, Mystic will now perform a FidoNet fuzzy zone match when auto routing Netmail. | ||
+ | |||
+ | To reiterate: For almost everyone, there is never a need touch the Route field in your Echomail node editor. | ||
+ | |||
+ | This 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 === | === Max PKT Size === | ||
Line 168: | Line 189: | ||
=== Use Filebox === | === Use Filebox === | ||
- | A Filebox is a directory you can place any file in to that will be sent to your EchoMail Node when you next poll it using Fidopoll | + | A Filebox is a directory you can place any file in to that will be sent to your EchoMail Node when you next poll it using MIS POLL or it polls your Mystic BBS. |
There are three options for this setting | There are three options for this setting | ||
* No - Don't enable this feature | * No - Don't enable this feature | ||
- | * Yes- Send files to EchoMail Node if you Fidopoll | + | * Yes- Send files to EchoMail Node if you MIS POLL it or if it polls your Mystic BBS |
* Hold - Only send files to the EchoMail Node if it polls your Mystic BBS | * Hold - Only send files to the EchoMail Node if it polls your Mystic BBS | ||
// | // | ||
Line 195: | Line 216: | ||
Defines the drive and directory pathway that is associated with the Filebox to be used with this EchoMail Node. If the directory does not exist then Mystic will offer to create it. | Defines the drive and directory pathway that is associated with the Filebox to be used with this EchoMail Node. If the directory does not exist then Mystic will offer to create it. | ||
+ | |||
+ | === Crash Limiter === | ||
+ | |||
+ | This feature is still being developed. The idea is that when MIS POLL sends files via BINKP it will skip queueing any files for sending larger than this value. It forces EchoMail nodes to poll and collect these files vs a HUB system spending time transferring large files to them. The value is defined in kilobytes. | ||
+ | |||
+ | At present there is no logic built in to this feature. That means if you set say a value of 1000 Mystic will send .TIC files that accompany a hatched file to an EchoMail node but if the actual hatched file is larger than 1000kb it will not send at the same time. This can cause issues for the receiving EchoMail node. | ||
+ | |||
+ | Keep an eye on this section of the Wiki and we'll update it as the feature evolves ;-) | ||
==== Page 2 of 6 - Security ==== | ==== Page 2 of 6 - Security ==== | ||
+ | ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21: | ||
PKT Password | PKT Password | ||
- | FIX Password | + | FIX Password |
- | TIC Password | + | TIC Password |
- | | + | |
- | | + | |
- | │ 6:Dir Toss | + | |
│ | │ | ||
│ | │ | ||
Line 235: | Line 265: | ||
Without this password set your Mystic BBS will ignore the files it receives and/or move them in to the BAD directory defined in the [FileToss] stanza of your MUTIL .ini file | Without this password set your Mystic BBS will ignore the files it receives and/or move them in to the BAD directory defined in the [FileToss] stanza of your MUTIL .ini file | ||
+ | |||
+ | === Encryption Key === | ||
+ | |||
+ | Echomail nodes now have an " | ||
+ | |||
+ | This is done in a way that is completely transparent to unsupporting systems, meaning that you can still route netmail through systems and they will not harm the encrypted netmails! | ||
+ | |||
+ | The other echomail node must of course have the same key configured for your node in order to decrypt the netmail when it arrives. | ||
+ | |||
+ | When routing Netmail, Mystic will intelligently re-encrypt the message between routing points when possible. | ||
=== Security Level === | === Security Level === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below. |
=== Access Flags === | === Access Flags === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | 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 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 | ||
+ | |||
+ | 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]]. | ||
+ | |||
+ | Hatch File EACS: g2|s255|fH|u10 | ||
+ | |||
+ | 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< | ||
+ | equal to < | ||
+ | g< | ||
+ | to < | ||
+ | f< | ||
+ | between A to Z. | ||
+ | u< | ||
+ | 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/ | ||
+ | |||
+ | 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 " | ||
+ | |||
+ | 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. | ||
==== Page 3 of 6 - Groups ==== | ==== Page 3 of 6 - Groups ==== | ||
- | Echo Group 01 │ None | + | Echo Group 01 │ fsxNet |
Echo Group 02 │ None 2:Security | Echo Group 02 │ None 2:Security | ||
Echo Group 03 │ None 3:GROUPS | Echo Group 03 │ None 3:GROUPS | ||
Line 263: | Line 333: | ||
| | ||
- | Placeholder text - this feature under development 1.12 A38 | + | Define which EchoMail groups |
==== Page 4 of 6 - BinkP==== | ==== Page 4 of 6 - BinkP==== | ||
- | + | ||
- | BINKP Hostname │ agency.bbs.nz: | + | BINKP Hostname │ net1.fsxnet.nz 1:General |
IP Type │ IPV4 2:Security | IP Type │ IPV4 2:Security | ||
- | | + | |
Time Out │ 30 4:BINKP | Time Out │ 30 4:BINKP | ||
Block Size │ 16384 5:FTP | Block Size │ 16384 5:FTP | ||
| | ||
Hide AKAs │ Yes | Hide AKAs │ Yes | ||
- | │ | ||
│ | │ | ||
│ | │ | ||
Line 283: | Line 352: | ||
│ | │ | ||
│ Page 4 of 6 | │ Page 4 of 6 | ||
+ | |||
- | A Binkp session | + | A Binkp section |
=== BINKP Hostname === | === BINKP Hostname === | ||
- | Set the DNS hostname (and port if required) for the EchoMail Node you will poll using Fidopoll. | + | Set the DNS hostname (and port if required) for the EchoMail Node you will poll using MIS POLL. |
=== IP Type === | === IP Type === | ||
- | Do you wish to use IPV4 or IPV6 when using Fidopoll | + | Do you wish to use IPV4 or IPV6 when using MIS POLL to connect to this system? |
=== Password === | === Password === | ||
- | Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using Fidopoll | + | Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using MIS POLL or it connects to your Mystic BinkP server and attempts to send your system Echomail, Netmail and/or other files. |
- | This password is case sensitive. Be warned some non-Mystic systems have issues with this. Best advice keep everything UPPERCASE to avoid hassles. | + | This password is case sensitive. Be warned some non-Mystic systems have issues with this. Best advice keep everything UPPERCASE |
=== Timeout === | === Timeout === |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon