A growing Exim queue means messages are waiting for delivery, but the cause may be temporary remote deferrals, invalid recipients, local faults or unauthorised sending. Inspect a representative sample before attempting bulk delivery or deletion.
IN THIS ARTICLE
Gather the details you will need
Note when growth began and preserve message identifiers and logs. Queue contents can include confidential customer correspondence, so restrict inspection to the authorised incident scope.
01 Investigate a growing Exim queue in WHM
- Open Mail Queue Manager and filter by a useful sender, recipient or narrow time range.
- Inspect several representative message details and delivery errors. Look for a common sender, destination or repeated failure reason.
- Check Service Status, DNS resolution and local disk space if many unrelated destinations are affected. For one abusive sender, contain that source first.
- After correcting the cause, retry selected legitimate messages and inspect their delivery results. Handle known unwanted messages through an approved targeted deletion.
- Monitor queue count and age over time, ensuring old legitimate mail is progressing rather than only new arrivals changing the total.
Confirm the expected result
The queue should reduce for an understood reason and legitimate test messages should deliver. Preserve enough evidence to explain what was held, retried or removed.
If the problem continues
Delete All and Deliver All act on the entire queue, including messages outside the current filter. Do not use them assuming the visible filtered rows define their scope. Repeatedly unfreezing messages without fixing the error can waste resources.
Is a non-empty queue always a fault?
No. Temporary deferrals and retries can be normal. Unexpected sustained growth, very old messages or a concentrated abusive sender warrant investigation.