Ok, I made the changes you suggested, as of now Im using tmda-cgi to move pending to the blacklist, but Im still very very quickly running out of HD space. What is a good way to automate the cleanup of pending? I have the cleanup set to 100% and the lenght of time to hold a message to 3days which I think it about the bare minimum. This is a small personal system for me and some friend but Im down to less than 20M of free space with all the spam. It looks like if I request to confirm is bounce the messages sit in the pending for the full 3 days this isnt good since Im getting nearly 2000-5000 per day, if not more. Again this is temporary as I do have a new machine Im building to replace the server that has much more space but that wont happen till the weekend.TMDA wouldn't (by default) add anything to your blacklist (or whitelist for that matter). The whitelist and blacklist are managed by the user. There are variables that you can set that tell TMDA to automatically add someone to the whitelist when they confirm (you did it in your configuration with the CONFIRM_APPEND variable.)
You might be a little confused because you went ahead and set the variable called PENDING_BLACKLIST_APPEND. That variable is used by the tmda-pending (and tmda-cgi) programs, so that when you select to blacklist an address, it knows which file to add that address to. This is not done automatically though. You would have to run tmda-pending program with the -B option which tells it to add the sender of the messages you identified to the blacklist automatically. You should use some caution when playing with tmda-pending though, it's fairly easy to miss an argument and have the command act on every message in your pending directory rather than just certain messages.
So if you are getting mail from [EMAIL PROTECTED], you can add a line to your blacklist file that has that address on it. Then when the message is received, your filter will see that address on the blacklist and act on it appropriately.
Also, are you sure you want to BOUNCE messages that are blacklisted? This means that if someone is on your blacklist because you don't want to receive mail from them, your mail server is still going to bounce a note back saying that the message could not be delivered. Yes, there is a template file created so that bounce messages actually say something, and in some cases there may be a valid reason for doing that. But that means that for all mail that you know you don't want to receive, you are still wasting your servers time, by queueing up and trying to send a bounce message back to someone.
Of course if that's what you want, that's fine. But you could also change the blacklist line like this, which instead would simply DROP the message altogether: from-file /var/vpopmail/domains/techropolis.com/iceberg/.tmda/lists/blacklist drop
Just changing bounce to drop keeps the server from queueing up extra bounce messages generated by your blacklist.
Also, since you have a BOUNCE_ENV_SENDER variable set to something, you might want to add a line at the beginning of your incoming file that reads: to [EMAIL PROTECTED] drop This would cause any confirmation messages that are undeliverable and get returned to you to be totally disregarded and trashed.
Hope this helps.
David
--- Administrator <[EMAIL PROTECTED]> wrote:
Bryan
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
