[GH-ISSUE #85] [Bug] Crash with existing encrypted cache created before a password change #74

Closed
opened 2026-03-03 01:19:35 +03:00 by kerem · 2 comments
Owner

Originally created by @Kabouik on GitHub (May 17, 2021).
Original GitHub issue: https://github.com/d99kris/nmail/issues/85

Originally assigned to: @d99kris on GitHub.

If the IMAP password is changed and there is an existing encrypted cache, the account cannot be opened in nmail until the cache is deleted and rebuilt from scratch. This can be an issue for people who rely on local storage to keep their emails but keep small server storage, and those are the most likely to use encryption for their big local cache I guess.

I noticed that on a config with different SMTP and IMAP accounts, and it occurred when changing the IMAP password. Not sure if the same would happen with SMTP as it's not directly related to the cache.

Let me know if you cannot reproduce and I'll collect some logs.

Originally created by @Kabouik on GitHub (May 17, 2021). Original GitHub issue: https://github.com/d99kris/nmail/issues/85 Originally assigned to: @d99kris on GitHub. If the IMAP password is changed and there is an existing encrypted cache, the account cannot be opened in nmail until the cache is deleted and rebuilt from scratch. This can be an issue for people who rely on local storage to keep their emails but keep small server storage, and those are the most likely to use encryption for their big local cache I guess. I noticed that on a config with different SMTP and IMAP accounts, and it occurred when changing the IMAP password. Not sure if the same would happen with SMTP as it's not directly related to the cache. Let me know if you cannot reproduce and I'll collect some logs.
kerem closed this issue 2026-03-03 01:19:35 +03:00
Author
Owner

@d99kris commented on GitHub (Oct 16, 2021):

Finally got a chance to take a look at this, it should be fixed with above commit. Please let me know if you encounter any issues. Thanks!

<!-- gh-comment-id:944888115 --> @d99kris commented on GitHub (Oct 16, 2021): Finally got a chance to take a look at this, it should be fixed with above commit. Please let me know if you encounter any issues. Thanks!
Author
Owner

@Kabouik commented on GitHub (Oct 16, 2021):

Thanks!

On 2021-10-16 11:35 Kristofer Berggren @.***> wrote:

Finally got a chance to take a look at this, it should be fixed with
above commit. Please let me know if you encounter any issues.
Thanks!

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/d99kris/nmail/issues/85#issuecomment-944888115

<!-- gh-comment-id:944888863 --> @Kabouik commented on GitHub (Oct 16, 2021): Thanks! On 2021-10-16 11:35 Kristofer Berggren ***@***.***> wrote: > Finally got a chance to take a look at this, it should be fixed with > above commit. Please let me know if you encounter any issues. > Thanks! > > -- > You are receiving this because you authored the thread. > Reply to this email directly or view it on GitHub: > https://github.com/d99kris/nmail/issues/85#issuecomment-944888115
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/nmail#74
No description provided.