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 revision
Previous revision
config_echomail_nodes [2019/03/16 17:02] – content updates avonconfig_echomail_nodes [2023/01/03 01:49] (current) – [Page 4 of 6 - BinkP] upload/download limits added 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 'Filebone Exports' option allows you to define which file bases you want to link to the EchoMail Node. 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! 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    Export Type    │ Crash
    Route Info     │ 21:*    Route Info     │ 21:*
 +   Uplink         │ No
    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 'Yes' it will be ignored by Mystic, Fidopoll and MUTIL when various processes are run.+A simple yes/now setting - unless you set this to 'Yes' it will be ignored by Mystic, MIS POLL and MUTIL when various processes are run.
  
 === Description === === Description ===
Line 88: Line 92:
 Define the name of the system you are connecting with. Define the name of the system you are connecting with.
  
-=== Zone ===+=== SysOp Name ===
  
-Set the Network Zone of this EchoMail Node.+Define the name of the system operator running this system. You can set an alias s/he uses or their real name
  
-=== Net ===+=== Address ===
  
-Set the Network Net of this EchoMail Node +Set the Network Zone, NetNode and Point (not often used) of this EchoMail Node. e.g. 21:1/100
- +
-=== Node === +
- +
-Set the Network Node of this EchoMail Node  +
- +
-=== Point === +
- +
-Set the Network Point of this EchoMail Node (often not used)+
  
 === Domain === === Domain ===
  
-Set the Domain Name of Network e.g. fsxnet+Set the Domain Name of Network. It's best to keep it lowercase and check you spell it correctly. e.g. fsxnet
  
 === Session Type === === Session Type ===
Line 113: Line 109:
  
   * Binkp - Fidpoll will send/receive bundles with this EchoMail Node using the BinkP protocol.   * Binkp - Fidpoll will send/receive bundles with this EchoMail Node using the BinkP protocol.
-  * FTP - Fidopoll will send/receive bundles with this EchoMail Node using the FTP protocol. +  * FTP - MIS POLL will send/receive bundles with this EchoMail Node using the FTP protocol. 
-  * Directory - Fidopoll will send bundles to/from locally configured inbound and outbound directories instead of using BINKP or FTP.+  * 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 161: 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, will first compare the destination address against all configured echomail nodes.  If there is a direct match Mystic will route the Netmail automatically to that node without reviewing +=== Netmail Routing Logic ===
-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.+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 node is still not found then Mystic will look for a zone matchand 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.  If a zone is between 1 and 6 they will find a match to a hub which is also part of a zone 1 through 6 if no other (better) routing match could be found. 
 + 
 +To reiterate: For almost everyone, there is never a need touch the Route field in your Echomail node editor.  If you ever want to test where a Netmail will route you can type "mis poll route <address>" and it will tell you where Mystic will route a message to that address based on your current configuration. 
 + 
 +This system allows for Netmail to work automatically without any knowledge of routing being required for most people while still allowing full control for power users. 
 + 
 +=== 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 176: 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 or it polls your Mystic BBS.+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 it or if it polls your Mystic BBS+  * 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 203: 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:1/100@fsxnet) ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
    PKT Password   │                                           1:General    PKT Password   │                                           1:General
-   FIX Password   │ *******                                   2:SECURITY +   FIX Password   │ *****                                     2:SECURITY 
-   TIC Password   │ *******                                   3:Groups +   TIC Password   │ *****                                     3:Groups 
-   Security Level │ 0                                         4:BinkP +   Encryption Key │ *****                                     4:BinkP 
-   Access Flags   │ --------------------------                5:FTP +   Security Level │ 0                                         5:FTP 
-                  │                                           6:Dir Toss+   Access Flags   │ --------------------------                6:Dir Toss
                   │                   │
                   │                   │
Line 243: 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 "Encryption Key" option.  When this option is set to a non-blank value, Mystic will encrypt all of the contents of Netmail messages to this node with an AES-256 encryption.  This completes a fully encrypted echomail solution as both transport and private messages are secured.
 +
 +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 encryption also hides the message subject, so when combined with Area/Filefix passwords will no longer be readable. You must have Cryptlib installed for this to work.
 +
 +The other echomail node must of course have the same key configured for your node in order to decrypt the netmail when it arrives.  This works the same way as any other password setting in echomail nodes.
 +
 +When routing Netmail, Mystic will intelligently re-encrypt the message between routing points when possible.  In other words if you have a point system who sends from 555:1/2.1 to 555:1/1 but is routed through 555:1/2,   Mystic at 555:1/2 will know that it has an encryption agreement between both 555:1/2.1 and 555:1/1 so it will decrypt the message from 555:1/2.1 and then re-encrypt it for 555:1/1 before routing it.
  
 === 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   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: 
 + 
 +     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<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.
  
 ==== Page 3 of 6 - Groups ==== ==== Page 3 of 6 - Groups ====
  
-   Echo Group 01  │ None                                      1:General+   Echo Group 01  │ fsxNet                                    1:General
    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 271: Line 333:
      
  
-Placeholder text - this feature under development 1.12 A38+Define which EchoMail groups this EchoMail node is a member of.
  
 ==== Page 4 of 6 - BinkP==== ==== Page 4 of 6 - BinkP====
  
- +   BINKP Hostname │ net1.fsxnet.nz                            1:General
-   BINKP Hostname │ agency.bbs.nz:24556                       1:General+
    IP Type        │ IPV4                                      2:Security    IP Type        │ IPV4                                      2:Security
-   Password       │ *******                                   3:Groups +   Server Type    │ Normal                                    3:Groups 
-   Time Out       │ 30                                        4:BINKP +   Password       │ ********                                  4:BINKP 
-   Block Size     │ 16384                                     5:FTP +   Time Out       │ 30                                        5:FTP 
-   CRAM-MD5       │ Yes                                       6:Dir Toss+   Block Size     │ 16384                                     6:Dir Toss 
 +   CRAM-MD5       │ Yes
    Hide AKAs      │ Yes    Hide AKAs      │ Yes
-                  │ +   Escape Mode    │ Auto 
-                  │ +   Upload Limit   │ 0 
-                  │ +   Download Limit │ 0
-                  +
                   │                   │
                   │                   │
Line 292: Line 353:
                   │                                          Page 4 of 6                   │                                          Page 4 of 6
            
-A Binkp session has the following options you should set:+A Binkp section has the following options you should look at and in most cases set up:
  
 === 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 to connect to this system?+Do you wish to use IPV4 or IPV6 when using MIS POLL to connect to this system? Or do you wish to set a preferred connection type and then a fallback type? e.g. IPV6 + IPV4 or IPV4 + IPV6 
 + 
 +=== Server Type === 
 + 
 +There are four possible options for this setting: 
 + 
 +  * Normal                  : Do not use SSL at all 
 +  * Direct SSL              : Connect with a direct SSL connection 
 +  * StartTLS (If Available) : Use TLS when available 
 +  * StartTLS (Required)     : Always require SSL connection to remote 
 + 
 +The StartTLS Required option will refuse to authenticate with any server that does not offer the opportunistic TLS upgrading. These features require that CryptLib is present and detected by Mystic.
  
 === Password === === Password ===
  
-Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using Fidopoll or it connects to your Mystic BinkP server and attempts to send your system Echomail, Netmail and/or other files.+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 and limited to no more than 8 characters to avoid hassles.
  
 === Timeout === === Timeout ===
Line 323: Line 395:
  
 Hide alternative network addresses during a BinkP handshake. When your system polls this EchoMail Node will it only show the network address you have set up for the same Zone this EchoMail Node has in common with or it will show all your defined EchoMail addresses? Hide alternative network addresses during a BinkP handshake. When your system polls this EchoMail Node will it only show the network address you have set up for the same Zone this EchoMail Node has in common with or it will show all your defined EchoMail addresses?
 +
 +=== Escape Mode ===
 +
 +Mystic's BINKP server now has a default "Escape mode" option which will  apply to any unknown connections that do not have a configuration in the Echomail nodes.  Echomail nodes have their own individual setting for this    in the node editor.
 +
 +This setting determines how Mystic will escape special characters in filenames and defaults to the Auto setting.
 +
 +When set to **Auto**, Mystic will automatically try to determine the escape mode by using the VERSION frame sent by the mailer.  If no version frame is found, Mystic will use FTS standard modern \x## escape mode.
 +
 +When set to **Legacy**, Mystic will use the \## format of file escaping which is used in some legacy mailers such as Argus, Internet Rex, and older versions of Mystic.
 +
 +When set to **Modern**, Mystic will use the \x## format which is preferred or even required by some newer mailers such as BinkD, Radius, and BinkIT.
 +
 +It is highly recommended to always keep these set to AUTO unless there is a very specific reason not to.  The escape mode will be logged after authentication if the loglevel is set to Verbose or higher.
 +
 +=== Upload Limit ===
 +
 +Set the upload speed limit: (Used when you send files to this node)
 +
 +BINKP has the ability to limit the bandwidth used when sending or  receiving files.  Setting any of these values to 0 disables the limit and causes them to operate at full speed.  Any non-zero value sets the maximum rate in Kilobytes (KB) to use for the connection. This setting overrides MIS POLL/BINKP settings if enabled.
 +
 +=== Download Limit ===
 +
 +Set the download speed limit: (Used when you receive files from this node). This setting overrides MIS POLL/BINKP settings if enabled.
  
 ==== Page 5 of 6 - FTP ==== ==== Page 5 of 6 - FTP ====
config_echomail_nodes.1552773766.txt.gz · Last modified: 2019/03/16 17:02 by avon

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki