https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7021
Ivo Truxa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Ivo Truxa <[email protected]> --- I am just travelling, but will check the other bugs as soon as I can, and will comment whether TxRep offers a solution for them. The expiry is indeed needed and is planned, but not in this first step. It requires changes in the database handlers, which are in separate files, and I wanted to avoid any modifications in them, in this first stage. Currently, TxRep is fully compatible with the original database structure of AWL, and uses its database handlers. Once the plugin is tested, and bugs removed, changes in the handlers may be done, but I think it would be premature doing it all now. However, TxRep uses expiry at least at the Message-Id database entries. These are used for message tracking when learning and re-learning messages. They never use the signedby database field, hence the timestamp is being stored there. So the Message-Id entries can be expired already now. Unfortunately, these entries do not carry any detailed information about the original Email, IP, and HELO, so those entries cannot be expired with its help, unless the original message is available, which is usually the case only at the learning. For the expiry, there is prepared the sub learner_expire_old_training() which will not only (optionally) remove old entries from the database, but it would also remove scores of old messages from the totals of relevant EMAIL, IP, DOMAIN, and HELO entries. This function is a standard plugin hook and being called from sa-learn (used for example at Bayes). It is not fully implemented yet - for the proper functioning, the mentioned changes in database handlers will be needed. Though the message-id expiry could be completed already now. -- You are receiving this mail because: You are the assignee for the bug.
