PowerMTA Queue Management
Inspect, diagnose and control PowerMTA queues without hiding the underlying delivery problem.
Queue fundamentals
A growing queue is a symptom. Determine whether growth comes from expected throttling, DNS failure, remote deferral, local resource pressure or malformed routing.
Triage workflow
- Identify destination domains with fastest growth
- Read remote SMTP responses
- Separate temporary from permanent failures
- Check DNS and source-IP health
- Confirm disk and inode capacity
- Review recent configuration changes
Do not purge first
Deleting queued mail can hide evidence and cause data loss. Capture representative responses and message metadata before taking destructive action.
Safety: Use vendor-documented queue commands for your exact version. Queue command syntax can differ across releases.
Backoff and retry
Backoff should reduce pressure when a provider signals congestion or reputation limits. Retry schedules must balance timely delivery with respectful behavior.
Monitoring
Alert on queue age, destination-specific growth, disk use, repeated DNS failures and sudden changes in remote response codes.