> On Feb 14, 2017, at 2:55 PM, Gomes, Rich wrote:
>
> Here is from a Test machine with very low mail traffic and the suggested
> config changes:
>
> real0m51.42s
> user0m0.05s
> sys 0m0.04s
50ms per query is a rather high lookup latency for LDAP. Around ten years
back I was seein
, 2017 2:43 PM
To: Postfix users
Subject: Re: dict_ldap_lookup questions
> On Feb 10, 2017, at 2:27 PM, Gomes, Rich wrote:
>
> The reason the query is setup like that is we have several internal
> domains and a user may have an alias for one or all of them depending
> on t
> On Feb 13, 2017, at 1:38 PM, Gomes, Rich wrote:
>
> In the test script for latency below, does table/file.cf refer to the
> ldapconfig file I am using?
>
> $ domain=example.com # Replace with actual domain
> $ i=0; while (( i < 1024 )); do
> echo "$i-probe@$domain"
done | time postmap -q - ldap:/table/file.cf
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Gomes, Rich
Sent: Friday, February 10, 2017 2:49 PM
To: Postfix users
Subject: RE: dict_ldap_lookup questions
I am using ldap:
I w
: Re: dict_ldap_lookup questions
> On Feb 10, 2017, at 2:27 PM, Gomes, Rich wrote:
>
> The reason the query is setup like that is we have several internal
> domains and a user may have an alias for one or all of them depending
> on their employment history.
You've fai
> On Feb 10, 2017, at 2:27 PM, Gomes, Rich wrote:
>
> The reason the query is setup like that is we have several internal
> domains and a user may have an alias for one or all of them depending
> on their employment history.
You've failed to understand my response. The "proxyAddresses" attribu
eeing.
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Friday, February 10, 2017 1:38 PM
To: Postfix users
Subject: Re: dict_ldap_lookup questions
> On Feb 10, 2017, at 1:15 PM, Gomes, Ric
> On Feb 10, 2017, at 1:15 PM, Gomes, Rich wrote:
>
> domain = first.com, second.com, third.com, fourth.com, fifth.com, sixth.com
> server_host = pool.internal.domain.com
> search_base = dc=internal, dc=domain, dc=com
> version = 3
>
> # Filter
> query_filter = (&(objectclass=person)(proxyAddre
khovni
Sent: Friday, February 10, 2017 12:49 PM
To: postfix-users@postfix.org
Subject: Re: dict_ldap_lookup questions
On Fri, Feb 10, 2017 at 05:37:36PM +, Gomes, Rich wrote:
> It's going against MS AD, I am sure indexing is configured correctly there.
That rather depends on what query
On Fri, Feb 10, 2017 at 05:37:36PM +, Gomes, Rich wrote:
> It's going against MS AD, I am sure indexing is configured correctly there.
That rather depends on what query you're sending, and how AD is
configured. Your confidence does not inspire confidence. :-(
> What can I do on my postfix s
ruary 10, 2017 12:33 PM
To: postfix-users@postfix.org
Subject: Re: dict_ldap_lookup questions
On Fri, Feb 10, 2017 at 05:21:18PM +, Gomes, Rich wrote:
> Can you point me in the right direction for indexing?
> All I can find is adding this line to the config:
> result_attribute = mem
On Fri, Feb 10, 2017 at 05:21:18PM +, Gomes, Rich wrote:
> Can you point me in the right direction for indexing?
> All I can find is adding this line to the config:
> result_attribute = memberaddr (this was in an expanding groups thread)
LDAP data indexing is something that happens in the LD
...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Friday, February 10, 2017 12:09 PM
To: Postfix users
Subject: Re: dict_ldap_lookup questions
> On Feb 10, 2017, at 12:01 PM, Gomes, Rich wrote:
>
> warning: dict_ldap_lookup: Search error -5: Timed out
You've probably neglected to index t
> On Feb 10, 2017, at 12:01 PM, Gomes, Rich wrote:
>
> warning: dict_ldap_lookup: Search error -5: Timed out
You've probably neglected to index the appropriate attributes.
Fix the indexing, and the timeouts will likely go away.
> Is this simply a matter of increasing the timeout?
No your LDAP
I've started to see a lot of these errors, albeit intermittently:
warning: dict_ldap_lookup: Search error -5: Timed out
Followed by these:
NOQUEUE: reject: RCPT from unknown[x.x.x.x]: 451 4.3.0
: Temporary lookup failure
This server is functioning as an internal relay (no local users) and is
15 matches
Mail list logo
