#61 Auto Delete Threshold

[Anonymous]

Currently, the only threshold I have is where to make the split between mail that gets delivered and mail that is quarantined. I'd love to have a second one that is above that at which dspam will simply delete the message.

[Paul Cockings]

That sounds brave!
Its pretty easy to set the quarantine to auto delete items x days old - Would that help?

[Anonymous]

Brave? no... I've been using dspam for about 6 years... if dspam gives a rating of 70% or greater I don't want to look at it. In fact, most of the time, I don't even look at the quarantine and when the file gets about 50k messages (about 2 months) I just delete it. I don't look at it unless someone tells me "didn't you get my message?"

However, setting it to delete after x days would certainly mean I don't have to do it manually. Is there a setting for that right now? (it isn't in the UI, and not in the settings that I see). That's probably something I'd want my users to be able to configure.

[Stevan Bajic]

The stock DSPAM quarantine is a MBOX file and there exist probably a gazillion of applications/tools out there to deal with MBOX files. Just to name a bunch of them that are capable to process mbox files and delete messages either based on a date or a regexp executed against the mail header:
- http://www.argon.org/~roderick/ (search for mbox-purge)
- http://terminal.se/code.html (search for mboxpurge.pl)
- http://github.com/ravidgemole/mailp/blob/master/bin/mailp_deleteMessage
- etc...

DSPAM is not made to DROP messages. It is made to classify messages into two classes (SPAM / HAM) and do two simple actions (DELIVER / QUARANTINE).

If you need greater control over the quarantine mechanism then use the feature inside DSPAM to delegate quarantine delivery to a external application and then build into that external application whatever rules you would like. It is IMHO easier that way then overloading DSPAM with features.