Mystic BBS Wiki

User Tools

Site Tools

Trace:
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
Next revisionBoth sides next revision
config_echomail_nodes [2019/03/16 16:24] – [Page 4 of 6 - BinkP] avonconfig_echomail_nodes [2019/03/18 02:48] – content updates avon
Line 9: Line 9:
 From the opening screen you can see EchoMail Node that have already been created. From the opening screen you can see EchoMail Node that have already been created.
  
-                            EchoMail Nodes  +  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ EchoMail Nodes ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ 
-   ID   Active  Description                                   Network  +   ID   Act  Description               SysOp                           Network 
-   ──────────────────────────────────────────────────────────────────  +   ─────────────────────────────────────────────────────────────────────────── 
-   1       Yes  fsxNet HUB                                   21:1/100  +   1    Yes  fsxNet HUB (NET 1)        Paul Hayton                    21:1/100 
-   2       Yes  Agency HUB (FidoNet)                          3:770/1  +   2    Yes  Agency HUB (FidoNet)      Paul Hayton                     3:770/1 
-   ──────────────────────────────────────────────────────────────────  +   
-                      Press / for command list                      +   
 +   
 +   
 +   
 +   
 +   
 +   
 +   
 +   ─────────────────────────────────────────────────────────────────────────── 
 +                            Press / for command list 
 +  
  
 The / key reveals a command list menu. The / key reveals a command list menu.
  
-                                I Insert            +                               I Insert 
-                                C Copy              +                               C Copy 
-                                D Delete            +                               D Delete 
-                                E Exports          +                               E EchoMail Exports 
 +                               F FileBone Exports 
 +                               1 Send AreaFix 
 +                               2 Send FileFix 
 +                               3 Netmail SysOp 
 +                              
  
-This menu allows you to add or remove EchoMail Nodes from the system. You can also copy an existing EchoMail Node and paste (or move) the copied nodes to elsewhere on the list. The 'Exports' option allows you to define which Echomail message bases you want to link to the EchoMail Node.+This menu allows you to add or remove EchoMail Nodes from the system. 
 + 
 +You can copy an existing EchoMail Node and paste (or move) the copied nodes to elsewhere on the list. 
 + 
 +The 'Echomail Exports' option allows you to define which Echomail message 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 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! 
 + 
 +  * 'Send Areafix' option sends a Areafix request via Netmail to the selected EchoMail node. 
 +  * 'Send Filefix' option sends a Filefix request via Netmail to the selected EchoMail node. 
 +  * 'Netmail SysOp' option sends Netmail to the Sysop of the selected EchoMail node. 
 + 
 +If you want these options to work correctly for you it pays to set up the next section with the correct information and ensure you complete all the fields you need to.
  
 Pressing the Enter key on an existing EchoMail Node (or a new EchoMail node) reveals the following screen. Pressing the Enter key on an existing EchoMail Node (or a new EchoMail node) reveals the following screen.
-In this example an EchoMail Node has been set up for the fsxNet HUB (21:1/100) to send/receive Echomail and Netmail to/from. +In this example an EchoMail Node has been set up for the fsxNet HUB (21:1/100) to send/receive EchoMail and Netmail to/from. 
  
 ==== Page 1 of 6 - General ==== ==== Page 1 of 6 - General ====
  
 +  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21:1/100@fsxnet) ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
    Active         │ Yes                                       1:GENERAL    Active         │ Yes                                       1:GENERAL
-   Description    │ fsxNet HUB                                2:Security +   Description    │ fsxNet HUB (NET 1)                        2:Security 
-   Zone           │ 21                                        3:Groups +   SysOp Name     │ Paul Hayton                               3:Groups 
-   Net            │ 1                                         4:BinkP +   Address        │ 21:1/100                                  4:BinkP 
-   Node           │ 100                                       5:FTP +   Domain         │ fsxnet                                    5:FTP 
-   Point          │ 0                                         6:Dir Toss +   Session Type   │ BinkP                                     6:Dir Toss
-   Domain         │ fsxnet +
-   Session Type   │ BinkP+
    Archive Type   │ ZIP    Archive Type   │ ZIP
    Export Type    │ Crash    Export Type    │ Crash
Line 46: Line 73:
    Max ARC Size   │ 2048    Max ARC Size   │ 2048
    Use Filebox    │ No    Use Filebox    │ No
-   Filebox Dir    │                                          Page 1 of 6+   Filebox Dir    │ 
 +   Crash Limiter  │ 0 
 +                  │                                          Page 1 of 6 
 +  
  
 There are a number options you can set on page 1. There are a number options you can set on page 1.
Line 58: Line 88:
 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, Net, Node 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 173: Line 195:
  
 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 FidoPoll 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 213: Line 244:
  
 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 241: Line 312:
      
  
-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 │ agency.bbs.nz:24556                       1:General    BINKP Hostname │ agency.bbs.nz:24556                       1:General
    IP Type        │ IPV4                                      2:Security    IP Type        │ IPV4                                      2:Security
-   Password       │ *******                                   3:Groups+   Password       │ *****                                     3:Groups
    Time Out       │ 30                                        4:BINKP    Time Out       │ 30                                        4:BINKP
    Block Size     │ 16384                                     5:FTP    Block Size     │ 16384                                     5:FTP
    CRAM-MD5       │ Yes                                       6:Dir Toss    CRAM-MD5       │ Yes                                       6:Dir Toss
 +   Use SSL/TLS    │ No
    Hide AKAs      │ Yes    Hide AKAs      │ Yes
-                  │ 
                   │                   │
                   │                   │
Line 261: Line 332:
                   │                   │
                   │                                          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 ===
Line 270: Line 342:
 === 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 Fidopoll 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
  
 === Password === === Password ===
Line 276: Line 348:
 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 Fidopoll 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 289: Line 361:
  
 Use MD5 hashing when connecting as a client? This hides session passwords so they are not sent in plain text. It's a good idea to use this. Use MD5 hashing when connecting as a client? This hides session passwords so they are not sent in plain text. It's a good idea to use this.
 +
 +=== Use SSL/TLS ===
 +
 +Mystic BINKP server and FIDOPOLL now support opportunistic SSL (TLS v1.2+) using a proprietary extension of the BINKP protocol. This means that it will only work with other Mystic BBS clients and servers, but the author plans to document the extension and send it to the authors of other mailers in hopes that it can be standardized.
 +
 +EchoMail Nodes now have three settings which can be used when polling for new mail:
 +
 +      No     : FIDOPOLL will not use SSL extension at all
 +      Yes    : FIDOPOLL WILL use SSL if the server supports it
 +      Forced : FIDOPOLL will refuse to exchange mail with a server
 +               unless it supports SSL
 +
 +This setting is experimental at present so your mileage may vary. If you're having issues connecting to other systems it's best to set this to 'No' for now.
  
 === Hide AKAs === === Hide AKAs ===
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki