Open Bug 2057745 Opened 14 hours ago Updated 6 hours ago

new mails not checked

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 152
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: petsuter, Unassigned, NeedInfo)

References

Details

Steps to reproduce:

Open Thunderbird.
Account settings: Check "Check for new messages every 10 minutes".
Keep Thunderbird running forever.

Actual results:

Sometimes Thunderbird stops checking messages for no reason.
No checks are done for many days.

Expected results:

It should always check messages every 10 minutes, keep checking forever.

Some users have been reporting gmail issues in support. But the only new bugs reported in last three months about getting new mail is Bug 2043149 - [EWS] Messages do not appear in the inbox folder if I don't click on the inbox folder itself. An older Bug 1931472 doesn't seem to match your issue - Inbox not updating after hybernating until I manually click on "Get Messages"

So I don't believe you are seeing a bug. Suggest you post your issue in support at https://support.mozilla.org/en-US/questions/new/thunderbird. Please post the link to you report request here.

Flags: needinfo?(petsuter)

Thanks.
I opened https://support.mozilla.org/en-US/questions/1594852

I don't see how this it not be a bug when Thunderbird stops checking email.
I had this happen about 10 times on multiple computers for multiple different email providers (one of them gmail, the other not gmail) over the last three to four months.

It is vaguely similar to Bug 2043149 in that the workaround is to manually select other folders and then checking mails starts working again.
It is vaguely similar to Bug 1931472 in that I use imap. I don't use hibernate (but "sleep", it doesn't happen every time after sleep/wakeup).
I use no extensions.

Flags: needinfo?(petsuter)

Sleep has the same effect as hibernate. If the issue only happens after sleep then it could be a match for Bug 1931472. But that was reported 1.6 years ago.

Flags: needinfo?(vseerror)
You need to log in before you can comment on or make changes to this bug.