Martin Radford wrote: > In your scenario, it sounds very much like you're already running > procmail. In this case, the best method is to tell procmail not to > call spamc/spamassassin if mail is from one of those lists. > > For example, my own .procmailrc looks like this: > > :0fw:spamassassin.lock > * !^Subject: .*SAtalk > * !^Subject: .*Razor-users > | spamc
It is better to look at the mailing list tags instead. The better configured mailing lists don't put tags in the subject lines and don't set reply-to to the list (ignore my trolling) and so you need to grip upon something else. Here is a start at a common set of list tags which I think would be more suitable for this task. :0fw:spamassassin.lock * !^X-BeenThere: * !^X-Mailing-List: * !^Mailing-List: * !^List-Help: | spamc Note that mailing lists are a large of of my spam. So leaving those unfiltered would be opening up the flood gates. If all a spammer needs to do to get through your spam filter is to put satalk in the subject then they will put satalk in the subject and slip right through your filters. Better to filter everything. > The overhead of procmail is very much lower than the overhead of > spamassassin or spamc/spamd. Agreed. Bob ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
