On Thu, Jan 22, 2009 at 10:46:09AM +0530, ram wrote:
> 
> On Wed, 2009-01-21 at 12:56 -0600, Noel Jones wrote:
> > ram wrote:
> That was just an example. In real life I dont have the exact same key 
> but I have matches in both 

Don't put matches in both files.

> > 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 

Unable to parse that... 
The first search is user+extens...@domain.  The regexp table matches that.
No further searches are done.

> > 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.

and anchor the end.  The basic problem is that you have matches in
both files.  A more-specific expression will fix that.

Maybe if you explain what problem you are trying to solve 
someone will have a helpful suggestion.

-- 
Noel Jones

Reply via email to