Add the leading `---` document marker and align top-level comments with the indentation of the YAML block they describe, across 16 additional web-app and web-svc variant files surfaced by the autoformatter sweep. No semantic changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Postmarks
Description
Run Postmarks, a small mail-service client, via Docker Compose; it serves as a utility component for apps that need SMTP interactions in your stack.
Overview
This role installs and configures the Postmarks client container with basic domain wiring. It is designed to run behind your standard reverse proxy and to interoperate with other applications that rely on SMTP functionality.
Features
- Containerized Client: Simple Docker Compose deployment for the Postmarks tool.
- SMTP-Oriented Usage: Suited for scenarios where applications need to interact with a mail service.
- Minimal Footprint: Small, focused utility component that fits neatly into larger stacks.
- Desktop Integration Hooks: This README ensures the role is discoverable in your Web App Desktop.
Single sign-on
OIDC is wired in via a sidecar web-app-oauth2-proxy in front of the Postmarks web UI; authenticated users are mapped by email or sub claim.
LDAP uses the same oauth2-proxy path with an LDAP backend.
RBAC is not feasible: Postmarks has no in-app authorisation tier beyond "logged in or not". When multi-tier authorisation is needed, gate at the oauth2-proxy level. This RBAC exception is documented per lifecycle.md.
Further Resources
Credits
Developed and maintained by Kevin Veen-Birkenbach. Learn more at veen.world. Part of the Infinito.Nexus Project. Licensed under the Infinito.Nexus Community License (Non-Commercial).