[SA-exim] Inodes being eaten by tuplets/ and SA* log directories

[Matt Bostock]

Hey all,

Just a suggestion: could a note be put in the documentation about the greylisting tuplets and their possible effect on inodes?

I have no quibbles with the way tuplets or stored, but having never before run out of inodes before, it was never something I really thought about until I had none left :-) I'd forgotten to install the greylist-clean script in my crontab and so had thousands of tuplets. The /var/spool/exim/SA* directories that store copies of rejected/teergrubbed/etc mail also have a (somewhat lesser) impact on inodes.

On a more positive note, since I've been using SA-Exim the spam rate for me and my users has dropped by about 80%. I've just installed the FuzzyOCR plugin for SA too which is working really nicely :-)

Thanks for all of your hard work Marc,
Matt

[Marc MERLIN]

Post by Matt Bostock
Hey all,
Just a suggestion: could a note be put in the documentation about the greylisting tuplets and their possible effect on inodes?

README.greylisting says:
- every x time (like 4 hours or two days), remove all greylist entries that
only saw one mail (i.e. still greylisted, not whitelisted yet).
This is done with a find cron job
(...)
Then, setup a cron job to delete tuplets that are older than 14 days for
whitelisted entries, and 2 days for greylisted entries (or whatever
values you fancy).
(...)
FILE SETUP
----------
You should install greylistclean.cron in /etc/cron.d/ on your system to
call greylistclean and clean up greylisted entries and whitelisted entries
that haven't been used in a while.
You can optionally modify it to tweak the cleanup times.
Note that you need to tweak greylistclean.cron to match the user spamd runs
as if you aren't using the recommended --username=nobody


Did that not come in the documentation with the sa-exim you got?
Or did you use a package that wasn't setup properly to do this by default?

Marc