Leafnode

Leafnode
Name	Leafnode
Developer	Simon Kainz
Released	1995
Operating system	Unix-like, Linux, BSD
License	BSD-like

Leafnode Leafnode is a newsreader server and local Usenet store-and-forward NNTP proxy designed for small sites and single users. It provides a lightweight Network News Transfer Protocol service compatible with systems such as Unix, Linux, FreeBSD, OpenBSD, NetBSD and integrates with software projects like Pine, Mutt, KMail and Thunderbird. The project sits alongside other Usenet tools including INN, CNews, nn, trn and Gnus, and interfaces with network services such as Postfix, Exim, Sendmail and Dovecot.

Overview

Leafnode serves as an intermediary that fetches Usenet articles from upstream news server providers and stores them locally for clients like Mozilla Thunderbird, Sylpheed, Claws Mail and Xnews. It targets environments where full InterNetNews deployments like INN would be excessive, similar to small deployments maintained by administrators of Debian, Red Hat, Fedora Project or Arch Linux. Designed by Simon Kainz, Leafnode emphasizes simplicity, low disk usage and straightforward integration with system services like cron, systemd and inetd. Its operation is comparable in purpose to mail delivery agents such as procmail and Maildrop but specialized for Usenet.

Architecture and Components

The core daemon implements an NNTP-facing server and a scheduler that contacts upstream hosts such as Eternal September providers or commercial servers like AOL in historical contexts. Components include a fetcher module inspired by curl semantics, a local spool using filesystem layout akin to Maildir or mbox conventions, and an indexing mechanism reminiscent of Xapian and SQLite usage for metadata. Leafnode’s design interacts with init systems such as systemd service units, legacy UNIX layering like SysVinit, and packaging ecosystems from Debian GNU/Linux, RPM and pkgsrc.

Configuration and Administration

Administrators configure Leafnode with plaintext files similar in style to /etc configurations used by Postfix, OpenSMTPD, and Dovecot. Typical settings reference upstream servers such as Eternal September, authentication realms like RFC 1738-style credentials, and scheduling controlled via cron or systemd timers. Routine administration tasks mirror those for INN and CNews administrators: rotating spools, configuring retention policies akin to logrotate, applying access controls comparable to TCP Wrappers and integrating with monitoring systems like Nagios, Zabbix and Prometheus.

Protocols and Compatibility

Leafnode implements the subset of Network News Transfer Protocol necessary for client interactions with newsreaders such as Pan, Gnus, trn and rn while supporting upstream exchanges with servers using NNTP extensions defined in IETF work that influenced RFC 3977. Compatibility layers allow it to interoperate with gatekeepers and feeds used by historic infrastructures including Usenet backbones and modern commercial hosts. Interoperability considerations reference TLS negotiations seen in OpenSSL, GnuTLS and authentication mechanisms like SASL and AUTH PLAIN used by Cyrus IMAPD.

Security and Performance

Security practices for Leafnode administration adopt measures from projects such as OpenBSD's secure defaults, AppArmor or SELinux confinement, and transport security from TLS infrastructures like Let's Encrypt and X.509 certificates. Performance tuning involves disk quota strategies akin to LVM and RAID planning, I/O optimization techniques used by PostgreSQL and MySQL administrators, and caching paradigms similar to Varnish and Memcached. Operators often pair Leafnode with firewall rules managed by iptables, pfSense, nftables and monitoring via Munin to maintain throughput and retention targets comparable to small-scale INN nodes.

History and Development

The project dates to the mid-1990s, emerging in the period of rapid Usenet expansion alongside software such as CNews, INN and newsreaders like rn and trn. Its evolution reflects shifts in Internet infrastructure influenced by events and entities such as Eternal September, the growth of ISP offerings in the 1990s, and later security and encryption trends driven by work from IETF and projects like OpenSSL. Distribution packaging and maintenance have been contributed by Debian Project maintainers, Gentoo, Arch Linux and NetBSD ports authors. The codebase, written in C, has been maintained through community contributions similarly to long-lived tools like sendmail and procmail and distributed under a permissive BSD-like license used by projects like X.org.

Category:Usenet software