| 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 | 9/4/18 (2846 days ago) |
| Due | |
| Updated | 3/2/19 (2667 days ago) |
| Assigned | 11/21/18 (2768 days ago) |
| Resolved | 3/2/19 (2667 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
Assigned to Michael Rubinsky
Priority ⇒ 1. Low
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ ImapClient fails to detect proper subtree structure
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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