[GH-ISSUE #556] Imap folders and sub-folders don't appear in some cases #405

Closed
opened 2026-02-25 21:34:56 +03:00 by kerem · 6 comments
Owner

Originally created by @smitgd on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/556

🐛 Bugreport

In my main imap account I only see the top-level folders. Several top-level folders definitely have sub folders, including INBOX, but a + does not appear beside them. On other accounts the sub-folders seem to be working OK. Not sure why there is difference between accounts. All folders and sub-folders on this account have us-ASCII names.

I also noticed that when I was first setting up my accounts, all folders on accounts with folder names containing non-US-Ascii characters would not appear until I renamed the folders (in thunderbird) with US-Ascii chars. Then all the folders appeared. However, after the folders appeared and I changed a single folder name back to a non-US-Ascii name, the folders still appeared and showed the UTF-8 character.

I don't know if these issues are related.

Originally created by @smitgd on GitHub (Feb 27, 2022). Original GitHub issue: https://github.com/cypht-org/cypht/issues/556 ## 🐛 Bugreport <!-- Describe your issue in detail. Include screenshots if needed. Give us as much information as possible. --> In my main imap account I only see the top-level folders. Several top-level folders definitely have sub folders, including INBOX, but a ```+``` does not appear beside them. On other accounts the sub-folders seem to be working OK. Not sure why there is difference between accounts. All folders and sub-folders on this account have us-ASCII names. I also noticed that when I was first setting up my accounts, all folders on accounts with folder names containing non-US-Ascii characters would not appear until I renamed the folders (in thunderbird) with US-Ascii chars. Then all the folders appeared. However, after the folders appeared and I changed a single folder name back to a non-US-Ascii name, the folders still appeared and showed the UTF-8 character. I don't know if these issues are related.
kerem 2026-02-25 21:34:56 +03:00
Author
Owner

@marclaporte commented on GitHub (May 9, 2022):

@smitgd

Sorry you are running into issues.

Can you create an account with no confidential information to demonstrate the issue, and share that with one of our developers?

Please join us at https://gitter.im/cypht-org/community so we can coordinate.

Thanks!

<!-- gh-comment-id:1120583824 --> @marclaporte commented on GitHub (May 9, 2022): @smitgd Sorry you are running into issues. Can you create an account with no confidential information to demonstrate the issue, and share that with one of our developers? Please join us at https://gitter.im/cypht-org/community so we can coordinate. Thanks!
Author
Owner

@marclaporte commented on GitHub (May 6, 2024):

@smitgd

Please retest, as a lot has changed since you reported this issue. Notably, we now have 3 active branches and recently released Cypht 2.0.0

<!-- gh-comment-id:2097115223 --> @marclaporte commented on GitHub (May 6, 2024): @smitgd Please retest, as a lot has changed since you reported this issue. Notably, we now have 3 active branches and recently released Cypht 2.0.0 - https://github.com/cypht-org/cypht/releases/tag/v2.0.0 - https://github.com/cypht-org/cypht/wiki/Lifecycle
Author
Owner

@truthsword commented on GitHub (May 24, 2024):

Just saw this thread... similar report here

<!-- gh-comment-id:2130499028 --> @truthsword commented on GitHub (May 24, 2024): Just saw this thread... similar report [here](https://github.com/cypht-org/cypht/issues/1046)
Author
Owner

@marclaporte commented on GitHub (May 25, 2024):

Good catch @truthsword !

<!-- gh-comment-id:2130536522 --> @marclaporte commented on GitHub (May 25, 2024): Good catch @truthsword !
Author
Owner

@marclaporte commented on GitHub (Sep 28, 2024):

@smitgd who is your ISP?

<!-- gh-comment-id:2380410477 --> @marclaporte commented on GitHub (Sep 28, 2024): @smitgd who is your ISP?
Author
Owner

@marclaporte commented on GitHub (Jan 21, 2025):

Solved via https://github.com/cypht-org/cypht/pull/1427

<!-- gh-comment-id:2605229218 --> @marclaporte commented on GitHub (Jan 21, 2025): Solved via https://github.com/cypht-org/cypht/pull/1427
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#405
No description provided.