Version: 3.4.1 (using KDE 3.4.1 Level "a" , SUSE 9.3 UNSUPPORTED) Compiler: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) OS: Linux (i686) release 2.6.11.4-21.7-default Storing addressbook entries on my imap server doesn´t work as expected. Here a short description what i´m doing: 1) Importing fresh address data from ldiv file into the imap resource 2) Nothing from the imported addresses shows up in the address book 3) However Kmail shows the data in inbox/Termine/Kontakte 4) Pressing the save button also shows the imported data in kaddressbook 5) Now i can work with the address data until next restart of kde 6) After a restart of kde (either reboot or init3/5) the addressbook data is still displayed by Kmail but not in kadressbook. 7) I can add fresh data to the addressbook (which is of course stored on the imap server) but still all the old data didn´t display. So, what could be wrong? Do i have to set special permissions on the imap server? Or can´t use i SSL session for imap?
That's a bug in the imap/kolab resource, not in kaddressbook itself.
I can confirm the same here. I have a courier-imap server which has had my contacts/calendar imported to it. The entries show up in the kmail folder view (if you unhide the groupware folders) but not in korganizer/kaddressbook. When a new entry is saved it shows up on the server (if viewed by kmail) but an error pops up saying "Unable to Save" When one of these new entries is then deleted it is removed off the server as expected. I am using KDE 3.4.1 compiled from source using Gentoo.
The problem is still existing in KDE 3.4.2. Can i help in any way to resolve the issue ?
I am experiencing the same problem after upgrading from KDE 3.3 to 3.4.2.
The problem exists with uw-imap server too.
Same trouble with bincimap (set up myself). No display of contacts, but vcards are definitely stored in imap folder. KDE 3.4.2.
*** This bug has been confirmed by popular vote. ***
Please verify whether this issue still exists with a current version of KDE (4.8 or later). I could not reproduce the issue with KDE 4.8.3. Should the issue still exist, please feel free to reopen this ticket.