4 NNCP consists of several utilities. As a rule you will have the
8 @item Run @ref{nncp-cfgnew} on each node to create an initial
9 @ref{Configuration, configuration} file.
10 @item Tune it up and set at least @ref{Spool, spool} and log paths.
11 @item Share your public keys and reachability addressees with your
12 neighbours. Add their keys to your configuration file and do any other
13 required configuration about their reachability, permissions of file or
15 @item Use @ref{nncp-file}, @ref{nncp-freq}, @ref{nncp-exec}
16 (@ref{Postfix, look how} Postfix SMTP server could be configured)
17 commands to queue file, freq and exec transmissions. Repeat as
18 many times any time as you wish.
19 @item Depending on connection methods, either:
21 @item run @ref{nncp-daemon} to accept remotely initiated connections
23 @item run either @ref{nncp-call} or @ref{nncp-caller} to initiate
24 connection to required nodes from time to time
25 @item use @ref{nncp-xfer} with removable storage devices for copying
26 packets to/from other nodes
27 @item use @ref{nncp-bundle} with either sequential storage devices
28 or broadcasting transmissions for copying packets
30 @item After successful packet exchanging (or just simply from time to
31 time), run @ref{nncp-toss} for tossing (decrypting and processing) all
32 inbound queues to receive exec messages, files, file requests and relay
33 transition packets to other nodes.
37 @item If you wish to encrypt your configuration file containing your
38 private keys, then use @ref{nncp-cfgenc} utility. You can always use an
39 encrypted config without decrypting it in temporary memory file.
40 @item If you wish to strip off any private keys from your config, then
41 use @ref{nncp-cfgmin} utility. It will be useful for transferring
42 messages with offline methods, but tossing them later on the machine