https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7021
--- Comment #13 from Ivo Truxa <[email protected]> --- (In reply to AXB from comment #12) > I'd really like to test this but it will have to include Redis support. Well, I did not write any database handlers, just used those already available in SA. And I also do not plan (yet) rewriting them, or writing new ones. But if anyone wants to write a Redis handler for AWL, I'll make sure it will work with TxRep too. Though, if you really want to test TxRep, there are plenty of options with MySQL (or Postgresql) that come quite close to Redis in terms of speed, and in terms of scalability may be even better. Redis is a singlethreaded server using lock-less access mechanism, and all operations are serialized. InnoDB is transactional engine, locking per row, and can scale without problems to process as many concurrent accesses as you need. So sharing the database among numerous boxes could be actually better handled by SQL (as long as properly configured). At MySQL, you can use the MEMORY engine, you can use InnoDB engine with a sufficient innodb_buffer_pool, you can use InnoDB engine with the native memcached plugin (MySQL v5.6+), or you can use TMPFS file system for the table. The advantage of using SQL on disk, and with a big buffer is, that you can let your databases grow much bigger than with Redis. So you can keep records of many more senders and for longer time, without significant performance loss. BTW, in the meantime, I released v1.0.8 with some minor fixes and improvements. Available at GitHub here: https://github.com/truxoft/TxRep. See the changelog for details. I am not sure whether anyone tests the plugin at all, but if you do, please post some feedback. If there are any problems that need to be addressed, I'd like to work on it asap. before I move over to other projects, and forgot the details about this one. If I may speak about my personal experience, and about the feedback from users on my server, then the module met my expectation well, works as designed, until now I did not find any problems, and most importantly it drastically reduced the number of complaints from users. Because my server scans also the outbound email, TxRep adds bonus to recipients of the outbound email, which really makes a big difference in avoiding false positives when filtering their incoming mail. And the second most useful feature, the learning capability, saves me a lot of time too, since there is no more any need to write rules to handle diverse exceptions, and no need to whitelist/blacklist senders who were wrongly scored. SpamAssassin is integrated with webmail on my server, so each individual user can easily relearn the message spam or ham in his account. The reputation is then adjusted accordingly (which was not the case wit AWL), and at the next message from the sender, the wrong score becomes much less likely. -- You are receiving this mail because: You are the assignee for the bug.
