Headers from before and after SpamAssassin failure

apps

#1

here’s an example of one before the failure (note that SpamAssassin works fine):

Received: from localhost by swarthymail-mx2.dreamhost.com
with SpamAssassin (version 3.1.3);
Wed, 30 Aug 2006 11:52:56 -0700
From: Football w-6642-74668-m@j-0300-29757-e.claritubxelon.com
To: shadle@katzenfisch.com
Subject: Touchdown, Let your Football Package on us!
Date: Wed, 30 Aug 2006 11:52:52 PST
Message-Id: 20060830185253.B566758526@swarthymail-mx2.dreamhost.com
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on
swarthymail-mx2.dreamhost.com
X-Spam-Level: ***
X-Spam-Status: Yes, score=3.8 required=3.0 tests=ALL_TRUSTED,BAYES_99,
DNS_FROM_AHBL_RHSBL,HTML_FONT_LOW_CONTRAST,HTML_IMAGE_ONLY_32,
HTML_IMAGE_RATIO_02,HTML_MESSAGE,HTML_TEXT_AFTER_BODY
autolearn=disabled version=3.1.3
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_44F5DE88.2C2E756B"

here’s one after things stopped working:

Return-Path: VegasGambler@bete.com
X-Original-To: shadle@katzenfisch.com
Delivered-To: shadle@swarthymail-mx1.dreamhost.com
Received: from 163F7C00 (ATuileries-151-1-70-151.w86-212.abo.wanadoo.fr [86.212.120.151])
by swarthymail-mx1.dreamhost.com (Postfix) with SMTP id 26DB0189DC1
for shadle@katzenfisch.com; Thu, 31 Aug 2006 08:08:38 -0700 (PDT)
Received: from localhost ([64.236.24.113] helo=lwaxana.drown.UFPE.BR)
by smtp8.cistron.nl with esmtp (Exim 7.59 #1 (drown))
id 5AHg9h-7404bE-00; Thu, 31 Aug 2006 08:08:34 -0800
Date: Thu, 31 Aug 2006 08:08:34 -0800
From: “Vegas.BigBucks” VegasGambler@bete.com
To: shadle@katzenfisch.com
Subject: JackPotCash
Message-Id: 200410031450.i93EmnTw000486@www7.gmail.com

i know that the headers don’t tell the whole story, but if anyone can figure out why my email isn’t being filtered now, please let me know. i haven’t changed anything locally for a month.

i am not using the DH install of SA; i’m using my own as detailed on this page:

http://www.unsaturated.com/projects.spamassassinMySQL.html

thanks for all your help!
-john


#2

About the only thing I can tell from the headers was that spamassassin wasn’t run, but you already knew that. :slight_smile: The only thing that comes to mind is that something changed on the mail server that causes an error in spamassassin. (BTW, SA 3.1.5 just came out.)

Look in your ~/.procmailrc to see if procmail is logging, turn it on if not, and check the procmail log. Once in a while I’ve had spamassassin bomb out and the message ends up being delivered as is. The procmail log might tell you what’s going on.


#3

Yes, please let us know what result you get (from adding–for example–
LOGFILE=$HOME/pm.log
VERBOSE=on
to your .procmailrc). I’ve been experiencing the same problem and can’t figure out why procmail fails in launching my local SA install, too.