If you are upgrading to Taurus from a mailer listed below or wish to use Radius in conjunction with other mailer, you may easily import password configuration. Import passwords dialogue box is invoked from Config/Passwords, Import button. You may import override configuration as well.
You will be prompted for the path to BinkD configuration file. Radius doesn't support nested configuration files of BinkD, so if you keep BinkD passwords in a separate file, you should point to it. Radius will parse selected file in search of "NODE" keyword. Also, FTN addresses following "NODE" keyword must be in full 4D/5D notation. If your BinkD configuration file has shortened form of addresses (e.g. for nodes from your own zone/net) Radius would not import them. Radius supports only one pair Address/Password per line when importing BinkP configuration file.
You will be prompted for the path to Bink/+ configuration file. Radius supports nested configuration files of Bink/+, so if you keep Bink/+ passwords in a separate file, you shouldn't point to it unless all addresses are in full 4D/5D notation or this file has ADDRESS keyword. Radius will parse selected file in search of "ADDRESS" (default address for expanding shortened addresses), " INCLUDE" (nested configuration file) and "OVERRIDE" keywords.
You will be prompted for the path to T-Mail configuration file. Radius supports nested configuration files of T-Mail. Note that you should point to T-Mail main configuration file, not to "subst"- or "security-"file. Radius will parse selected file in search of the following keywords: "ADDRESS" (default address for expanding shortened addresses), "INCLUDE" (nested configuration file), "SUBSTLIST" (path to T-Mail file with substitutes; "PASSWORD" keyword will be in search there) and "SECURITY" (path to T-Mail file with passwords).
You will be prompted for the path to Xenia configuration file. Radius supports nested configuration files of Xenia. Radius will parse selected file in search of the following keywords "INCLUDE" (nested configuration file) and "PASSWORD" (password record) keyword. Also, FTN addresses following "PASSWORD" keyword must be in full 4D/5D notation. If your Xenia configuration file has shortened form of addresses (e.g. for nodes from your own zone/net) Radius would not import them. Xenia configuration file may specify several addresses to be bound to a password in a single line, Radius will properly import such entries.
You will be prompted for the path to FrontDoor passwords file (password.fd). FrontDoor configuration file is a binary file. Import of other data rather than passwords from FrontDoor is not supported. Other versions of FrontDoor rather then 2.12 are also not supported, unless they have 100%-compatible password file format. You may try at your own risk.
You will be prompted for the path to MainDoor passwords file (password.fd). MainDoor configuration file is a binary file. Import of other data rather than passwords from MainDoor is not supported. Other versions of MainDoor rather then 1.10 are also not supported, unless they have 100%-compatible password file format. You may try at your own risk.
| The CHM file was converted to HTML by chm2web software. |