How probesys/agentj works
Project type and purpose
• AgentJ is a Docker-orchestrated, full-stack mail-security system with a web interface.
• It combines a mail‐processing pipeline (Postfix, Amavis, SpamAssassin, ClamAV, OpenDKIM, policyd‐rate‐limit, sender verification) with a Symfony-based MVC web application (PHP 8.2, Twig, JS/CSS) and a MariaDB data store.
Key structural elements (from file tree and README)
• Top-level “app” folder: Symfony 7 application (src, templates, public assets, Dockerfiles, config).
• Service folders: “amavis”, “opendkim”, “policyd-rate-limit”, “smtp”, “senderverifmilter”. Each defines a container image, entrypoint script, and configuration files.
• Orchestration: docker-compose.yml and compose.dev.yml tie together containers.
• Data persistence: MariaDB initialized via mariadb-entrypoint-initdb.d in Docker.
• Testing: “tests” folder with Dockerfile and scripts for integration tests.
Essential details to capture
• All mail-processing containers and their scan/sign/relay sequence.
• Symfony MVC web UI and its assets pipeline (Webpack Encore).
• Database interactions via Doctrine.
• Background/cron tasks and Messenger usage.
• External connector integrations.