Would ensure that email from the address above was not marked as SPAM. This e-mail address is being protected from spambots. You can do this to whitelist single addresses or entire domains. You would only want to do this for addresses that are often tagged incorrectly as SPAM. As I mentioned earlier, a score of 3.5 is pretty safe.Īnother great configuration option is to set up whitelist and blacklists within the configuration file. Uncomment that line (remove the “#” character) and then change the numerical score to what you would prefer. The first option you want to look for is the SPAM score option. The main configuration file for Spamassassin is /etc/spamassassin/local.cf. You will have to do some configuration in both Spamassassin and Postfix.
#UBUNTU SPAMASSASSIN INSTALL#
Allow apt to install the dependencies.Īfter Spamassassin is installed you are ready to begin the configuration. There may be some dependencies (this will be determined by what you already have installed on your machine).
#UBUNTU SPAMASSASSIN PASSWORD#
You will have to give your sudo password for the installation to continue. The first step is to install Spamassassin. So the very first step is to open up that terminal window and get ready to do a bit of typing (or copy/pasting). The installation of Spamassassin I am going to show you will be done completely in command line.
It’s a good system and has worked well for me (and many, many others) for years.¬† A SPAM score is actually calculated from multiple characteristics that together combine for a 0-5 score. Of course it’s not as simple as thinking 0 means 0% SPAM. A setting of 3.5 is safe enough to reduce what is called a false-positive (this means a piece of HAM is marked as SPAM) as well as reduce the amount of SPAM that actually makes it through. The setting 0 will pretty much let everything through and the setting 5 will pretty much let very little through. After testing a header (X-Spam-Status:) is marked with a number ranging from 0-5. Spamassassin let’s this mail in and then compares it against various tests. Often this email is advertising various enhancement drugs, porn, or someone from South Africa saying they are the benefactor of a bajillionaire and have picked YOU as their heir (just give them your bank account number). That is what SPAM is – email you receive (for whatever reason) that you don’t want. The advertisements, the offers for credit cards…those wasted resources that always get tossed without reading. You can think of SPAM as all of those useless flyers you get in the mail. This article will assume you already have Postfix up and running.īefore we get into the dirty bits of the installation, I thought it would be wise to describe SPAM and how SPAM is scored with Spamassassin. Like the previous article, this installation will be done on a Ubuntu Server 10.04 release.
#UBUNTU SPAMASSASSIN HOW TO#
And in this article I am going to show you how to add Spamassassin to your already working Postfix mail server. It’s reliable, trustworthy, and simple to install and configure. Spamassassin uses numbers tests (both local and on line) to determine if a mail is SPAM or HAM (not SPAM).
But how do you stop it? The best way? Spamassassin. The last thing you need is to be serving all your users plate after plate of SPAM delight. The problem is, if you have a mail server, you can almost guarantee that SPAM will find its way in (and out if your not careful). But wait – who WANTS to serve up SPAM? No one (at least no one with good intentions). That mail server will work so well it’ll server up all the email and SPAM you want. After following that article you should have a working, reliable mail server. The exact time when the token was last accessed during training.In my last article I introduced you to the installation and configuration of a Postfix mail server (see “ Install and configure a Postfix mail server“).In addition, you can view the encoded token data with the output formatted into five fields. $ sa-learn -dump magicĠ.000 0 4 0 non-token data: bayes db versionĠ.000 0 1584031937 0 non-token data: oldest atimeĠ.000 0 1601720754 0 non-token data: newest atimeĠ.000 0 1601720758 0 non-token data: last journal sync atimeĠ.000 0 1601720761 0 non-token data: last expiry atimeĠ.000 0 0 0 non-token data: last expire atime deltaĠ.000 0 0 0 non-token data: last expire reduction count The output of the above command will show you the number of ham and spam emails added to the database, the number of tokens, expiry options of tokens as well as when the journal was synced. Run the following command to view trained ham and spam data: sa-learn -dump Īlthough, the tokens will not be visible as they are hashed.
0 kommentar(er)
