[GH-ISSUE #349] Deleting an IMAP server can break special folder associations #300

New issue

Closed

opened 2026-02-25 21:34:41 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:34:41 +03:00

Owner

Originally created by @jasonmunro on GitHub (Jun 21, 2019).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/349

Originally assigned to: @jasonmunro on GitHub.

Deleting an IMAP server can cause the association of special folders to be "offset" because they are using server ids which can change between login. We need to:

change the data structure used by the imap folders module set to use the IMAP server name and username to associate the special folders instead of the id.
re-save the details maybe as a one time check on login so it can be done without user interaction. Need to think about that. Worst case this becomes a non-backwards compatible fix and users will have to re-assign their special folders.

Originally created by @jasonmunro on GitHub (Jun 21, 2019). Original GitHub issue: https://github.com/cypht-org/cypht/issues/349 Originally assigned to: @jasonmunro on GitHub. Deleting an IMAP server can cause the association of special folders to be "offset" because they are using server ids which can change between login. We need to: - change the data structure used by the imap folders module set to use the IMAP server name and username to associate the special folders instead of the id. - re-save the details maybe as a one time check on login so it can be done without user interaction. Need to think about that. Worst case this becomes a non-backwards compatible fix and users will have to re-assign their special folders.

kerem

2026-02-25 21:34:41 +03:00

closed this issue
added the
bug

imap_folders
labels

kerem commented

2026-02-25 21:34:41 +03:00

Author

Owner

@dumblob commented on GitHub (Jun 21, 2019):

Worst case this becomes a non-backwards compatible fix and users will have to re-assign their special folders.

If there will be a semi-automated way of backing them up (or exporting) in a human (not necessarily machine) readable format (e.g. some txt or structured JSON or SQL dump or you name it) either as the user, then I would say there is no obstacle and we don't need to preserve backward compatibility and just add a huge warning to the documentation for the last release supporting the old behavior and also to the installation/init setup procedure of the newer versions for the next 12 months while copying the current DB (or just the relevant tables) somewhere to avoid potential loss of user settings.

@dumblob commented on GitHub (Jun 21, 2019): >Worst case this becomes a non-backwards compatible fix and users will have to re-assign their special folders. If there will be a semi-automated way of backing them up (or exporting) in a human (not necessarily machine) readable format (e.g. some txt or structured JSON or SQL dump or you name it) either as the user, then I would say there is no obstacle and we don't need to preserve backward compatibility and just add a huge warning to the documentation for the last release supporting the old behavior and also to the installation/init setup procedure of the newer versions for the next 12 months while copying the current DB (or just the relevant tables) somewhere to avoid potential loss of user settings.

kerem commented

2026-02-25 21:34:41 +03:00

Author

Owner

@kroky commented on GitHub (Feb 23, 2021):

I think https://github.com/jasonmunro/cypht/pull/454 should fix this issue.

@kroky commented on GitHub (Feb 23, 2021): I think https://github.com/jasonmunro/cypht/pull/454 should fix this issue.

kerem commented

2026-02-25 21:34:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Jul 14, 2022):

The problem persists and it's not just special folders: https://github.com/jasonmunro/cypht/issues/573

@marclaporte commented on GitHub (Jul 14, 2022): The problem persists and it's not just special folders: https://github.com/jasonmunro/cypht/issues/573

kerem referenced this issue

2026-02-25 21:36:12 +03:00

[PR #300] [MERGED] 🚀 github templates #779