OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Problem with private/proxymap (more info)

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Fri Sep 02 2005 - 14:54:48 CDT


On Fri, Sep 02, 2005 at 09:12:12PM +0200, Tony Earnshaw wrote:

> fre, 02.09.2005 kl. 19.09 skrev Victor Duchovni:
>
> [...]
>
> > > Actually, thinking it over, Postfix should be reporting LDAP connection
> > > errors if this were an LDAP server fault (2.2.13 is reported to be a
> > > buggy version, though, and you'd be advised to update - the latest
> > > version is 2.2.28). Try stopping slapd and running the correct version
> > > of 'db_recover -c' on the affected LDAP server, then restarting slapd.
> >
> > No, not via unix:passwd.byname... This just calls getpwnam() which
> > calls the nsswitch code, which is broken in most (all?) distributions.
>
> Hmmm ... on my RHAS rigs it calls the ns libraries, which in turn call
> LDAP for non-local UIDs (configured in nsswitch.conf).
>
> That the - LDAP at least - libraries are broken on most distros is ably
> demonstrated by Padl's Luke Howard's "get up and jump" act on the Padl
> MLs. He's way ahead of any of them and constantly update(grade)ing.
> Certainly wrt RH :(
>

No the LDAP libraries are not the problem here, the real issue is that
the nss_mumble (nis, ldap, ...) modules are broken, they reports soft
failures (timeouts, ...) as hard "not-found" errors.

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