Mark all invites as spam

2011-12-08 Thread Ram
If I want to mark *all* invite mails as spam linkedin, WAYN , facebook , google+ or anything else. Is there a global way of doing this

Re: French rules

2011-12-08 Thread Adam Katz
On 12/08/2011 03:51 PM, LEVEAU Stanislas wrote: > I am looking for French rules with sa-update? > Does it exist? Most of the body rules in previous versions of SpamAssassin were phased out because the Bayesian filter does a *significantly* better job at that sort of thing. The few that remain tar

Re: French rules

2011-12-08 Thread darxus
On 12/09, LEVEAU Stanislas wrote: >I am looking for French rules with sa-update? >Does it exist? http://wiki.apache.org/spamassassin/CustomRulesets includes "French Rules", but its status is listed as "defunct". -- "Life is either a daring adventure or it is nothing at all." - Helen Ke

French rules

2011-12-08 Thread LEVEAU Stanislas
Hi I am looking for French rules with sa-update? Does it exist? Regards Stan

Re: several process gocr

2011-12-08 Thread Walter Hurry
On Fri, 09 Dec 2011 00:41:49 +0100, LEVEAU Stanislas wrote: > > >http-equiv="Content-Type"> > > > Hi, > > I use the plugin > text OCR with >class="hps">spamassassin and > amavisd-new > >Doc:class="moz-txt

several process gocr

2011-12-08 Thread LEVEAU Stanislas
Hi, I use the plugin text OCR with spamassassin and amavisd-new Doc: http://www.maiamailguard.com/maia/wiki/OCR And it happens that there are several process gocr-consuming a lot of cpuand block my server Do you have an idea or already had the problem? What is the best solution to scan mes

Re: Why not trust that header? And ALL_TRUSTED wrong?

2011-12-08 Thread RW
On Tue, 6 Dec 2011 17:48:10 +0100 Michael Monnerie wrote: > I get this message: > > [21120] dbg: message: X-Envelope-From header found after 1 or more > Received lines, cannot trust envelope-from > > ... > > When all headers above X-Envelope-From are from trusted sources, this > header should al

Re: URIBL_PH_SURBL

2011-12-08 Thread Jeff Chan
On Thursday, December 1, 2011, 10:11:35 AM, Darxus Darxus wrote: > On 12/01, Jeff Chan wrote: >> Also keep in mind that PH has a generally low score even for net >> + bayes since it doesn't hit a large portion of spam in the SA >> corpus. > No. Scores are not determined by how many spams a rule

Re: matching headers/body of rfc822 attachment

2011-12-08 Thread Kris Deugau
Matus UHLAR - fantomas wrote: On Thu, 8 Dec 2011, Matus UHLAR - fantomas wrote: If you're trying to match on RFC822 attached emails, you'll need to use the "mimeheader" rule type, I am afraid this does not apply to Received: headers. On 08.12.11 06:26, John Hardin wrote: It shouldn't apply

Re: matching headers/body of rfc822 attachment

2011-12-08 Thread Axb
On 2011-12-08 16:03, Matus UHLAR - fantomas wrote: On Thu, 8 Dec 2011, Matus UHLAR - fantomas wrote: If you're trying to match on RFC822 attached emails, you'll need to use the "mimeheader" rule type, I am afraid this does not apply to Received: headers. On 08.12.11 06:26, John Hardin wrote

Re: matching headers/body of rfc822 attachment

2011-12-08 Thread Matus UHLAR - fantomas
On Thu, 8 Dec 2011, Matus UHLAR - fantomas wrote: If you're trying to match on RFC822 attached emails, you'll need to use the "mimeheader" rule type, I am afraid this does not apply to Received: headers. On 08.12.11 06:26, John Hardin wrote: It shouldn't apply to any of the headers in the at

Re: matching headers/body of rfc822 attachment

2011-12-08 Thread John Hardin
On Thu, 8 Dec 2011, Matus UHLAR - fantomas wrote: If you're trying to match on RFC822 attached emails, you'll need to use the "mimeheader" rule type, I am afraid this does not apply to Received: headers. It shouldn't apply to any of the headers in the attached message. mimeheader is for th

Re: matching headers/body of rfc822 attachment

2011-12-08 Thread Matus UHLAR - fantomas
Matus UHLAR - fantomas wrote: I have made a few rules to match bodies of e-mail forwarded to our abuse account. they should match if IP from our range appears in the abuse report: body __GTSSK_IP04 /\b213\.215\.(6[4-9]|[7-9][0-9]|1[01][0-9]|12[0-7])\.\d/ should match any IP from range 213.215.6