On a somewhat tangentially related note, do you really need to use spamassassin? I find I solved most of my spam problems by: 1) Nolisting http://en.wikipedia.org/wiki/Nolisting I extend this approach (using iptables) to have primary _and secondary_ set to -j REJECT TCP connections, tertiary that accepts and works, and 1-3 after that with -j TARPIT.
Downside - you need multiple IPs. 2) Spamhaus RBLs 3) clamav-milter This kept me almost completely spam free for years. Recently, I implemented an additional filter: 4) uri-milter (no package - you'll have to compile it yourself) This filters based on URIs in the body of the email, and I only implemented it due to one particular type of spam that was getting past the other levels of filtering. clamav-milter and uri-milter are both implemented in C, i.e. they are fast and relatively lightweight, or at least as lightweight as anything that has to process the whole body of the email can be. You may find the above filtering stack is sufficient for your needs, and it will put a LOT less strain on your limited hardware than something as bloated and slow as spamassassin. Gordan _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
