> I submitted a bug#: 46778. It's still 'unconfirmed'. > > Just want to check if anyone else is having this problem > in a similar environment: > > Evolution 1.4.3 > Redhat 9.0 ( lastest patch from RHN ) > LDAP server is company's internal server.
Oh yeah, you're not alone... http://bugzilla.ximian.com/show_bug.cgi?id=44873 http://bugzilla.ximian.com/show_bug.cgi?id=41523 http://bugzilla.ximian.com/show_bug.cgi?id=41081 http://bugzilla.ximian.com/show_bug.cgi?id=46124 http://bugzilla.ximian.com/show_bug.cgi?id=40379 One of the problems with LDAP autocomplete is that the LDAP search pattern is hardcoded. As long as your LDAP server indexes all the fields that the evo autocomplete search specifies in its pattern, it'll generally return a result within a reasonable amount of time, and autocomplete might work (sort-of-sometimes, if you type slowly enough). If one (or more) of the fields in the hardcoded search pattern are not indexed, the result will take *way* too long for an interactive autocomplete, and it won't work at all. I've long since given up on having a nice working (like netscape4/mozilla) LDAP autocomplete, and just enjoy evolution for the rest of its really nice features... Cheers! -- Brett _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
