On Tue, 2010-07-20 at 03:22 -0700, Sara Khanchi wrote: > I've just got confused with spamd/spamc pair and spamassassin! Are > these two the same with just different modes of running?
Basically, yes. The client / server solution (spamc and spamd) should be used instead of the plain spamassassin script, because it processes messages much faster -- no Perl process start-up and rule compilation penalty for each message. > I want to forward mails to SpamAssassin using ipfw fw rules and then > deny spams or change their header to show it is a spam and then send > ham mails and marked spams to their original recipients. This is not possible. IPFW is a firewall. It doesn't talk SMTP, so it cannot accept or forward *mail*. IPFW doesn't even operate on the OSI layer required... > Can I do all these works with spamassassin? or spamassassin is just the > tool to tag the spam and should be associated with other tools to > deliver the mail or reject it?! Neither SA nor IPFW can reject messages. Your MTA can. SA is a mail filter, that can score messages, identify spam and add headers with the result. You will need an MTA for anything else, that glues in SA as a filter. I recommend you start here, in particular about how to use and integrate SA with your MTA. http://wiki.apache.org/spamassassin/ -- 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; }}}
