Mailspring: Inbox unread count incorrect—persistent "1 new message"

Created on 26 Feb 2018  Â·  15Comments  Â·  Source: Foundry376/Mailspring

What operating system are you using?

MacOS 10.13.3

What version of Mailspring are you using?

1.1.4-22d9f20d

Do you have any third-party plugins installed? If so, which ones?

None

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

Perhaps—I only use Gmail, but it is appearing in one of three Gmail accounts I have synced to Mailspring.

Is the issue reproducible with a particular attachment, message, signature, etc?

As you can see in the attached Mailspring and webmail screenshots, the app is reporting an unread message that is not appearing in the Gmail web interface (nor my wife's web interface; we share this account). I tried removing and re-adding the account, to no avail. Just thought I'd share in case someone else is having the same problem (though I didn't see anything about unread accounts when I searched known issues).

Thanks for a great and improving product.

Brian

screen shot 2018-02-25 at 8 30 10 pm
screen shot 2018-02-25 at 8 30 23 pm

Most helpful comment

It's definitely an issue that needs to be corrected, however for those curious as to a short term fix there is a solution. Go into "Unread" and then click on whatever the thread of emails is that's causing the incorrect unread mark. Then at the top click the "Mark as Unread" (because even though it's claiming to be read, it's not letting you "Mark as Read" because of this bug). Once you've done that it will change to allow you to "Mark as Read".

For the developers, I found this solution from someone who I recommended the software to when I went through and noticed that even after expanding the emails it still claimed it was unread. Unfortunately my inbox is almost never at 0 (and in fact is usually several thousand beyond that :'D) but syncing and refreshing both did not, nor did expanding each message. Although, and I double clicked on it rather fast so I cannot confirm this, but it seemed to mark it as read, or at least removed the '1' the moment I clicked "Mark as Unread". Perhaps I didn't see it properly or perhaps that is a point in the direction of the error, but again it's not something solved by expanding, syncing, or restarting the application.

I hope this helps.

(On a side note I love the product and you really should consider a lifetime license because while I wouldn't pay a subscription fee for it I definitely would pay a decent bit to support the project if there was a lifetime license available. Either way keep up the great work.)

All 15 comments

Same here on Ubuntu 16.04, only I have also had a larger number on occasion. I am able to temporarily resolve the issue by marking ALL my mail as unread and then re-marking it as read, but the issue will eventually return. If I perform this action on my mail in chunks the number will decrement gradually, which seems to imply it is particular messages causing this bug and not just a random number.

Hey! Is this like #616 (which was a dupe of https://github.com/Foundry376/Mailspring/issues/247)?

Have you checked in the Unread section just under Inbox like in the video? If the messages are there, that should at least help you do the toggle trick on the specific messages instead of the whole inbox. But yeah, I agree this is annoying, as it keep happening daily to me at least.

In my case that solved the issue:
I had a message in the "Unread" section (as suggested by @louim .
There was a message, that was a series of collapsed messages. I think one of them was unread. I simply opened them all and then the new message was gone.

Hope it helps.

The suggestion from @louim has sped up the time to clear this error each time it happens, but it is still happening, and the cause in my case isn't due to a chain email as suggested by @RedaBousbah. I often have old messages pop up as unread even if it is a single email. I haven't been able to find any pattern among the messages that are switching back to unread, so I'm guessing its just random. The time interval between each occurance is also seemingly random.

I've got the same issue. It is a specific thread of messages that was causing it. They would show up in the unread folder, but would display in every other way as being read (text normal instead of bold, "Mark as unread" icon in toolbar).

Gallium OS, no plugins, Mailspring 1.2.2-96fb3a99

I have the same issue and i have noticed it happens to me when I read an email using another email client.

I have the same issue. I'm using Mac mail and Mailspring in a same time. I don't know that it causes this issue but this is really annoying..

Same. I used the mac client.

I've been getting this issue more frequently the past week or so. v1.5.2 on ubuntu 18.04.

To fix I need to go to unread, mark the thread as unread (because it's inexplicably unread there too), then mark as read.

this issue is still happening, ubuntu 18.04

FWIW I'm getting the same thing on MacOS Mojave 10.14.6 and Ubuntu 18.04

can we just add a "marked as read" menu item as a defensive function to this bug? the number highlighted as unread but actually no is quite annoying.

This would be great. Currently one has to mark as unread and then view the email to clear the alert

Sent from my iPad

On Jan 28, 2020, at 11:16 AM, Tom CHEN notifications@github.com wrote:


can we just add a "marked as read" menu item as a defensive function to this bug? the number highlighted as unread but actually no is quite annoying.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

It's definitely an issue that needs to be corrected, however for those curious as to a short term fix there is a solution. Go into "Unread" and then click on whatever the thread of emails is that's causing the incorrect unread mark. Then at the top click the "Mark as Unread" (because even though it's claiming to be read, it's not letting you "Mark as Read" because of this bug). Once you've done that it will change to allow you to "Mark as Read".

For the developers, I found this solution from someone who I recommended the software to when I went through and noticed that even after expanding the emails it still claimed it was unread. Unfortunately my inbox is almost never at 0 (and in fact is usually several thousand beyond that :'D) but syncing and refreshing both did not, nor did expanding each message. Although, and I double clicked on it rather fast so I cannot confirm this, but it seemed to mark it as read, or at least removed the '1' the moment I clicked "Mark as Unread". Perhaps I didn't see it properly or perhaps that is a point in the direction of the error, but again it's not something solved by expanding, syncing, or restarting the application.

I hope this helps.

(On a side note I love the product and you really should consider a lifetime license because while I wouldn't pay a subscription fee for it I definitely would pay a decent bit to support the project if there was a lifetime license available. Either way keep up the great work.)

It's definitely an issue that needs to be corrected, however for those curious as to a short term fix there is a solution. Go into "Unread" and then click on whatever the thread of emails is that's causing the incorrect unread mark. Then at the top click the "Mark as Unread" (because even though it's claiming to be read, it's not letting you "Mark as Read" because of this bug). Once you've done that it will change to allow you to "Mark as Read".

For the developers, I found this solution from someone who I recommended the software to when I went through and noticed that even after expanding the emails it still claimed it was unread. Unfortunately my inbox is almost never at 0 (and in fact is usually several thousand beyond that :'D) but syncing and refreshing both did not, nor did expanding each message. Although, and I double clicked on it rather fast so I cannot confirm this, but it seemed to mark it as read, or at least removed the '1' the moment I clicked "Mark as Unread". Perhaps I didn't see it properly or perhaps that is a point in the direction of the error, but again it's not something solved by expanding, syncing, or restarting the application.

I hope this helps.

(On a side note I love the product and you really should consider a lifetime license because while I wouldn't pay a subscription fee for it I definitely would pay a decent bit to support the project if there was a lifetime license available. Either way keep up the great work.)

Thanks mate, that worked for me.

Was this page helpful?
0 / 5 - 0 ratings