ubuntu breezy korganizer not showing Journal Entries stored in IMAP

[Matthew Carpenter]

Kontact (Korganizer):
I'm storing my contacts/journal/calendar in an IMAP folder through KMail.
When I create Journal entries I can see that they've been created (viewing the
IMAP folder), and can see the journal entry for the duration of using Kontact.
When I close Kontact and start it back up, they do not appear in the Journal
page (although the data is still in the IMAP folder).

This is pretty vital to me for using the Journal.

Thanks!

[Rocco Stanzione (trappist)]

This is probably a symptom of bug 19457. Can you see whether contacts stored in an IMAP folder behave the same way, and if so mark this a duplicate of that bug?

[Matthew Carpenter (matt-eisgr)]

Nope. Contacts and everything stores and retrieves just fine using an IMAP storage resource. That is all working supremely well for me. The journal entries are even being stored correctly, the journal viewer simply doesn't show any IMAP-stored entries.

Thanks
Matt

[Jon Skanes (jon-skanes)]

I can confirm this bug.

I've tried a few different builds of UW-IMAP recently. It seems to happen with them all: both 2004 and 2006 versions. Matt, do you know what type of IMAP server you're connecting to?

Here's my post to the Kubuntu forums:

Hi Everyone,

Before I report this as a bug, I'd like to see if anyone has had similar problems.

I'm running Kontact 1.2.3, Korganizer 3.5.5, Kmail 1.9.1 from the sources listed in the Kubuntu site news for KDE-3.5.5. My IMAP server is running UW-IMAP 2006c1 with 'mix' format mailboxes. The problem also occured when i was using 'mbx' format mailboxes. This seemed to effect KDE 3.5.[43] as well.

Every time I restart Korganizer all my journal entries disappear until I rebuild the IMAP cache in Kmail for each journal folder. I have two journal folders configured for the IMAP server; one is for personal info and is private, the other is a group shared IMAP resource. This effects both folders. There is no data loss that I can see, however, the time it takes to rebuild the IMAP cache is very annoying.

I had been hoping to role this out as a workgroup solution for some of my small business customers. It won't be feasible until i can get a solution. The amount of journal use for some of these customers is huge making rebuilds very intensive for network, server, and client resources.

I don't know a whole lot about IMAP, but could this have something to do with the message UIDs? I'm willing to spend a bit of time troubleshooting this if anyone can give me some suggestions.

Thanks,
Jon

[Matthew Carpenter (matt-eisgr)]

I use Cyrus IMAPd almost exclusively. I'm also using Dapper, and I believe
the bug in question was fixed in Breezy. However, now in Dapper, I seem to
be having issues keeping my dimap entries alive... My groupware account is
right now listing no entries... I've only really noticed this in the past
few weeks.

[Matthew Carpenter (matt-eisgr)]

Sorry for the weird misdirection on the last entry. This is still a problem. I'm about to start using a local file resource for Journal entries, but that is less than ideal.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

appears to be fixed in 3.5.6, which will be in feisty in the next day or so.