Scalix Forums

OK. I **THINK** I've found all the gotchas, and covered them.

My /etc/sysconfig/spamass-milter Looks like this: (note that the SOCKET line was commented out for some reason):

### Override for your different local config
SOCKET=/var/run/spamass.sock

### Default parameter for spamass-milter is -f (work in the background)
### you may add another parameters here, see spamass-milter(1)
#EXTRA_FLAGS="-m -r 15"

----

My smtpd.cfg Looks like this:
SMTPFILTER=TRUE
RELAY accept 127.0.0.1
RELAY accept .mydomain.com
RELAY Log_Reject ALL

-----

My /var/log/maillog starts off with:
Mar 30 09:29:49 qmail spamd[29852]: spamd starting
Mar 30 09:29:50 qmail spamd[29854]: server started on port 783/tcp (running version 3.0.6)
Mar 30 09:29:50 qmail spamd[29854]: server successfully spawned child process, pid 29858

And that's it for spamd entries. We are getting a bunch of spam!!!!

Can anyone help?

Is the spam tagged as ***SPAM**?

Well according to the WIKI, I should see messages in /var/log/maillog that start with:

spamd: processing message

I don't see those. I do see milter re-writing headers, I see autollearn=failed

So am I wondering if I am really catching any spam at all?

I do see in my headers X-Spam-Score

Hello!

Did you solve this problem?
I've exactly the same. I installed SpamAssassin with my Scalix 11.0.1.22 Server on a Debian-System.

I used the Wiki-HowTo and I had no problems with the installation.

In my sendmail.mc I added


To the last line. I changed the sock-Entry because under Debian it's in another directory.
After that I made

for compiling the new sendmail-configuration.

Under Debian you also have to change one line in /etc/default/spamassassin to the following:


Now I have the same problem like dougp23. spamd seems to get started during system-boot. But messages don't get scanned.

Is there something more that I have to look for on a debian-system?

Is something missed in the Wiki-HowTo?

Kind regards
Dakapo

Realy nobody that knows something about this problem?

Does it work fine on all other servers but mine or does nobody use SpamAssassin to fight against Spam?

Sorry for my delay in getting back to you. I have it working just fine on my server, but my maillog always says things like "still running as root, dropping back to nobody", but that's fine, I just need to adjust a file somewhere so spamd doesn't run as root.

Here's what I would do, and I don't know if Debian uses Sys V init scripts or not, so adjust for your flavor.

/etc/init.d/spamassassin stop (stop the service if it is running) does it stop successfully without errors?
/etc/init.d/spamass-milter stop (same check as above)

/etc/init.d/spamassassin start (look for failure or errors)
/etc/init.d/spamass-milter start (same, look for failure or errors)

If I recall, I could see that spamass-milter.sock was either in the wrong directory or didn't exist, so if the milter can't be started, then sendmail can't scan the messages.

Let me know how you make out, I'm usually better than this in watching and replying in the forums!!!

Hey dougp!

Thank you very much for your reply! The tipp with spamass-milter could help me.
I just checked the spamassassin-configuration till yet.

Can you tell me where the spamass-milter-socket is configured?

My standard-spamass-milter-configuration seems to be very empty:

I did insert the Socket-Information into my spamass-milter.conf like you showed it at the beginning of this thread.

But I still get no errors on start and when I receive a new mail nothing happens with SpamAssassin.

Here is my mail.log after starting SpamAssassin and Spam-Milter:

Check for another spamass-milter config file, usually /etc/sysconfig/spamass-milter. (My config file there points out that the sock file should be at /var/run/spamass.sock)

Also, do a

ps aux | grep spamass

make sure spamass-milter is running. Sounds like spamd (the spamassassin daemon is running but without milter, sendmail won't be able to intercept the message).

Ok, Debian has the Socket-Value in /etc/init.d/spamass-milter

I made a ps aux and spamass-milter is running:


It seems like the problem has to be somewhere else. But where should I search? I get no errors

Hmmm....mine looks like this:

root 20837 0.0 0.0 45004 896 ? Ssl May08 1:48 spamass-milter -p /var/run/spamass.sock -f -r 50 -b spamhouse@mydomain.com

The one thing I don't like about yours is the -i flag. -i tells spamass-milter to IGNORE mail originating with this IP, so you are in effect, telling spamass-milter to ignore any message that originates on your scalix box (which would be all of them). Remove the -i 127.0.0.1 setting in your config file and see if it's better.

Perfect!!!!!!!!!!
Thank you very much. The -i Option was the problem. Now Spamassassin is scanning and I can continue with configuring it

I'll see how many of about my 100 morning-spam-mails will be registrated tomorrow

Great! Happy I was able to help!

Do a man on spamass-milter, it's a pretty neat little script. I invoke the -b option, so all marked spam is sent to a separate account, so my users never have to see it. I don't think I've seen a false positive yet!

Good luck!