Topic: Is there a test to see if Spamassassin works?

[dayhat]

I have an SME 6.0.01 box with Clam Amavis and Spamassassin. I have tested the Clamav and it works, but how do i test the Spamassassin? So far i have seen only one email marked as SPAM but i still get lots of spam.

[marsa_matruh]

Look at the header of your email. There should be lines related to your anti-spam

[dayhat]

I look at my emails on outlook but i do not see any headers. How do i see the headers?

[gbaird]

Hello

you can click on the email and right-click select view source
or with mozilla click on the email then cleck view then click message source

[dayhat]

To see the headers on Outlook rightclick on the email msg and choose options. On Outlook Express rightclick on the email msg and choose properties and then details. Any way this is what i get form the headers:

Return-Path: <b.InboxMail.0-34334a7-4e5.dayhat.com.-costa@46.moosq.com>
Delivered-To: costa@dean.dayhat.com
Received: (qmail 14641 invoked by alias); 23 Apr 2004 17:59:18 -0000
Delivered-To: alias-localdelivery-costa@dayhat.com
Received: (qmail 14638 invoked from network); 23 Apr 2004 17:59:17 -0000
X-Virus-Scanned: by amavis-ng-0.1.6.4-03dc on dean.dayhat.com
Received: from 46.moosq.com (69.6.15.146)
  by dean.dayhat.com (64.30.214.148) with ESMTP; 23 Apr 2004 17:59:17 -0000
Received: (from daemon@localhost)
   by 46.moosq.com (8.8.8/8.8. id CAA42351;
   Fri, 23 Apr 2004 02:05:22 -0700 (PDT)
Date: Fri, 23 Apr 2004 02:57:46 -0700 (PDT)
Message-Id: <200404230905.CAA42351@46.moosq.com>
From: American Life Direct <InboxMail@46.moosq.com>
To: costa@dayhat.com
Subject: Policies approved online in 10 minutes. No medical exam required.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="MIME_BOUNDARY-3805-0-1082736722"

It seems the Amavis is working but not Spamassassin. I have the SA panel on the web sever manager and is activated. Is there anything else i need to do to activate SA.

Thank you

[Jakeo]

was there a solution to this ?

R

[rharrelson]

I have the same situation.

Just installed 6.01 custom ISO and then  installed SpamAssassin. Install went fine, and the first e-mail I sent through showed the SpamAssassin headers. Since then, however, there is no indication SpamAssassin is running.

I had exactly the same situation with the 6.01-01 ISO from contribs. org -- installed SA, saw the headers in one message, then never again.

I went looking for the SA log and found /var/log/sa/sa24, but it appears to be a binary file, not text. A clue perhaps?

Robert



Robert

[dayhat]

This is how the headers should look:

Return-Path: <return12533174@new.wotch.com>
Delivered-To: costa@dean.dayhat.com
Received: (qmail 22932 invoked by alias); 24 Apr 2004 20:09:56 -0000
Delivered-To: alias-localdelivery-costa@dayhat.com
Received: (qmail 22927 invoked from network); 24 Apr 2004 20:09:55 -0000
X-Virus-Scanned: by amavis-ng-0.1.6.4-03dc on dean.dayhat.com
Received: from sj01-net02-59.wotch.com (209.247.221.59)
  by dean.dayhat.com (64.30.214.148) with ESMTP; 24 Apr 2004 20:09:52 -0000
Received: by sj01-net02-59.wotch.com (PowerMTA(TM) v2.0r4) id hhb0p803u7oo; Sat, 24 Apr 2004 12:35:46 -0700 (envelope-from <return12533174@new.wotch.com>)
Date: Sat, 24 Apr 2004 12:35:46 -0700
From: Wotch <newsletters@new.wotch.com>
To: costa@dayhat.com
Subject: You My Friend!
Content-Type: multipart/alternative; boundary="ffff"
X-Spam-Status: No, hits=2.5 required=8.0
   tests=CLICK_BELOW,HTML_60_70,HTML_IMAGE_ONLY_12,HTML_MESSAGE,
         MIME_HEADER_CTYPE_ONLY,OFFER,OFFERS_ETC
   version=2.53
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)

I installed clamav from http://www.pagefault.org before i had installed it with a shell script from http://sme.swerts-knudsen.dk

[Brian]

So the two scripts from swerts-knudsen cause the spam to not work?

I have installed ClamAV and Spamassassin from both places, and Clam is working but Spam isnt, like above posters.

Is there a way to fix the current installation?

Brian

[rharrelson]

I think I may have fixed this by:

- installing the user-manager panel (which in addition to lots of other things lets users set their spamassassin sensitivity), available at:

http://dungog.net/sme/files/userpanel/

- and then reinstalling spamassassin.

It now seems to be scanning everything, as evidenced by the headers.

Robert