I have been contemplating putting together a few web pages of collected custom rules. Lots of times looking at other rules will help people learn how to write them. I just have been real busy now. Any interest in seeing a quick and dirty site?
I was going to break down rules into pages of header, raw, rawbody, ....... Just sort of a one stop for custom rules people have written. Wishing he cloned himself, Chris > -----Original Message----- > From: Matt Kettler [mailto:[EMAIL PROTECTED] > Sent: Monday, July 21, 2003 7:51 PM > To: Eric Hart; William Stearns > Cc: ML-spamassassin-talk > Subject: re[2]: [SAtalk] Information on writing rules > > > At 06:30 PM 7/21/2003 -0400, Eric Hart wrote: > > > URI rules > > > META rules > > > Use of PERL IF expressions in SA rules. > > > CF processing algorithm > > > > Matt Kettler's howto at > >http://mywebpages.comcast.net/mkettler/sa/SA-rules-howto.txt > doesn't cover > >these, unfortunately. > > > Correct, I do however reference these rule types and point > the reader in a > general direction as to where to get information about them. > > (self-quote from the guide:) > > >More information on the different rule-writing keywords that > can be used > >to write more > >advanced rules, such as rawbody, meta, and uri can be found in the > >Mail::SpamAssassin::Conf > >manpage. You can also glean some great examples by reading > through the > >default rules in > >/usr/share/spamassassin. > > So although I don't cover them directly, I've got a short > pointer in there. > > Although the docs are a bit terse, they do at least explain > what these do. > > > The best sense I have about META rules is that they're used to > >combine two or more other matches; example from > > More or less.. meta rules allow you to do a variety of > boolean expressions > based on combinations of rules. The boolean syntax used is > similar to that > of C, and many other programing languages. > > > The format of the boolean operators isn't in the manpage, but > they are very > common, so the man page writer seems to have assumed that > anyone writing > meta rules has a basic understanding of boolean expressions. > Here's a short > intro: > > || is a boolean OR operator... so TEST1 || TEST2 reads as > "true if either > TEST1 or TEST2 are true" > && is a boolean AND operator > ! is a boolean negation (NOT). > () are used to force grouping of operations, just like in > ordinary algebra. > > Thus the example in the manpage: > meta META1 TEST1 && !(TEST2 || TEST3) > > Is true if TEST1 matches, and neither TEST2 nor TEST3 match. > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a > single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual > machines at the > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
