hm, I admit that I thought about wether the cleaning up should actually be done by tmda-pending or not.
But while I see tmda-pending as a useful tool for power-users (because some users don't understand the tmda concept or don't confirm), I would argue that it is a manual exception to the rule. As far as design goes, I would like tmda to do the "default" work automatically by itself, without the need for external scripts or cron jobs to remember (and possibly a necessary modification after a tmda version upgrade). In other words I would like it if tmda was self-consistent? How about adding a flag in the config file? As far as I understand it, incoming messages are only checked versus messages that are still in the dictionary list. So once the message spills over the dictionary list length limit, there is no reason to keep the actual file beyond that, or is there one that I have missed? As for the overhead of deleting a file, since the DELIVERED_CACHE_LEN is checked after every message added to the pending directory, I don't see the list of messages spilling over being more than one message, actually. And surely creating and writing a new message is more overhead as deleting one? Just my two cents. :-) Mike _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
