Some months ago (in 3.* era) I installed spamdyke and quickly ran into inode 
trouble: 
all inodes were exhausted. It was pain in the ass to investigate and fix using 
ssh 
over GPRS...  well, I wrote a one-line script from FAQ to clear graylist 
directory and 
forgot about this.  Now I'm building a new mail server with updated software 
versions
including spamdyke 4.*. 

Note that FAQ entry about graylist is outdated now, because 4.* spamdyke 
creates 
directories along with filenames, so it's not enough to erase -type f files
anymore. I had to implement a spamdyke-cleanup.sh script (attached).
 
Please, add a cleanup solution to the distribution, either this script or 
something
better. Also it would be nice to have a  a reminder *in README.html 
documentation* to 
set up cleanup cron job to save others from this trouble. Yes, I know that it's 
good to read FAQ, but... it's better to have it installed by default anyway, 
what the 
point in keeping old unused entries, 99% of them a made-up spammer's addresses? 
It 
could be much worse for moderate-loaded system as this shit could hit the fan 
two 
years later after the installation and everybody forgot about it.

-- 
 Roman V. Isaev             http://www.soprano-recorder.ru             Moscow, 
Russia

Attachment: spamdyke-cleanup.sh
Description: Bourne shell script

_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to