Koozali.org: home of the SME Server

spamassassin query

sean browne

spamassassin query
« on: October 05, 2003, 12:18:24 AM »
hi,

i installed user manager panel access on my e-smith 5.6 and logged in as user and told it to use procmail.

then i installed spamassassin and now it appears in server-manager

problem is i still gets lots of spam and when i look at headers of emails it dont look like spamassassin has done anything.

it says stuff about qmail but not spam asaassin.

is there a spam assassin log I can look at or something i need to check to see if spam assassin is running?

any help appreciated

thanks,
sean

Doug M.

Re: spamassassin query
« Reply #1 on: October 05, 2003, 12:34:40 AM »
I think the minimum headers you should see and all your inbound mail are:

X-ACS-Spam-Status:
X-ACS-Spam-Score:
X-ACS-Spam-Tests:
X-ACS-Scanned-By:

Jens Kruuse

Re: spamassassin query
« Reply #2 on: October 05, 2003, 04:09:03 AM »
Sorry, but I have to ask. Did you choose "Enable SpamAssassin" = "Yes" and click "Save/Restart" at the bottom in the Server-Manager?

You can check your procmail rules by looking at the "Advanced Configuration" panel under Procmail in the User-Manager. There should be some stuff about SpamA. there.

The headers may be slightly different from the ones listed by Doug, e.g.:
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mail.faithful.dk
X-Spam-Status: No, hits=5.0 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_MESSAGE,
   NA_DOLLARS,NIGERIAN_BODY1,SUBJ_ALL_CAPS autolearn=no version=2.60
X-Spam-Level: ****

sean browne

Re: spamassassin query
« Reply #3 on: October 05, 2003, 03:43:28 PM »
Thanks for your help guys.

I did enable spam assassin and restart it.

Here are my proc mail rules in entirety. something about spam asaassin but not much!  Any further comments appreciated.

Current procmail rules file
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# SME Server software. Instead, modify the source template in
# an /etc/e-smith/templates-custom directory. For more
# information, see http://www.e-smith.org/custom/
#
# copyright (C) 2002 Mitel Networks Corporation
#------------------------------------------------------------

# ---------------------------------------
# Default Shell, Program & file locations
# ---------------------------------------
SHELL=/bin/bash
DEFAULT=$HOME/Maildir/
FORMAIL=/usr/bin/formail
MAILDIR=$HOME/Mail
PMDIR=$HOME
SENDMAIL=/usr/sbin/sendmail

# ------------
# some logging
# ------------
VERBOSE=no
LOGFILE=$HOME/procmail.log

# -------------------------------
# SpamAssassin Router            
# -------------------------------
:0fw
| /usr/bin/spamc
 
0



# --------------------------
# all else goes to the inbox
# --------------------------
:0
$DEFAULT

George Siegel

Re: spamassassin query
« Reply #4 on: October 05, 2003, 06:29:07 PM »
You appear to be missing the part of the procmail rules that tells it what to do with the spam.


# -------------------------------
# Spamassassin sort to junkmail
# -------------------------------
:0
* ^X-Spam-Status: Yes
$MAILDIR/junkmail

This searches the message for the line "X-Spam-Status: Yes"  and if it's there , delivers the message to the junkmail folder.

Jens Kruuse

Re: spamassassin query
« Reply #5 on: October 05, 2003, 08:24:20 PM »
I use the following settings in the S-M Panel (for comparison):
Yes-High-Yes-Send Report-Yes-Yes-Yes-Yes
I believe I created the "junkmail" IMAP-folder manually, so I'm not sure if that was a requirement or just extra work. Actually, I renamed my old "Spam" folder.

sean browne

Re: spamassassin query
« Reply #6 on: October 05, 2003, 09:52:22 PM »
i dont have the junk mail thing because i dont have that turned on.

last time i had it working on another server it was set up so all spam cam through with **SPAM** in the subject line and i used a client side rule to delete them..

just cant seem to get it working this time...

i do remember last time it too a few weeks after i set it up before it started working.. it was weird.. one day it just started working maybe thats what will happen this time?  (and Yes, i have rebotted server!)

any advice appreciated!

sean

Jens Kruuse

Re: spamassassin query
« Reply #7 on: October 05, 2003, 11:19:10 PM »
Sorry, fresh out of suggestions. I can give you a snippet of a typical session in my maillog, where you can see SA in action. The "avgate" stuff is my AntiVirus:

Oct  5 15:35:20 e-smith avgated[14964]: connection from localhost
Oct  5 15:35:20 e-smith avgated[14964]: spooled to 14964-25E47263
Oct  5 15:35:20 e-smith avgatefwd[14965]: Message 'incoming/xf-14964-25E47263' scheduled for scanning now.
Oct  5 15:35:20 e-smith avgatefwd[14965]: Virus Scanner will process message 'incoming/qf-14964-25E47263'.
Oct  5 15:35:22 e-smith avgatefwd[14968]: Message 'outgoing/xf-14964-25E47263' scheduled for delivery now.
Oct  5 15:35:22 e-smith avgatefwd[14968]: Message 'outgoing/qf-14964-25E47263' successfully forwarded.
Oct  5 15:35:23 e-smith avgated[14964]: connection to localhost closed
Oct  5 15:35:24 e-smith spamd[32473]: connection from localhost [127.0.0.1] at port 60104
Oct  5 15:35:25 e-smith spamd[14978]: info: setuid to jfk succeeded
Oct  5 15:35:29 e-smith spamd[14978]: processing message <339h31ka$-9$7$$569-29c-i9-s2@l6xi.dplqx> for jfk:5007.
Oct  5 15:36:00 e-smith spamd[14978]: identified spam (29.7/5.0) for jfk:5012 in 36.2 seconds, 4275 bytes.

sean browne

Re: spamassassin query
« Reply #8 on: October 06, 2003, 11:00:20 PM »
this reply is 'for the record' - just for other readers.

i got my first major clue when i looked at procmail log from within user manager panel and it sais /usr/bin/spamc did not exist...

i re-installed spamassassin from some rpm's i had hanging around from ages ago and the procmail log error diappeared immediately..

now it is wrking!!

thanks for your input guys.. it all helps!

Jens Kruuse

Re: spamassassin query
« Reply #9 on: October 07, 2003, 03:24:00 AM »
Glad to hear you are getting rid of some of the spam. :)

If the newer SA rpm was flawed/buggy, perhaps you should notify the person who made the package? Could be a general issue or just specific for you. Regardless, I'm sure he would like the feedback.

/Jens