vvrpgsporcupineorg rolf e sonneveld wietse venema wrote mike kenny others might able speak query mechanism suggestion stop remote queries ldap possible doesnt mean take dumps windows ad required attributes twohourly basis day use generate hashed map files actual address resolution postfix servers dump interval probably represent kpis might relation accountmail account creation speeding query time looking local maps youre annoying ldap administrators constantly thrashing internal network lookups spurious course probably performance tradeoffs hash whatever maps get large dump process takes long believe hash maps comfortably deal enough entries largest organisations thanks tracy million relevant records ldap requirement minimize latency constant updates throughout day night dont think work us without major rearchitecture dumping file save butt next time spammer comes along starts dictionary attack due respect fail see stick dumptoafile technique era quadcore processors gigabit backbones etc cant simply use ldap queries smart caching results exactly bottleneck openldap client routines dont cache caching help sshole dictionary attack mail server cant cache nonexistent names sshole asks addition postfix smtpd nonpersistent processes implement caching nonpersistent ldap clients would store shared local cache might well run local ldap replica wietse thu 07 aug 2008 065909 0500 postfix making many queries ldap