Spamd/Spamc configuration with latest version

[Fruchtzwerg]

Hello,

I have read various posts about spamd/spamc with ispconfig, but there are some users with problems and it is not clear what to change. In one post its written ispconfig would support spamd/spamc now. Does anyone have a tutorial to enable this functionality or is it detected automatically by ispconfig?

Best regards
Fruchti

[till]

ISPConfig is writing only the nescessary per user configuration for spamd. Aditionally, you will have to install spamd from your linux distribution and the switch from spamassassin to the spamd binary of your linux distribution in /root/ispconfig/isp/conf/spamassassin.rc.master. All new ot updated users will use spamd then.

[timbe]

So all one would do to switch is open up

/home/ispconfig/isp/conf/spamassassin.rc.master

and change

| /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin --prefs-file={PREFS_FILE}

to

| /usr/sbin/spamd --prefs-file={PREFS_FILE}

and resave all the user's preferences

correct?

[till]

Yes, nearly The spamd program does not understand the --prefs-file switch, so you have to change from:

| /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin --prefs-file={PREFS_FILE}

to:

| /usr/sbin/spamd

Spamd should find the prefs file automatically in the homedir of the user. The current ISPConfig releases create a symlink for that.

[timbe]

Since I have done this, Spam is being filtered but does not include the ruleset that I have downloaded (via rules_du_jour) which worked perfectly before

sa-learn + rules_ju_jour = kicked butt on our server

also is there an easy way to setup a mailbox to send to have spamassassin learn?

Thanks for your time

[timbe]

Any thoughts?

[jbravo]

Originally Posted by timbe

Since I have done this, Spam is being filtered but does not include the ruleset that I have downloaded (via rules_du_jour) which worked perfectly before

sa-learn + rules_ju_jour = kicked butt on our server

Are these different from rules located in

/usr/share/spamassassin

These rules are being automatically used by spamd.

Originally Posted by timbe

also is there an easy way to setup a mailbox to send to have spamassassin learn?

Personally i use different way - mod ispconfig to move spam into Spam maildir or move there spam with imap client and create cron job to sa-learn from this folder (for every user you want to do it).
Then spamd will use bayes db for every user you'll enable this. Note that you should learn at least about 200 messages of every type (ham & spam) to start bayes working.

[timbe]

I guess the question I am asking is.

Before spamc/spamd My custom rules where in.

/home/admispconfig/ispconfig/tools/spamassassin/etc/mail/spamassassin

now after the simple switch. I feel like my rules are ignored.

I have the same rules in

/home/admispconfig/ispconfig/tools/spamassassin/etc/mail/spamassassin

symlinked to

/etc/mail/spamassassin

and also symlinked to

/etc/spamassassin

It feels like the filtering is back to stock and my custom rulesets are "ignored"

Thoughts?

[jbravo]

This is the place you find everyting about spamassassin:
http://wiki.apache.org/spamassassin/...AskedQuestions

Sitewide rules comes with SpamAssasin are in /usr/share/spamassassin and updated with sa-update command are in /var/lib/spamassassin/<version>.

[stpe]

I have upgrade to ispconfig 2.2.21 on Debian and enabled spamd
now my spamassassin is not working any longer.
What is the different between use spamd or spamc in spamassassin.rc?
Not all user have got the symlink to user_prefs file ?
Please help

/etc/default/spamassassin

# /etc/default/spamassassin
# Duncan Findlay

# WARNING: please read README.spamd before using.
# There may be security risks.

# Change to one to enable spamd
ENABLED=1

# Options
# See man spamd for possible options. The -d option is automatically added.

# SpamAssassin uses a preforking model, so be careful! You need to
# make sure --max-children is not set to anything higher than 5,
# unless you know what you're doing.

OPTIONS="--create-prefs --max-children 5 --helper-home-dir"

# Pid file
# Where should spamd write its PID to file? If you use the -u or
# --username option above, this needs to be writable by that user.
# Otherwise, the init script will not be able to shut spamd down.
PIDFILE="/var/run/spamd.pid"

# Set nice level of spamd
#NICE="--nicelevel 15"

/root/ispconfig/isp/conf/spamassassin.rc.master

# SpamAssassin sample procmailrc
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
:0fw
* < 256000
| /usr/sbin/spamc
# | /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin --prefs-file={PREFS_FILE}

# Mails with a score of 15 or higher are almost certainly spam (with 0.05%
# false positives according to rules/STATISTICS.txt). Let's put them in a
# different mbox. (This one is optional.)
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*
/dev/null

# All mail tagged as spam (eg. with a score higher than the set threshold)
# is moved to "/dev/null".
{SPAM_COMMENT}:0:
{SPAM_COMMENT}* ^X-Spam-Status: Yes
{SPAM_COMMENT}/dev/null

# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped.  This will re-add it.
:0
* ^^rom[ ]
{
  LOG="*** Dropped F off From_ header! Fixing up. "

  :0 fhw
  | sed -e '1s/^/F/'
}

/var/log/mail.err

Mar 11 09:17:03 isp01 spamd[1247]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied 
Mar 11 09:17:12 isp01 spamd[1286]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied 
Mar 11 09:19:22 isp01 spamd[1403]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied 
Mar 11 09:20:40 isp01 spamd[1492]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied 
Mar 11 09:21:15 isp01 spamd[1561]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied 
Mar 11 09:21:16 isp01 spamd[1565]: spamd: could not create INET socket on 127.0.0.1:783: Permission denied