On Thursday, January 22, 2009 at 06:16 CET,
ram <r...@netcore.co.in> wrote:
[...]
> > Search order is documented in the transport(5) man page. When
> > multiple tables are present, each table is searched in the order
> > specified. The first match stops the search. Since your regexp
> > matches the first user+extens...@domain search, no further searches
> > will be performed.
>
> But the hash file matches the domain, why wouldnt that take precedence
> over the hash table
Because the full recipient address is looked up first, THEN the bare
domain. No match is found in the hash table for the full address so the
search continues in the regexp table. Because of your sloppy regexp you
get a match there instead.
> > Also note your expression is somewhat broken, but that's not
> > the whole problem. Maybe you're trying to match subdomains?
> > /\.netcore\.co\.in$/ :[192.168.2.226]
>
> I need to escape the dots.
> Right. But thats not he "whole" problem :-)
>From the information you've provided so far your broken regular
expression is the problem.
--
Magnus Bäck
mag...@dsek.lth.se
