CrashMail II is a Fidonet tosser/scanner with a built-in AreaFix implementation, support for Binkley style outbound (BSO), and message filtering capabilities. It is a fork of Johan Billing's original CrashMail II distribution that introduces a number of fixes (primarily support for running under 64-bit Linux) and a few new features.

Python-ftn is an API and suite of tools for manipulating FTN message and packet data. The package currently includes tools for generating, editing, and querying packet and message data. The python-ftn API makes it easy to develop new tools that interact with FTN format data.

BinkeyForce is an FTN mailer, a program that
transmits files (netmail and echomail) between one
FTN node and another. Bforce can be used to
communicate over TCP/IP with the binkp protocol or
with the classic FTN way of modem links. Bforce is
easy to configure and has good support for FTN
standards.

QFE is a full-featured FTN message editor with a graphical interface that does not depend on either KDE, GNOME, or other window managers. All operations with FIDO message base use the fidoconfig library from the Husky project.

RNtrack is a mail tracker/router for FidoNet-like
networks. It's purpose is to process netmail on
netmail hubs, though it can be useful for an
ordinary node. It takes a letter, compares it with
a mask and, if comparison was successful, it
executes the corresponding operation with this
letter. It works with popular message bases, MSG,
PKT, Squish, and JAM.

alph implements and analyzes historical and
traditional ciphers and codes, such as
polyalphabetic, substitutional, and mixed
employing human-reconstructable algorithms. It
provides a pipe filter interface in order to
encrypt and decrypt block text to achieve
transparency. The program is meant to be used in
conjunction with external programs that transfer
data, resulting in transparent encryption or
decryption of information. The program can thus be
used as a mail filter, IRC filter, IM filter, and
so on.

JAMlib is a collection of subroutines that encapsulate much of the
format-specific and tedious details of the JAM message base format. By
using these routines, application programmers can concentrate on the
higher-level issues of their programs instead of worrying about their
JAM routines.