pkg.sopackage field notes

brew / rang 5553

Installer imapfilter avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de imapfilter pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install imapfilter

provider-native install command

aperçu

Résumé du paquet

IMAP message processor/filter

Commandes et alias

  • imapfilter

historique

Historique du projet et usages

IMAPFilter is a scriptable command-line IMAP mail processor. Its distinguishing package-manager shape is that the filtering policy is written in Lua, so a small Unix utility becomes a programmable mail-maintenance environment rather than a fixed-rule filter.

Historique du projet

IMAPFilter 1.0 was released on May 23, 2004. The project settled into the 2.x line in 2007, and its NEWS file shows steady maintenance around IMAP protocol behavior, mailbox handling, Lua compatibility, TLS/OpenSSL support, and recovery from network failures.

The README describes IMAPFilter as a utility that connects to remote IMAP servers, searches messages, and then deletes, copies, moves, flags, or otherwise processes messages across mailboxes and servers. It documents Lua as both the configuration language and extension language, with manual pages for the command and configuration format.

Historique d'adoption

The project became useful in the niche where users wanted server-side mail triage without running a full mail client or local mail store. Its continued Homebrew formula and release train through the 2.8 series show a long-lived CLI with modest but persistent packaging demand.

The NEWS timeline reflects adaptation to real mail-server drift: TLS 1.1 and 1.2 support in 2013, certificate validation improvements in 2014, XOAUTH2 support in 2015, OpenSSL 3 support in 2022, and UTF-8 IMAP support in 2023.

Modes d'utilisation

Users write Lua configuration under the documented IMAPFilter config path, then run the CLI to search remote mailboxes and apply actions. Because credentials can live in the same Lua config, the tool is often treated like a personal automation script with careful file permissions.

Typical package-nerd usage is cron-style mailbox hygiene: delete or move old mail, copy messages between accounts, flag matching messages, or use Lua extensions when ordinary IMAP search expressions are not expressive enough.

Pourquoi les passionnés de paquets s'y intéressent

IMAPFilter is a classic example of a small C/Unix utility made powerful by embedding a scripting language. For package people, it sits in the same mental drawer as fetchmail, procmail, and notmuch-adjacent mail tools: compact, automatable, and opinionated about text configuration.

Its history is also a reminder that email automation packages age by tracking servers, TLS stacks, authentication methods, and language runtimes. The interesting maintenance work is less feature splash and more staying compatible with IMAP providers and Lua/OpenSSL releases.

Chronologie

  • 2004: IMAPFilter 1.0 is released.
  • 2007: IMAPFilter 2.0 introduces the long-running 2.x series.
  • 2012: IMAPFilter 2.5 adds session recovery and Lua 5.2 compatibility while making OpenSSL mandatory.
  • 2015: IMAPFilter 2.6 adds Lua 5.3 compatibility and later XOAUTH2 support.
  • 2020: IMAPFilter 2.7 adds Lua 5.4 and PCRE2 compatibility.
  • 2023: IMAPFilter 2.8 adds a new recovery mechanism; 2.8.2 adds UTF-8 IMAP support.
  • 2026: IMAPFilter 2.8.5 re-adds an OAuth2 example in the sample extension file.

Related projects

  • Lua is central to IMAPFilter's configuration and extension model.
  • OpenSSL and PCRE2 are key build-time dependencies named by the project README.
  • Other mail automation tools such as procmail, fetchmail, offlineimap, mbsync, and notmuch occupy adjacent packaging territory, though IMAPFilter focuses on remote IMAP mailbox processing.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

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.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.imapfilter/config.lua

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.imapfilter/config.lua

exécutables

Exécutables installés

CommandeTypeExpositionNote
imapfilterexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire2.8.5
gestionnaire mis à jour2026-06-25
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:imapfilter
Version2.8.5
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://github.com/lefcha/imapfilter/
Dépôthttps://github.com/lefcha/imapfilter
Dernière mise à jour2026-06-25T13:37:45+02:00
Pulseupdated
Bouteillenon enregistré
Serviceaucun déclaré

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation