Bug 400325 - Freshly created mailbox with a trailing hierarchy separator is not shown
Summary: Freshly created mailbox with a trailing hierarchy separator is not shown
Status: RESOLVED WORKSFORME
Alias: None
Product: trojita
Classification: Unmaintained
Component: IMAP (show other bugs)
Version: git
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Trojita default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-26 09:23 UTC by Jan Kundrát
Modified: 2023-01-01 05:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kundrát 2018-10-26 09:23:05 UTC
When I create a mailbox for storing other mailboxes, the LIST command which gets issued to discover it does not return any mailboxes because the LIST contains the trailing hierarchy separator:

11:19:22.527 >>> y88 CREATE "dev.ONF."␍␊
11:19:22.536 <<< y87 OK Idle completed (0.028 + 6.534 + 6.561 secs).␍␊
11:19:22.546 <<< y88 OK Create completed (0.000 + 0.000 secs).␍␊
11:19:22.546 >>> y89 LIST "" "dev.ONF."␍␊
11:19:22.553 <<< y89 OK List completed (0.000 + 0.000 secs).␍␊
11:19:22.553 Imap::Mailbox::CreateMailboxTask Completed
11:19:28.854 >>> y90 IDLE␍␊
11:19:28.864 <<< + idling␍␊
11:19:40.883 >>> DONE␍␊
11:19:40.884 Imap::Mailbox::GetAnyConnectionTask Activated
11:19:40.885 Imap::Mailbox::GetAnyConnectionTask Completed
11:19:40.886 Imap::Mailbox::CreateMailboxTask Activated
11:19:40.959 >>> y91 CREATE "dev.ONF."␍␊
11:19:40.968 <<< y90 OK Idle completed (0.001 + 12.106 + 12.105 secs).␍␊
11:19:40.977 <<< y91 NO [ALREADYEXISTS] Mailbox already exists (0.000 + 0.000 secs).␍␊

When listing mailboxes, we should not include the trailing dot (the hierarchy separator).
Comment 1 Justin Zobel 2022-12-02 01:23:09 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-17 05:14:02 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-01-01 05:20:37 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!