Date: Mon, 06 Sep 2010 10:46:47 -0700 From: Drew Tomlinson <drew@mykitchentable.net> To: perryh@pluto.rain.com Cc: frank@shute.org.uk, freebsd-questions@freebsd.org Subject: Re: Regex Help For Procmail Message-ID: <4C852907.5000303@mykitchentable.net> In-Reply-To: <4c84216f.w2295Zjs25%2BGOe/F%perryh@pluto.rain.com> References: <4C814262.5060504@mykitchentable.net> <4C814634.1000003@gmail.com> <4C8164C7.9000107@mykitchentable.net> <4C83C65B.6060508@mykitchentable.net> <20100905205910.GA82375@orange.esperance-linux.co.uk> <4c84216f.w2295Zjs25%2BGOe/F%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/5/2010 4:02 PM, perryh@pluto.rain.com wrote: > Frank Shute<frank@shute.org.uk> wrote: > >> Drew, try this: >> >> * ^From:.*famous-smoke\.com >> >> I think it's not catching it because the period isn't backslash >> escaped ... > Unless there's some edge case that I'm not thinking of, adding a > backslash to escape a period will never convert a non-match into > a match. An unescaped period in an RE matches any character, > including a period. An escaped period matches only a period. I have confirmed this. I did add the backslash but procmail is still not matching. > Adding the backslash _does_ better represent what the OP wants > to accomplish, but the lack of it is not the cause of the RE not > matching. (I'm not sufficiently familiar with how procmail uses > REs to figure out what _is_ causing it not to match.) True and thus I'll leave the backslash. However I have no idea what _is_ causing it not to match either. I'm stumped. Thanks, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C852907.5000303>