kabc silenty completes after the 1000 record limit

[Ritesh Raj Sarraf]

Binary package hint: kaddressbook

Hi,

I'm not sure if people have come across this problem.

If you're using Kontact as your PIM Application and KAB as your Address Book
application, you can configure your address book to contact the exchange
(ldap) server to get all the address records.

The problem is that either ldapsearch or exchange has put a restriction of max
1000 records per query. (You can verify that with the ldapsearch command.
It'll terminate after receiving 1000 records).

I think kabc's ldap code also inherits the same bug and is only able to fetch
1000 records, after which it silently keeps quiet (It should rather have
popped up an error message). Or else have a workaround in place to fetch all the records bypassing this limit

I'm attaching a workaround (in Python) which fetches all the records.

But there still is a problem. With the workaround in place, I end up with 9000 records. This should be a normal case in any huge organization. But when typing the contact in the "To:" box of Kmail's composer, it ends up being very slow because of the large number of records.
Kmail should be able to efficiently filter the contact (as typed) from the large number of records.

[Ritesh Raj Sarraf (rrs)]

This workaround fetches all contact details from the exchange server.

[Rich Johnson (nixternal)]

Confirming due to upstream report response. Seems to be an "offline" issue only according to the upstream report.

[Richard Birnie (rbirnie-deactivatedaccount)]

Hi,

There hasn't been any activity on this report or in the upstream thread for over 1 year. Is this still an issue in KDE4? If so what version of kabc, KDE and Kubuntu are you using?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!