Differences

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

--- config_echomail_nodes [2019/03/16 17:21] – page 2 updates avon
+++ config_echomail_nodes [2019/03/16 17:24] – added enryption key details avon
@@ Line 244: / 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
+=== 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 ===