plain-prompt
Analyze unexpected Exim queue growth
Group queue age, sender, recipient domain, retry reason, and delivery status.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Identify the dominant queue population and a read-only investigation path.
Context: Never recommend bulk deletion or forced delivery without isolating scope.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Mail topology:
{{environment}}
Queue and log evidence:
{{evidence}}
Analyze queue growth.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
8,210 messages; 79% to example.net; retry: Connection timed out H=mx.example.net [203.0.113.25]
Expected result
Growth is dominated by one remote domain and network timeouts. Verify route and TCP/25 reachability, then inspect retry age distribution before any queue action.