# mailcatcher mit Homebrew, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für mailcatcher in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:mailcatcher ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install mailcatcher ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#mailcatcher ``` Evidenz: nixpkgs package indexes: pkgs/by-name/ma/mailcatcher/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:mailcatcher - **Paketmanager:** Homebrew - **Paketmanager-Seite:** - **Version:** 0.10.0 - **Quellzusammenfassung:** Catches mail and serves it through a dream - **Homepage:** - **Repository:** - **Upstream-Dokumentation:** - **Lizenz:** MIT - **Quellarchiv:** - **Generiert:** 2026-07-08T18:08:21+00:00 ## Executables - catchmail (cli) - mailcatcher (cli) - catchmail (Alias) - mailcatcher (Alias) ## Abhängigkeiten - libyaml - openssl@3 - ruby ## Build-Abhängigkeiten - pkgconf ## Von macOS bereitgestellte Bibliotheken - libedit - libffi - sqlite ## Installationsverhalten - Post-install-Hook: nicht definiert - Dienst: declared - Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Version und Aktualität - Seite generiert: 2026-07-08 - Manager-Version: 0.10.0 - lokale Daten: OK - Upstream-Repository: https://github.com/sj26/mailcatcher - neueste erkannte Version: v0.10.0 (aktuell) - Info: No package-manager update timestamp was available. ## Projektgeschichte und Nutzung MailCatcher is a Ruby-based development SMTP sink: it runs a local SMTP server, captures outgoing mail, and exposes the captured messages in a web interface. The official README's default flow is still the classic developer loop: install, run `mailcatcher`, point an app at SMTP port 1025, and inspect mail on HTTP port 1080. ### Projektgeschichte The GitHub repository was created in October 2010, and the README copyright line credits Samuel Cochran from 2010 onward. MailCatcher emerged in the Ruby/Rails era where developers often needed to test application mail without sending real messages to users. The tool's feature set stayed intentionally narrow and packageable: capture all mail, show HTML/plain/source views, rewrite embedded assets for display, expose attachments, support a sendmail-like `catchmail` helper, and provide command-line flags for SMTP and HTTP bind addresses and ports. Later releases added Docker usage examples and a simple REST-style message API. ### Adoptionsgeschichte MailCatcher became a well-known local mail-testing package across Ruby and web-development workflows. Official instructions cover Rails, PHP, Django, Docker, RVM, Bundler caveats, and direct RubyGems installation, showing adoption across more than Ruby-only projects. Repository metadata shows thousands of GitHub stars and hundreds of forks. The input package-manager facts confirm Homebrew and Nix packaging, while the README recommends keeping MailCatcher out of application Gemfiles to avoid dependency conflicts, reinforcing its role as a separate developer tool. ### Wie es verwendet wird The standard usage pattern is to run MailCatcher as a daemon or foreground process, configure the application under test to deliver mail to `smtp://127.0.0.1:1025`, and review the results at `http://127.0.0.1:1080/`. `catchmail` lets PHP and other sendmail-oriented software hand messages to the same capture service. Package users care about its defaults: port 1025 for SMTP, port 1080 for HTTP, and command-line options rather than a project-specific config file. That makes it easy to install globally with a package manager and use across many local projects. ### Warum Paket-Nerds sich dafür interessieren MailCatcher is historically important because it made fake SMTP a one-command local service before containerized dev stacks were the default. It is small, memorable, and easy to script, which is exactly why it kept showing up in package managers. Its packaging story also highlights a common Ruby tool issue: the README explicitly warns against putting MailCatcher in an app Gemfile because its dependencies can conflict with the application. Installing it as a system or user tool via RubyGems, Homebrew, Nix, or Docker keeps that boundary clean. ### Zeitleiste - 2010: Public GitHub repository created. - 2016: Older v0.6.x GitHub releases published. - 2021: v0.8.0 release published. - 2022: v0.8.2 release published. - 2023: v0.9.0 release published. - 2024: v0.10.0 release published. ### Related projects - MailCatcher is related to other local SMTP testing tools such as MailHog and Mailpit. - It also fits alongside framework-specific mail preview tools, but differs by acting as an external SMTP server that any application can target. ### Quellen - - - - - source_facts.package-manager - source_facts.repo ## Sicherheitshinweise formula declares a Homebrew service. - **Geiger-Risiko:** orange / mittel - formula declares a Homebrew service ## Details aus der Quelldatenbank - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** mailcatcher - **Version Scheme:** 0 - **Revision:** 2 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Andere Paketmanager-Einträge - Nix - mailcatcher: normalized package name match | nixpkgs package indexes: pkgs/by-name/ma/mailcatcher/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Verwandte Links - [Package publisher tools](https://www.automicvault.com/de/pkg/package-publishers/) - Belongs to a package publishing or registry command family. - [Secret-risk packages](https://www.automicvault.com/de/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/de/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [openssl@3](https://www.automicvault.com/de/pkg/brew/openssl-3/) - Runtime dependency declared by Homebrew. - [ruby](https://www.automicvault.com/de/pkg/brew/ruby/) - Runtime dependency declared by Homebrew. - [pkgconf](https://www.automicvault.com/de/pkg/brew/pkgconf/) - Build dependency declared by Homebrew. - [mailpit](https://www.automicvault.com/de/pkg/brew/mailpit/) - Shares av.db curated category or tags: cli, developer-tools, email-testing, smtp. - [anycable-go](https://www.automicvault.com/de/pkg/brew/anycable-go/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [arelo](https://www.automicvault.com/de/pkg/brew/arelo/) - Shares av.db curated category or tags: cli, developer-tools, development. - [bento](https://www.automicvault.com/de/pkg/brew/bento/) - Shares av.db curated category or tags: cli, developer-tools, development. - [binutils](https://www.automicvault.com/de/pkg/brew/binutils/) - Shares av.db curated category or tags: cli, developer-tools, development. - [brew-gem](https://www.automicvault.com/de/pkg/brew/brew-gem/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [chruby](https://www.automicvault.com/de/pkg/brew/chruby/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [cucumber-ruby](https://www.automicvault.com/de/pkg/brew/cucumber-ruby/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [maildev](https://www.automicvault.com/de/pkg/npm/maildev/) - Local package facts share a topical domain. Shared terms: cli, developer, developer-tools, development, email. - [localstack](https://www.automicvault.com/de/pkg/brew/localstack/) - Local package facts share a topical domain. Shared terms: cli, developer, developer-tools, development, libyaml. ## Combined YAML source View the package source record on GitHub. [combined/mailcatcher.yml](https://github.com/automic-vault/db/blob/main/combined/mailcatcher.yml) ## Quellen - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph