Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IMAP unread count is too high #6394

Closed
amelchio opened this issue Mar 4, 2017 · 0 comments · Fixed by #6395
Closed

IMAP unread count is too high #6394

amelchio opened this issue Mar 4, 2017 · 0 comments · Fixed by #6395

Comments

@amelchio
Copy link
Contributor

amelchio commented Mar 4, 2017

Home Assistant release (hass --version):

0.38.4 (downgraded due to #6299)

Python release (python3 --version):

Python 3.6.0

Component/platform:

IMAP

Description of problem:

The IMAP unread counter is sometimes too high.

Expected:

The unread count should match the value in my normal mail clients.

amelchio added a commit to amelchio/home-assistant that referenced this issue Mar 4, 2017
Message deletion in IMAP is a two step process: first delete, then expunge.
Deleting a message just sets a flag that usually makes the mail client hide
the message. It is the expunge that actually removes the message.

Thus, exclude the deleted messages so that the unread count matches up with
that of most mail clients.
balloob pushed a commit that referenced this issue Mar 5, 2017
Message deletion in IMAP is a two step process: first delete, then expunge.
Deleting a message just sets a flag that usually makes the mail client hide
the message. It is the expunge that actually removes the message.

Thus, exclude the deleted messages so that the unread count matches up with
that of most mail clients.
@balloob balloob mentioned this issue Mar 11, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Jul 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant