-
Notifications
You must be signed in to change notification settings - Fork 59
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
Unread count doesn't work with Owl account #166
Comments
Hi, I know a bit of time has passed since you created this issue, but if you are still interested in solving this, we are in the process of changing how we read the unread email counter from the mork files. If you are able it would be awesome if you could test your |
Please provide the feedback whether the latest code fixes this issue, thanks! |
Would you be able to use a different Thunderbird profile (or alternatively delete the
Yeah, because the
If you don't close Thunderbird it never really closes the mork file, even trough it does write to it. This may explain why the modification date never changes. To make sure that Birdtray detects changes in that case, you might need to enable the |
These are .msf files present on the clean profile with ExQuilla Exchange account setup
Birdtray is able to read correct unread counter when those files are selected by holding Thanks for the help with setting things up! |
OS: Ubuntu 19.10 64bit x86
Birdtray version: 1.6
Thunderbird version: 68.1.2
Birdtray origin: package manager (ppa:linuxuprising/apps)
Qt version: NA
Description
I use Owl to access my company's Office 365 account so the path to the
msf
file is a bit different:~/.thunderbird/<profile>.default/webaccountMail/outlook.office.com/Inbox.msf
The file on file seems to be getting updated every time I receive an email so it seems to be the correct file, however I never see the number of unread emails
Expected behavior
Number of unread emails displayed on top of the systray icon.
To Reproduce
Screenshots
Additional context
Running on i3-wm / gnome (Don't know if that's relevant)
The text was updated successfully, but these errors were encountered: