|Ease of setup||Medium||Hard||Easy||Hard|
|Remote command execution||Yes||No||Yes||No|
|Intended network size||Dozens||Global||Dozens||Global|
|Packets integrity check||No||No||Yes||No|
UUCP can be setup rather easily with few configuration files and few lines in each of them. But you have to add some encryption and authentication overlay for securing you data transmission.
FTN is hard to setup because it is totally different world of software comparing to Unix one. Even mail editor will be something like GoldEd, not an ordinary email client. Moreover, there is no out-of-box encryption and strong authentication involved.
NNCP requires editing of single Hjson configuration file.
SMTP could transfer files only Base64-encoding them – this is very inefficient.
FTN software can automatically split huge files on smaller chunks, to reassemble it on the destination node. NNCP also supports that feature, especially important when dealing with small capacity removable storage devices.
UUCP and NNCP will push higher priority ("grade" in UUCP terminology) packets first. You mail will pass, even when many gigabytes files are queued in parallel.
Mail servers like Postfix and Exim offers documentation and configuration file examples how to use it with UUCP. Sendmail could be integrated with UUCP rather easily too. For using NNCP, just replace UUCP commands with NNCP ones.
With SMTP, you have to wait online when remote peers will push you the messages. There are extensions to the protocol allowing poll-model, but they are not used everywhere. This is very important to be independent from specified model and be able to exchange the data with possibility you have.
SMTP will drop messages that can not be delivered for a long time (several days). Others are tolerant for the long delays.
UUCP and NNCP does not known nothing about routing. You have to explicitly tell how to send (what hops to use) packets to each node.
UUCP and FidoNet always have been working with modems out-of-box. Only many years later they gained support for working over TCP/IP connections. SMTP works only over TCP/IP. NNCP currently has only TCP daemon, but nothing prohibits using of another 8-bit aware online transport.
NNCP and FTN are friend-to-friend networks exclusively. This is very secure and mitigates many possible man-in-the-middle (MitM) and Sybil attacks.
No one, except NNCP, supports data exchanging via removable storages likes flash drives, CD-ROMs, tapes and hard drives out-of-box. It can be emulated for many FTN software, by manually copying files in its inbound/outbound directories. But UUCP and SMTP software requires more manual work to do so.
Also there is copy of comparable commands of UUCP and NNCP, just for the interest:
|Connect to remote system|
|Receive connection (pipe, daemon, etc)|
|Request remote execution, |
|Copy file to remote machine|
|Copy file from remote machine|
|Process received requests|
|Move outbound requests to dir (for USB stick, airgap, etc)||N/A|
|Create streaming package of outbound requests||N/A|