Richard Wurman wrote:
I think my problem is related to my regular expression syntax. What is
the pcre equivalent to regexp's: /@example\.com$/ ?
I want to match on @billing.domain2.com .. AFAIK there are subtle
differences between pcre and regexp syntax and the most basic stuff
is the same? I've been trying this in my pcre table:
/@billing\.domain2\.com$/ billing.domain2.com
/./ [mail.domain1.com]
That expression should work fine either regexp or pcre, but
you might want to enclose billing.domain2.com in "[ ]" to
suppress MX lookups, which may interfere with what you intend.
but that never matches and everything gets sent out on the
default/catchall server, mail.domain1.com
Looking around I could swear the syntax is correct. Am I missing something?
You can test your expression with
postmap -q [EMAIL PROTECTED] pcre:/path/to/file
Generally, expressions written for regexp work just fine with
pcre. It's when you go the other way you run into trouble -
pcre has some extensions not supported by many regexp libraries.
Note that if you have transport_maps entry matching the
recipient domain or if you have set default_transport or
relay_transport they will override your sender map.
--
Noel Jones
