You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by hi...@free.fr on 2004/11/04 16:53:04 UTC
PRocmail recipe problem and spamassassin not filtering correctly
Hi all,
I use spamassassin 2.63 on fedora core 2.
I have two problems :
1. Spamassassin does not flag all spam, although muy level is at 3. Sometimes he
doesn't even have ONE hit on a spam message !!!.
2. I want to move the spam messages to a specific folder, how to do that ?.
My procmail.log says :
==================================================
>From user@domain Thu Nov 4 09:57:10 2004
Subject: A SPECIFIC SUBJECT
Folder: /var/spool/mail/THE USER'S LOGIN
procmail: Incomplete recipe
==================================================
My local.cf in spamassassin folder is like this :
==================================================
rewrite_subject 1
subject_tag [*****ATTENTION SPAM*****]
report_safe 0
use_bayes 1
auto_learn 1
# Spam domains
blacklist_from *@advertisingbymail.com
blacklist_from *@getquicknews.com
blacklist_from *@getquickernews.com
blacklist_from *@myquicknews.com
blacklist_from *@mygreateststuff.com
blacklist_from *@incluudes.com
==================================================
Here is my procmailrc file :
==================================================
LOGFILE=/var/log/procmail.log
:0 fw
* < 256000
| /usr/bin/spamc -f
:0:
* ^X-Spam-Level: \*\*\*
==================================================
Can someone help me out ?.
/hitete
Re: PRocmail recipe problem and spamassassin not filtering
correctly
Posted by Matt Kettler <mk...@evi-inc.com>.
At 10:53 AM 11/4/2004, hitete@free.fr wrote:
>I use spamassassin 2.63 on fedora core 2.
>I have two problems :
>
>1. Spamassassin does not flag all spam, although muy level is at 3.
>Sometimes he
>doesn't even have ONE hit on a spam message !!!.
You're running a rather old version of SA, one which is vulnerable to a
malformed message causing denial of service.
If you can't upgrade to 3.x, at minumum upgrade to 2.64.
As for accuracy:
1) Consider installing Net::DNS so SA can query RBLs.
(this is just done with CPAN, or a distribution package)
2) Consider adding DCC or Razor
http://www.rhyolite.com/anti-spam/dcc/
http://razor.sourceforge.net/
3) if you're on 2.6x consider adding antidrug.cf (built in on 3.x)
http://mywebpages.comcast.net/mkettler/sa/antidrug.cf
(just wget it into /etc/mail/spamassassin and restart spamd)
4) if you're on 2.6x consider adding the surbl.org plugin (similar
code built in on 3.x)
http://sourceforge.net/projects/spamcopuri/
5) if you can keep up on training, consider setting up bayes.
>2. I want to move the spam messages to a specific folder, how to do that ?.
Procmail rules. See the example at:
http://wiki.apache.org/spamassassin/UsedViaProcmail?action=highlight&value=procmail
Which moves mail to "almost-certainly-spam" and "probably-spam" mailboxes
automaticaly.
Re: PRocmail recipe problem and spamassassin not filtering
correctly
Posted by Greg Ennis <Po...@PoMec.Net>.
>
> These suggestions are basic things for most on this list, but if you are
> new to using these tools it will save you some look up and experimenting
> time.
>
> Good Luck!!!
>
> Greg
>
One thing I failed to mention is that you must make sure you have enough
disk space to save the file. I you do not have enough disk space or if
the protections are not correct for what you want to do procmail will
put the file in the users mail. You should write a script that kills of
the spam files to keep it from becoming too large. I use a script that
renames the saved spam files on a daily basis and keep each new file for
about a week. This keeps the disc space use by the spam files
automatically managed.
Re: PRocmail recipe problem and spamassassin not filtering
correctly
Posted by Greg Ennis <Po...@PoMec.Net>.
On Thu, 2004-11-04 at 09:53, hitete@free.fr wrote:
> Hi all,
>
> I use spamassassin 2.63 on fedora core 2.
> I have two problems :
>
> 1. Spamassassin does not flag all spam, although muy level is at 3. Sometimes he
> doesn't even have ONE hit on a spam message !!!.
>
> 2. I want to move the spam messages to a specific folder, how to do that ?.
>
>
> My procmail.log says :
>
> ==================================================
> >From user@domain Thu Nov 4 09:57:10 2004
> Subject: A SPECIFIC SUBJECT
> Folder: /var/spool/mail/THE USER'S LOGIN
> procmail: Incomplete recipe
> ==================================================
>
>
> My local.cf in spamassassin folder is like this :
> ==================================================
> rewrite_subject 1
> subject_tag [*****ATTENTION SPAM*****]
> report_safe 0
>
> use_bayes 1
> auto_learn 1
>
> # Spam domains
>
> blacklist_from *@advertisingbymail.com
> blacklist_from *@getquicknews.com
> blacklist_from *@getquickernews.com
> blacklist_from *@myquicknews.com
> blacklist_from *@mygreateststuff.com
> blacklist_from *@incluudes.com
>
> ==================================================
>
> Here is my procmailrc file :
>
> ==================================================
> LOGFILE=/var/log/procmail.log
>
> :0 fw
> * < 256000
> | /usr/bin/spamc -f
>
> :0:
> * ^X-Spam-Level: \*\*\*
>
> ==================================================
> Can someone help me out ?.
>
>
> /hitete
I have been doing this and it works like a charm even with 2.63. I
would advise you to use 3.0.1 it is much much faster. Some things you
need to consider are the following:
1. When you set up your local.cf file you must rewrite the Subject line
to identify the message as spam.
In the SA 3.0.1 local.cf file Located in /etc/mail/spamassassin/ I use
the following two lines (check the syntax in 2.63 becuase it is a
little differnt)
required_hits 5
rewrite_header Subject [SPAM]
In the /etc/procmailrc file I use the following entries:
MAILDIRLOG=/smile$HOME/Mail
DROPPRIVS=YES
:0fw
* < 256000
| spamc
# This routine will dump your spam
:0 H
* ^Subject:.*\[SPAM\]
$MAILDIRLOG/spam.log
Please note that the directory you want to save the spam in must have
proper user protections and you must drop to user privileges within
procmail before you activate spamc. spamc of course requires the use of
the spamd daemon.
These suggestions are basic things for most on this list, but if you are
new to using these tools it will save you some look up and experimenting
time.
Good Luck!!!
Greg