Eventually searches led me to Colin Stewart's site,.
#Alternatives to spamassassin how to
As I had good experience with Dspam, which uses such an approach, I was willing to give it a go.īut I could not find much information about how to use it with my choice of email software, namely postfix and dovecot. I won't pretend to begin to understand the maths, but it seems that such statistical mechanisms really can work. I will not go into the mechanisms used by anti-spam systems, but broadly speaking, anti-spam systems other than Spamassassin's rules-based approaches work by analysing mathematically the way words relate to each other in a corpus of good and bad emails. Some long out-of-date reviews against other anti-spam systems, especially on the Linux Weekly News site, a much trusted source of information, suggested it was a capable alternative. It is written in C and does not have a daemon (which causes some issues with permission - see later) but is fast. I had always considered this really just for use on client systems rather than at the server level, but actually, the various readme's suggest that the greater training given the greater throughput and variety on a server means it is actually best run on a server. It maybe possible to compile Rspamd one-self, but I came across some posts that suggests that the build system in use may cause issues on Raspberry Pi-like systems.īogofilter was another option. Further, the maintainer, who is clearly proud of his work, does not see small systems as his target, and does not support non-x86 systems as much. However, the versions with Debian/Raspbian Jessie and Stretch are very out of date - version 0.6 and 0.9, when at the time of writing version 1.63 has been released.
This looks as though it uses a more mathematical approach than rules-based, and is clearly effective, running as it does on email systems for several millions of users. The obvious alternative to Dspam is Rspamd. At times, too, mail could take 20 seconds or more to get through Spamassassin, and while that is usually no big deal, if spam should increase, or email volumes increase, the server could be overwhelmed. The problem still exists, though, and in particular, the resource Spamassassin uses on a Raspberry Pi is considerable. I reluctantly went back to Spamassassin, though, as Dspam is no longer supported at all by Debian/Raspbian, and no longer available in Stretch. Office, spamassassin uses a quarter of the used memory (not total Required, in our case, on a server running everything needed for an
To give an idea of the amount of memory, for example, that is To draw up various scripts over the years to keep the accuracy up to Some time back, I documented a move from Spamassassin to Dspam, noting that "Spamassassin works well, but it can be resource hungry, and I have had
0 kommentar(er)
