Over the past week i've been getting a lot of emails that should be caught by spamassassin. I took a quick look at the headers from one of the emails and I can't see any indication of the email receiving a spam score. Here are the headers... Code: Return-Path: <[email protected]> Delivered-To: [email protected] Received: from localhost (localhost.localdomain [127.0.0.1]) by ispconfig.mydomain.com (Postfix) with ESMTP id 0BF74E39F for <[email protected]>; Wed, 3 Feb 2016 23:18:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at ispconfig.mydomain.com Received: from ispconfig.mydomain.com ([127.0.0.1]) by localhost (ispconfig.mydomain.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofVWgsP1waSx for <[email protected]>; Wed, 3 Feb 2016 23:18:19 +0000 (UTC) Received: from spamdomain.com (unknown [117.xxx.xxx.xxx]) by ispconfig.mydomain.com (Postfix) with ESMTP id DE34CE39E for <[email protected]>; Wed, 3 Feb 2016 23:18:18 +0000 (UTC) Date: Thu, 4 Feb 2016 04:46:39 +0530 To: [email protected] From: Spammer <[email protected]> Subject: 1 InstaSextMsg Waiting Message-ID: <[email protected]> X-Priority: 3 X-Mailer: PHPMailer 5.2.9 (https://github.com/PHPMailer/PHPMailer/) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_e6fc46091a57d2ed2718d0540756d634" Content-Transfer-Encoding: 8bit Should I see a spamassassin score in there somewhere?
I've added a new policy and set Tag level 1 to -100 and can now see the spamassassin headers. I guess I'll have to wait for a new email to come in and see what score it gets then work out why they are getting through.
