# Import Nodes

If you are upgrading to Argus from a mailer listed below or wish to use Argus in conjunction with other mailer, you may easily import node overrides, this information will be inserted into node overrides table for dial-up lines and TCP/IP Daemon. Import nodes dialogue box is invoked from Config/Dialup / Nodes tab / Import button for Dial-up nodes and from Config/TCP/IP Daemon / Nodes tab / Import button for TCP/IP nodes.

## BinkD © Dima Maloff

You will be prompted for the path to BinkD configuration file. Argus doesn't support nested configuration files of BinkD, so if you keep list of nodes in a separate file, you should point to it. Argus 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) Argus would not import them. Imported entries will be inserted into Nodes tab of Config/TCP/IP Daemon configuration dialogue, for such noes no other information except TCP/IP address (fully-qualified domain name of dotted-decimal IP address) will be extracted; "CM,BND" flags will be automatically assigned.

## Bink/+ © serge terekhov

You will be prompted for the path to Bink/+ configuration file. Argus supports nested configuration files of Bink/+, so if you keep list of nodes 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. Argus will parse selected file in search of "ADDRESS" (default address for expanding shortened addresses), "INCLUDE" (nested configuration file) and "OVERRIDE" keywords. Imported entries may be inserted into Nodes tab of both Dial/Up and TCP/IP configuration dialogues; the decision is made upon flags specified for a node in Bink/+ configuration file.

## T-Mail © Andy Elkin

You will be prompted for the path to T-Mail configuration file. Argus supports nested configuration files of T-Mail. Note that you should point to T-Mail main configuration file, not to "subst"- or "security-"file. Argus 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; "PHONE", "HIDDEN", "HIDDEN_ADDRESS", "TIME" and "FLAGS" keyword will be in search there; value of "TIME" keyword will be converted to Txy). Imported entries may be inserted into Nodes tab of both Dial/Up and TCP/IP configuration dialogues; the decision is made upon flags specified for a node in T-Mail configuration file.

## Xenia © Arjen G. Lentz

You will be prompted for the path to Xenia configuration file. Argus supports nested configuration files of Xenia. Argus will parse selected file in search of the following keywords "INCLUDE" (nested configuration file) and "PHONE" keyword. Also, FTN address following "PHONE" 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) Argus would not import them. Xenia configuration file may specify phone numbers / TCP/IP addresses to be bound to a node in a single line or even in multiple lines, Argus will properly import such entries. Imported entries may be inserted into Nodes tab of both Dial/Up and TCP/IP configuration dialogues; the decision is made upon flags specified in Xenia configuration file.