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

6.0.0-beta1

7/3/25

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	09/04/2018 (2494 days ago)
Due
Updated	03/02/2019 (2315 days ago)
Assigned	11/21/2018 (2416 days ago)
Resolved	03/02/2019 (2315 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/02/2019 03:48:24 PM	Michael Rubinsky	State ⇒ Not Reproducible

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

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

09/04/2018 09:12:01 AM	matthias (dot) althaus (at) iserv (dot) eu	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ ImapClient fails to detect proper subtree structure Queue ⇒ Horde Framework Packages Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	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