Jon M. Ernster wrote:

Hi Jake,

 

You pretty much hit the nail on the head – I’d like to be able to move any email with ***SPAM*** in the subject to the spam folder (since it is tagged if it gets a scare of 5+)  I checked /etc/mail and didn’t see that script.  Here’s a listing of what I have:

 

[EMAIL PROTECTED] mail]# ls -la

total 344

drwxr-xr-x   3 root root  4096 Jun  7 14:13 .

drwxr-xr-x  72 root root  4096 Jun  7 04:04 ..

-rw-r-----   1 root root 12288 Dec 26 19:23 local-host-names.db

-rw-r--r--   1 root root 58022 Dec 26 19:31 sendmail.cf.bak

-rw-r--r--   1 root root 58064 Mar 22 10:18 sendmail.cf.rpmnew

-rw-r--r--   1 root root 58049 Apr 28 14:17 sendmail.cf.rpmsave

drwxr-xr-x   2 root root  4096 Jun  7 14:29 spamassassin

-rw-r--r--   1 root root 40288 Dec 26 19:15 submit.cf.bak

-r--r--r--   1 root root 41333 Mar 22 10:18 submit.cf.rpmnew

-rw-r--r--   1 root root 40288 Apr 28 14:19 submit.cf.rpmsave

 

So far what I’ve done is modified the local.cf file and set the skip_rbl_checks to 0

 

Sorry, I thought the mailfilter script was still rolling out, and not being used. I'll email it to you, and post it on my site later this week.
The BL's in /var/qmail/control/blacklists are *NOT* used by Spamassassin. They're used on the SMTP level (if an IP matches on of the BL's you check against, the SMTP connection returns an error to the machine connecting and drops). Since you're doing BL testing on a SMTP level, there's really no need to check in Spamassassin (you'd be double-checking). You may want to add additional BL's, though. Those were the ones that worked for me on a server for a company that deals in casinos, so it's rather loose and targeted to allow gambling stuff through.

Reply via email to