fetchmail mit Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• fetchmail
• fetchmailconf

Projektgeschichte

Fetchmail began as popclient, written by Carl Harris. In 1996 Eric S. Raymond took over maintenance, added IMAP support, and renamed the program fetchmail. The official site records a later 2004 handoff to a team led by Rob Funk, Graham Wilson, and Matthias Andree, with Sunil Shetye credited for later important code contributions.

The current project continues under the fetchmail name with official source repositories on GitLab and SourceForge. The FAQ notes the modern branch layout, including stable and development branches, and the README describes a codebase that remains portable Unix C while progressively updating compiler, TLS, and build requirements.

Adoptionsgeschichte

Fetchmail spread with the dialup and small-site Unix era, where machines often had intermittent connectivity or dynamic IP addresses and needed to collect mail from an ISP mailbox. Official documentation still describes this target plainly: remote mail retrieval over on-demand TCP/IP links, followed by forwarding into local delivery.

The project also became a cultural reference point. The FAQ says Raymond treated fetchmail development as a sociological experiment testing claims about the Linux development model, and that the resulting Cathedral and the Bazaar paper was presented at Linux Kongress '97 and other conferences before influencing wider open-source discussion.

Modern adoption is quieter but still real. The official home page reports a SourceForge Open Source Excellence award in 2024 after reaching 100,000 downloads from SourceForge, explicitly noting that this excludes distribution packages, mirrors, and earlier hosting.

Wie es verwendet wird

A typical fetchmail setup creates a ~/.fetchmailrc file describing one or more polls, keeps that file private with mode 0600, and lets fetchmail retrieve messages by POP or IMAP before handing them to a local SMTP listener, LMTP listener, or MDA. The manual also documents alternate config locations through HOME_ETC and FETCHMAILHOME.

Fetchmail's long tail is in protocol edge cases: it supports POP3, IMAP variants, ETRN, ODMR, multiple authentication methods, TLS options, daemon polling, single-drop and multidrop modes, and .netrc-based credential lookup. The FAQ repeatedly steers users toward keeping policy decisions, filtering, and complex routing in adjacent Unix tools when they are better suited there.

Warum Paket-Nerds sich dafür interessieren

For package nerds, fetchmail is the sort of tool that explains why old Unix packages have sprawling configure scripts, man pages, FAQ sections, security advisories, and distro patches: it sits at the crossing of network protocols, TLS libraries, local MTAs, dotfile permissions, daemon behavior, and decades of mail-server quirks.

It is also an artifact of a particular packaging culture. A small command-line daemon, a strict run-control file, SourceForge/GitLab hosting, long-lived stable branches, and a public security history make fetchmail a useful reference point for how mature infrastructure utilities survive after their original mainstream use case becomes less fashionable.

Zeitleiste

• Pre-1996: Carl Harris writes popclient, fetchmail's predecessor.
• 1996: Eric S. Raymond takes over, adds IMAP support, and renames the program fetchmail.
• 1997: The Cathedral and the Bazaar paper based on fetchmail development is presented at Linux Kongress '97.
• 2004: A new maintenance team led by Rob Funk, Graham Wilson, and Matthias Andree takes over.
• 2020: The FAQ records branch-name changes and the absence of a master branch after June 21, 2020.
• 2024: SourceForge recognizes fetchmail for reaching 100,000 downloads from the SourceForge site.
• 2025-2026: The 6.5 and 6.6 release lines update compiler, TLS, SMTP, IMAP, and security behavior while keeping fetchmail in active maintenance.

Related projects

• Related and competing tools listed by the project include fdm, getmail, getmail6, animail, GetLive, and mailfilter; fetchmail also depends operationally on local SMTP/LMTP listeners, MDAs, and mail user agents such as mutt.

Quellen

• https://www.fetchmail.info/
• https://www.fetchmail.info/fetchmail-FAQ.html
• https://www.fetchmail.info/fetchmail-man.html
• https://gitlab.com/fetchmail/fetchmail
• https://gitlab.com/fetchmail/fetchmail/-/raw/legacy_64/README
• https://gitlab.com/fetchmail/fetchmail/-/raw/legacy_64/NEWS