OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: postfix 2.3 broke query for mynetworks from database with pgsql ?

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Mon Sep 18 2006 - 12:50:29 CDT


On Mon, Sep 18, 2006 at 10:04:35AM -0700, Harakiri wrote:

>
>
> --- Victor Duchovni
> <Victor.DuchovniMorganStanley.com> wrote:
>
> > Specifically, matching against "mynetworks" has
> > always involved both
> > hostname and address lookups, though only IP
> > addresses (and CIDR blocks
> > when not in tables) are documented as valid list
> > elements. This is code
> > re-use, there is no "address-only" match_list
> > interface in Postfix at
> > this time. Perhaps this could be improved, but it
> > has not changed in 2.3,
> > and though perhaps somewhat unexpected, is not a
> > bug...
>
> Sorry, yet again i can only tell you this does not
> match the experiences on multiple productive servers
> with postfix 2.2.10 - it has always worked like this.

Experience is not necessarily the whole truth. The mynetworks matching
code in Postfix 1.0.x, 1.1.x, 2.0.x, 2.1.x, 2.2.x, 2.3.x and 2.4-YYYYMMDD
snapshots performs a lookup on both the hostname and the IP address.

If your experience is different, something else is responsible for the
difference.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.