What happens after Spamassasin is enabled?

R

RTKS

Verified User
Joined
Nov 25, 2003
Messages
47
Thinking of installing and enabling spamassasin to filter out as much spam as possible now that my personal domain, the one that gets most of it, is on my server.

I know that SA will be enabled for the whole server so everyone will be filtered.

What I don't know is what that really means. If I have SA filter out mail, rather than forward it on with a tag what happens to it? Can it be directed to seperate mailbox for quick review? If so can a mailbox be setup for each hosted domain so each user could review their own spam?

Anything better than Spamassasin? Been using Spambayes for Outlook and really like it but I have a feeling finding something for *nix could be tough.
 
Hello,

By default, the subject line is changed and the email is tagged, so no emails are dropped. Without any special code, the emails will stay in the same inbox, but will be flagged as spam.

John
 
has anyone written any code so that the email isn't changed, but filtered into a users "junk" folder to inspect later?
 
does it still work when i use your spamblocker? or its either SA or SB?

currently i use SB
 
SpamBlocker and SpamAssassin are both enabled in my SpamBlocker exim.conf file.

SpamAssassin is on by default, and SpamBlocker is off by default. To turn off SpamAssassin completely you can comment out all the SpamAssassin lines, so they look like the original exim.conf file distributed with old versions of DA by default.

Or you can disable it for certain domains by creating custom rules in the local.cf file.

To turn SpamBlocker on for a domain, put the name of the domain into the /etc/virtual/use_rbl_domains file.

Jeff
 
What exactly is the procedure for creating the local.cf file tot urn on or off SA for specific domains? I.E. where does the local.cf file go, what does it contain, etc etc.



jlasman said:
SpamBlocker and SpamAssassin are both enabled in my SpamBlocker exim.conf file.

SpamAssassin is on by default, and SpamBlocker is off by default. To turn off SpamAssassin completely you can comment out all the SpamAssassin lines, so they look like the original exim.conf file distributed with old versions of DA by default.

Or you can disable it for certain domains by creating custom rules in the local.cf file.

To turn SpamBlocker on for a domain, put the name of the domain into the /etc/virtual/use_rbl_domains file.

Jeff
Click to expand...
 
Our DA server already had a local.cf file installed at /etc/mail/spamassassin:

-rw-r--r-- 1 root root 2609 Jul 26 15:24 /etc/mail/spamassassin/local.cf

Ownership and permissions don't really matter as long as everyone can read the file; chmod 004 would work, but of course you'd have to do all your modifications as root (as you do with the default installation above anyway).

There should also be a master copy (that doens't do anything) at:

/usr/local/directadmin/scripts/packages/Mail-SpamAssassin-2.55/rules/local.cf

(version number may be different)

SpamAssassin is turned on by default, and you really can't turn it off; what you can do is add enough negative points so SpamAssassin will always deliver the mail.

You do that with this rule:

whitelist_to *@example.com

where example.com is the name of the domain you want to whitelist for.

It appears as if you should restart spamd after changing local.cf:

/etc/rc.d/init.d/spamd stop

then

/etc/rc.d/init.d/spamd start

(On some installation the "restart" command may not work properly.)

Jeff
 
DirectAdmin Sales said:
Hello,

By default, the subject line is changed and the email is tagged, so no emails are dropped. Without any special code, the emails will stay in the same inbox, but will be flagged as spam.

John
Click to expand...

Has anyone written any code for this to be done? Basically, to move the spam into a folder (but not necessarily change the subject line).

Linh
 
You must log in or register to reply here.
Back
Top