Bug 212052

Summary: kmail dimap to domino server duplicates inbox
Product: [Unmaintained] kmail Reporter: David Goodenough <david.goodenough>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description David Goodenough 2009-10-27 13:53:25 UTC 
Version:            (using KDE 4.3.2)
Installed from:    Debian testing/unstable Packages

When I connect kmail to my Lotus Domino server and I set up an account using disconnected IMAP I get two inboxes (both with the inbox icon).  They both seem to get the same content, so everything is duplicated.  Neither of them appear in the Local Subscriptions list, so I can not unsubscribe from one of them.

I thought I had found references to this being a known problem, but I can no longer find these references.  This is not a new problem, it also exists in 3.5.10.

I can provide access to a Domino server if that would help a developer fix the problem.
Comment 1 David Goodenough 2009-11-02 12:49:55 UTC 
I notice in /.kde/share/config/kmailrc that both are present, one called INBOX and the other called Inbox.  Both however are called Inbox on the UI.  I suspect this could be cured by doing a case insensitive search for the name Inbox.
Comment 2 David Goodenough 2009-11-02 12:55:41 UTC 
Small correction, on the UI they are both called inbox - so in both cases the case has been folded to lower case.  So the logic would be to do the same when looking at the list of folders so as to remove the duplication.
Comment 3 David Goodenough 2009-11-04 15:25:07 UTC 
With kmail 1.12.2 I get a slightly different behaviour.  Both inboxes are show,  but all the mail gets put in the first one (and every message appears twice).  When I classify one of these duplicates as SPAM the other one looses its date and moved from (say) Today to Unknown.
Comment 4 Christophe Marin 2009-11-20 00:37:39 UTC 

*** This bug has been marked as a duplicate of bug 93812 ***