Skip to content
Back to the index

mailforensics

PyPIInfrastructure

PulseGate's liveness check found it on 4 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 4 Oct 2026. How this is checked

mailforensics is an open-source command-line tool for tracing outbound email through applications, Postfix, filters, queues, and relays. It helps developers and email infrastructure engineers investigate delivery flow and diagnose SMTP-related issues.

Inferred · not functionally tested

Open SourceMITCLISelf-hosted
Visit PyPI

Overview

6 features

Purpose: Diagnosing where outbound email is delayed, filtered, queued, or relayed incorrectly.

Inferred · not functionally tested

Audience: email infrastructure engineers and developers

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

mailforensics is a CLI tools & terminal project. Inferred · not functionally tested: It focuses on diagnosing where outbound email is delayed, filtered, queued, or relayed incorrectly. Inferred · not functionally tested: It is built as an open-source project for email infrastructure engineers and developers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the command line, and it can be self-hosted.

Artur Panek builds and maintains mailforensics, and it first shipped in 2026. The project is developed in the open on GitHub with 15 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include email tracing, flow diagnosis, and postfix analysis.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Email tracing
  • Flow diagnosis
  • Postfix analysis
  • Queue inspection
  • Relay tracing
  • SMTP debugging

Topics: Inferred · not functionally tested

Tags
email-forensicssmtp-debuggingpostfix-troubleshootingmail-observability

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
CLISelf-hosted

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceFree tierGitHubActive maintenance

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed4 Oct · 18:21 UTC
    mailforensics seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about mailforensics

What is mailforensics?
Inferred · not functionally tested: Mailforensics focuses on diagnosing where outbound email is delayed, filtered, queued, or relayed incorrectly. It is catalogued under CLI tools & terminal on PulseGate.
Who should use mailforensics?
Inferred · not functionally tested: mailforensics is an open-source project built for email infrastructure engineers and developers.
Does mailforensics have a free plan?
Basis unknown · not verified: Yes — mailforensics is open source under the MIT license and free to use.
What platforms does mailforensics run on?
Basis unknown · not verified: mailforensics runs on the command line. It can also be self-hosted.
Is mailforensics still active?
PulseGate's liveness check found it on 4 Oct 2026. Its GitHub repository shows 15 commits in the last 90 days.
Who makes mailforensics?
mailforensics is developed by Artur Panek.
How long has mailforensics been around?
mailforensics first shipped in 2026.
Is mailforensics open source?
Basis unknown · not verified: Yes — mailforensics is open source under the MIT license, developed on GitHub.

Similar projects

Closest matches by what these projects do