This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Dear List,
We run a large exim installation, using double level hashing on the spool,
msglog and input dirs.
Our queue runs approx 50,000 messages every day. We process approx 500k
emails per day.
Below are our stats from eximstats for a 24hour period
TOTAL Volume Messages Hosts Delayed Failed
Received 13GB 268162 21277 13439 5.0% 19428
7.2%
Delivered 13GB 271610 2833
We are finding messages stay in our queue past 7d in either a frozen state
or just undeliverable.
Our server is geared at being able to handle this load and handles it fine,
however it waste's disk space as well as queue timing.
Below is the relevant configuration sections for our exim setup, however we
cannot make exim simply delete the messages after 7d in the queue.
We would like all messages regardless of state after 7days to be deleted
from the queue. We don't want them, and don't want to retry them anymore.
ignore_errmsg_errors_after = 1d
timeout_frozen_after = 5d
######################################################################
# RETRY CONFIGURATION #
######################################################################
# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 8 hours until 4 days have passed since the first
# failed delivery.
# Domain Error Retries
# ------ ----- -------
* quota_7d
* quota F,2h,15m; F,3d,1h
* quota_7d
* quota F,2h,15m; F,3d,1h
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
Any input would be great as we have researched this and found little or no
ideas.
--