Bug 146247 - Address completition doesn't work with all resources
Summary: Address completition doesn't work with all resources
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: composer (show other bugs)
Version: 1.9.7
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 146249 160599 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-06-01 13:03 UTC by Andre Mathibe
Modified: 2009-08-29 12:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
my ~/.kde/share/config/kresources/contact/stdrc (1.99 KB, text/plain)
2007-06-06 22:49 UTC, Wouter Horré
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Mathibe 2007-06-01 13:03:39 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Unlisted Binary Package
OS:                Linux

since i´ve updated to KDE 3.5.7 from 3.5.6 (http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/), the completition of an eMail-address in the to:/cc:/bcc. field does not work with existing addressbook-resources and recent addresses.
Only queries to the LDAP-Server (if) defined in kaddressbook will give me a result.

Has it to do with this? (found in http://www.kde.org/announcements/changelogs/3_5_7/kdepim.txt)

2007-03-28 20:16 +0000 [r647591] schaarsc

* branches/KDE/3.5/kdepim/libkdepim/addresseelineedit.cpp,
branches/KDE/3.5/kdepim/libkdepim/ldapclient.cpp: - fix broken
ldapSearch - lookup domain in ldapSearch (kmailcompletion already
does) - do not load all contacts from ldapkio, use ldapSearch
instead - do not reload local contacts with each ldapSearch
(implies contact caching)




This bug isn´t common to the existing (resolved) bug # 86292


For a workaround i´ve downgraded kdepim to version 3.5.6


regards 

Andre Mathibe
Comment 1 Thomas McGuire 2007-06-05 23:41:42 UTC
*** Bug 146249 has been marked as a duplicate of this bug. ***
Comment 2 Thomas McGuire 2007-06-05 23:42:54 UTC
Adjusting summary.
Comment 3 Christian Schaarschmidt 2007-06-06 22:22:43 UTC
I cannot reproduce this bug on my machine. 
could you provide me with your ~/.kde/share/config/kresources/contact/stdrc
to give me an idea of your configuration. 
(replace ldap user/host and other confidential info with ####)
Comment 4 Wouter Horré 2007-06-06 22:49:21 UTC
Created attachment 20790 [details]
my ~/.kde/share/config/kresources/contact/stdrc

This for the case where there is no completion from ldap, but completion from a
local resource works.

The second ldap resource (localhost) is actually a connection through stunnel4
to a remote ldaps-server.
Comment 5 Christian Schaarschmidt 2007-06-07 01:45:04 UTC
please check kaddressbook configuration

add your server to the LDAP search function
Comment 6 Wouter Horré 2007-06-11 12:09:23 UTC
Do you mean "LDAP lookup" in the kaddressbook configuration? I don't see why that would be necessary. That would mean I have to duplicate the configuration for my ldap resources, since the ldap servers are already configured as a resource. In kde 3.5.6, it works without adding the ldap servers to the LDAP lookup configuration in kaddressbook.

I have also compared the output of:
$ grep -ri addressbook ~/.kde/share/config
on a machine with KDE 3.5.6 and one with KDE 3.5.7. There is no significant difference. Are there any other things I could compare between these two machines?
Comment 7 Christian Schaarschmidt 2007-06-11 18:33:42 UTC
LDAP lookup is necessary for the asynchronous LDAP search, if you don't want to browse/edit the directory you don't need to configure a resource.

kmail 3.5.6 did download all LDAP contacts for each mail which is not desirable because of performance issues and unnecessary network traffic. patch r647591 did activate ldapSearch, see Bug 110867.

The original report complains about recent-address not working. Can you provide more information to reproduce that issue?
Otherwise I would tend to close this bug.
Comment 8 Wouter Horré 2007-06-12 10:29:30 UTC
Christian,

Thanks for the clarification. One of the ldap servers I use is actually read-only, so I removed it as a resource and added it in LDAP Lookup. Autocompletion does work again now for this server.

The other LDAP server is my personal addressbook that I have placed in LDAP to be able to use it from several instances of kmail. It is read/write... If I want autocompletion to work for that, I guess I'll have to duplicate my configuration? It would be nice if there was a possibility to link to the existing resource configuration from the LDAP lookup configuration. Or alternatively, auto completion from an LDAP resource should also use ldapSearch. (Should this be filed as a new bug?)

With respect to the other problem: I have never encountered that. I filed a separate bug for my problem, but it was merged later on.
Comment 9 Christian Schaarschmidt 2007-06-12 18:42:36 UTC
sorry, but for your local LDAP you'll have to duplicate the config.

we are concentrating manpower on KDE4, there will be no fix for this issue in 3.5.
KDE4 will come with a new backend (akonadi) for pim-applications. with the new infrastructure this should not be necessary anymore.
Comment 10 BJ Blanchard 2007-10-05 16:52:45 UTC
Similar to bug 146249 - which was marked as a duplicate - kdepim-enterprise, which  contains the patch from [r647591] schaarsc under revision 668105, has broken address completion from LDAP resource.

It does not make sense that ANY resource defined be excluded from address completion.  If there are performance issues, then address those - don't break kmail.

I backed out this patch and rebuilt and now LDAP completion is working as it should.

This is definitely a bug and should be re-opened.

BJ.
Comment 11 Thomas McGuire 2008-04-13 20:31:44 UTC
*** Bug 160599 has been marked as a duplicate of this bug. ***
Comment 12 Dyllan Pascoe 2008-04-15 19:41:32 UTC
I cannot see the logic in not fixing this bug. Yes KDE4 is priority for the devel team but although the developers must have full confidence in their software (KDE4), it is not wise for a large corporate environment to upgrade a stable KDE environment from 3.5.8 to 4.x without proper testing and implementation that will take time. KDE 3.5.8 is near perfect except for this extremely frustrating bug in KMail which should be fixed as it burden's productivity.

Now i am forced to downgrade to a working 3.5.6 which also makes no sense, but that is how crucial the email auto-completion is to a large corporate these days.

On a side note i take my hat off to the KDE Developers for KDE, fantastic Opensource software.
Comment 13 Allen Winter 2008-04-22 15:50:45 UTC
re-open.
we are expecting a patch soon
Comment 14 Kevin Ottens 2008-04-23 10:52:14 UTC
SVN commit 800071 by ervin:

Don't filter out ldapkio resources for the auto-completion.

That should fix 146247, at least now that works for me. Please test and
close if appropriate.

CCBUG: 146247


 M  +2 -3      addresseelineedit.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=800071
Comment 15 Dario Andres 2009-04-04 16:21:39 UTC
Any news on this ? Should the report be closed ?
Comment 16 Pavel Lastovicka 2009-04-06 10:49:41 UTC
(In reply to comment #15)
> Any news on this ? Should the report be closed ?

AFAIK only the enterprise branch is fixed. Not every Linux distribution uses it. IMHO the fix should go into main code tree also.
Comment 17 Martin Koller 2009-08-29 12:04:35 UTC
it went also into the main trunk:
http://websvn.kde.org/?view=rev&revision=800132