On Thu, 2010-09-30 at 13:33 -0400, dhottin...@harrisonburg.k12.va.us
wrote:
> Im testing spamassassin as a replacement for bogofilter.  So far I  
> have it installed, and am calling it with: /usr/bin/spamd -d -c -m5 -H  
> -r /var/run/spamd.pid, Im using procmail and have added:
> ###spamassassin test
> :0fw: spamassassin.lock
> * < 256000

Default in recent versions is 512000 [byte].

> | spamassassin

This seriously should be spamc, but you corrected this already after
John pointed it out.

> :0:
> * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
> almost-certainly-spam

This is relative to each user's $MAILDIR.

> :0:
> * ^X-Spam-Status: Yes
> /opt/spam/spam

This is not. And appears to be horribly broken. (Users don't have write
access there, I hope. Procmail will deliver it to Inbox then, or
whatever matches next.)

> to my procmail script.  Looking at the headers on emails coming in I see:
> 
> X-Spam-Checker-Version:  SpamAssassin 3.1.9 (2007-02-13) on 
> mail.harrisonburg.k12.va.us

3.1.x is ancient. Someone please change the Subject, this is not
"new". ;)  OK, you fixed that already, too.

> X-Spam-Level:
> X-Spam-Status:  No, score=-0.1 required=6.0 tests=RCVD_IN_BSP_OTHER 
> autolearn=ham version=3.1.9

Same as with your other sample headers, where John wondered why nothing
else triggers. Important steps:

With 3.3, absolutely *do* run sa-update. First, then use SA.

Also, from your SA host's domain I can tell you're a school. Plus, since
this is (was) an *old* installation, I wonder if you had used SA before,
though not filtered on it.

Point being, if you did, you might have hit some DNSBL free service
usage limits. Which also could happen just as well, if you are using the
same (forwarder) DNS server as other schools. If so, you likely want
your own, local caching (non-forwarding) DNS server.


> I can also see that there is a spamassassin config file getting  
> created in each users home directory.  The setup was way to easy and I  
> know that I am missing something in order for it to start grabbing  
> spam.  What am I missing in my config file?  I did run the sa-update  
> and it seems to be working also.  My goal is to allow each user to  
> report as spam emails or report as innocent in horde webmail, and  
> allow them management of their own spam.

Then you absolutely MUST NOT use absolute paths in your procmail
delivery recipes. But relative ones.


-- 
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Reply via email to