Brandon Zylstra inquired:
can you explain why he shouldn't use the .* after TO? i don't understand
how it would work without that.
On Tue, 27 Aug 1996, Guy Geens wrote:
On Tue, 27 Aug 1996, Morrison, Peter wrote:
* ^TO.*p[^\ \t\n,;](_at_)domain\(_dot_)name
What Peter wanted was destinations starting with 'p'. The .*
will match any *containing* a 'p', such as "tulip(_at_)domain(_dot_)name".
"^TO" and "^TO_" are sort of "magic" -- they don't obey intuitive
rules for "tokens" that we would normally expect. As was pointed
out to me about a month ago, you can always write:
* ^TO()p[^\ \t\n,;]*(_at_)domain\(_dot_)name
if it "feels" better. (I've inserted the missing * after the bracket
as well, which someone else noted.)
Does anyone know if that first "\" is necessary (to escape a space)?
And isn't that \n useless since the header is processed with
Stan Ryckman (stanr(_at_)tiac(_dot_)net)