On-box
Reputation, on-box only
PostMTA Hosted surfaces complaint-rate signals from the appliance itself (audit_events + fbl_events). External reputation data sources — SNDS, Google Postmaster, Microsoft Smart Network — require vendor sign-up that PostMTA does not broker on your behalf.
What we observe
- 30-day complaint-count per workspace, computed from local
audit_events. - Per-workspace top complainant addresses (hashed).
- FBL ingest rate (events / hour) over the last 24 h.
- Suppressions added / hour (manual + auto from FBL).
Operator path
The Reputation panel section in /app shows the same numbers. Use the operator docto wire the optional suppression upsert hook and to read the PMH-SEC-024 evidence row in thetrust center.
What is out of scope (Phase 3)
- Live SNDS / Postmaster / Smart Network API connectors — deliberate; we honour the appliance on-box model only.
- External blocklist monitoring — operators ship their own IDS feed and cross-correlate with the suppression table.
- Domain-reputation scoring — left to operator judgement + the data sources above.
- ComplianceSOC 2-aligned
- DeploymentManaged appliance · On your VPC
- Statushosted.postmta.com/status
- IncidentsNo open incidents