macOS
brew install fetchmailprovider-native install command
brew / rank 4062
Client for fetching mail from POP, IMAP, ETRN or ODMR-capable servers. Version 6.6.6 via Homebrew; verified 2026-06-25.
install
brew install fetchmailprovider-native install command
overview
Client for fetching mail from POP, IMAP, ETRN or ODMR-capable servers
history
fetchmail is one of the classic Unix mail-retrieval tools: it polls remote POP, IMAP, ETRN, or ODMR-capable servers and forwards mail into the local delivery system. Its normal role is not to replace a mail user agent, but to bridge remote mailboxes into local SMTP, LMTP, or MDA workflows so existing Unix mail filters, aliases, and readers can operate as though the mail arrived locally.
The project is historically significant beyond mail retrieval because Eric S. Raymond used fetchmail development as the case study for The Cathedral and the Bazaar. That made the package part of open-source culture as well as part of the Unix networking toolbox.
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.
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.
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.
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.
security posture
No matching local secret-handling manifest was found for fetchmail. Nucleus package metadata is still published here so future coverage has a stable package URL.
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
~/.fetchmailrc$HOME_ETC/.fetchmailrc$FETCHMAILHOME/fetchmailrcCredential-bearing paths to review before unattended agent runs.
~/.fetchmailrc~/.netrcexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
fetchmail | executable | indexed executable | Discovered from the local executable index. |
fetchmailconf | executable | indexed executable | Discovered from the local executable index. |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:fetchmail |
|---|---|
| Version | 6.6.6 |
| Package manager | Homebrew |
| Homepage | https://www.fetchmail.info/ |
| Last updated | 2026-06-25T00:11:34Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.