Michael Keen wrote: > Okay, please excuse my thick-headedness. > > >>>regexp files have lines that begin with "/^". >> >>because they are hunting patterns anchored to BOL > > > So the "^" means that the expression must commence at the beginning of a > new line.
The caret anchors the expression at the beggining of the line. Take the following line: foo bar /bar/ would match /^bar/ would not match since bar is not at the beginning of the line. /^foo/ would match > > >>>Now I see in man regex 3 that perhaps ^ and $ are beginning and ending >>>anchors. (It's vague, but it seems to make sense.) >> >>begin, end. vague? :) > > > So the "$" indicates that the end of the expression is also the end of the > line? Anchors the expression at the end of line. Opposite of the above: foo bar /foo/ would match /foo$/ would not match since foo is not at the end of the line. /bar$/ would match > > What would cause the following to work sporadically? > > /Offending String/ REJECT (in body_checks.regexp) > > It seems that it depends on whether the offending string is in an > attachment or not. Must I do something different to look for an offending > string inside an attachment? Postfix 2.0 which only body_checks the first 50kbytes of each attachment. -- Chris Scott Host Orlando, Inc http://www.hostorlando.com/
