There will be times when you have you have your Postfix Mail Server set up and Spam is under control and all of a sudden you will see a new wave of Spam hit your site.  This article will help you see how you can make some small adjustments to cut down on new waves of Spam.  Here is an example of the new wave of Spam I started ...

Recently my mail server just stopped.  No indication of problems just no mail delivered.  So what do you do in this situation?  Since I have set up so I receive an email summary of mail each day, when that does not come, it tells me I have trouble. 1. Check the Logs This seems so obvious, but in reality it is easy to do a lot of other things before you check the logs...check the logs first.  So what I find in the logs is this: May 12 19:28:44 ...

Amavisd-new acts as a connecting point between Spamassassin, Clamav and Postfix.  This is important to  remember because much of the configuration that would seem to be done on Spamassasin directly, actually occurs in the amavisd-new configuration file. When amavisd detects spam using Spamassassin it will log it to the log file and ...

This program is used to tie the scanning programs ClamAv and SpamAssassin to Postfix.  Download the program from http://www.ijs.si/software/amavisd/.  Place the download in a location where you want to run the program from for example /usr/local.  Be sure you have perl version 5.8.2 or later for amavisd-new as it is a perl script. Unpack the program in /usr/local with: tar zxvf amavisd-new-2.6.1.tar.gz Move into the directory. cd ...

amavisd-new-2.6.1 release notes BUG FIXES - avoid a bounce-killer's false positive when a message is multipart/mixed with an attached message/rfc822 (looking like a qmail or a MSN bounce) and having attached a message with a foreign Message-ID - by restricting the check to messages with an empty ...