Tickets :: [#14853] ImapClient fails to detect proper subtree structure

6.0.0-git

2019-07-19

Summary	ImapClient fails to detect proper subtree structure
Queue	Horde Framework Packages
Type	Bug
State	Not Reproducible
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	matthias.althaus (at) iserv (dot) eu
Created	2018-09-04 (318 days ago)
Due
Updated	2019-03-02 (139 days ago)
Assigned	2018-11-21 (240 days ago)
Resolved	2019-03-02 (139 days ago)
Milestone
Patch	No

2019-03-02 15:48:24	Michael Rubinsky	State ⇒ Not Reproducible

2018-11-21 15:08:08	Michael Rubinsky	Comment #3 State ⇒ Feedback	Reply to this comment
Please provide an imap client debug log.

2018-10-23 01:13:40	Michael Rubinsky	Comment #2 Priority ⇒ 1. Low Assigned to Michael Rubinsky	Reply to this comment
Still trying to reproduce this.

2018-09-04 09:12:01	matthias (dot) althaus (at) iserv (dot) eu	Comment #1 Type ⇒ Bug State ⇒ Unconfirmed Priority ⇒ 2. Medium Summary ⇒ ImapClient fails to detect proper subtree structure Queue ⇒ Horde Framework Packages Milestone ⇒ Patch ⇒ No	Reply to this comment
Hi, we've encountered a bug when using the Imap_Client to fetch a mailbox structure like this: INBOX INBOX/foo INBOX/foo/bar INBOX/foo-bar INBOX/bar INBOX/bar/foo Requesting information about `INBOX/foo` returns `\hasnochildren` as soon as the `foo-bar` folder is created. The same request on `INBOX/bar` properly returns `\haschildren`. Cheers Matthias