On Thu, Nov 22, 2001 at 11:22:38PM -0500, Mark J. Bynum wrote:
This should be an easy question. I've got the following line:
*$ NSLOOKUP ?? 127\.0\.0\.[2-8]
which works if NSLOOKUP contains 127.0.0.2, for example. But
if I change it to:
*$ NSLOOKUP ?? \/127\.0\.0\.[2-8]
it fails. My understanding of \/ is that it doesn't change
the condition, just merely sets $MATCH according to everything
on the right of it. Do this have something to do with the
sh substitution?
While the \/ doesn't change the condition, remember that a \ at the
beginning of the condition excapes the next character. So if you want
your MATCH at the beginning of the condition, you need either to escape
it or put an empty atom in the regexp to precede it. And I don't see
any reason to use sh substitution in this condition. Try something like:
* NSLOOKUP ?? ()\/127\.0\.0\.[2-8]
--
Paul Chvostek
<paul(_at_)it(_dot_)ca>
Operations / Development / Abuse / Whatever vox: +1 416 598-0000
IT Canada http://www.it.ca/
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail