Thunderbird 74.0b2 does not check for new email at startup
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: rvaldes, Unassigned)
References
Details
(Whiteboard: [support])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Steps to reproduce:
Opened the program and Thunderbird 74.0b2 does not check for email at startup
Actual results:
had to check for mail manually
Expected results:
Mail client should have checked for new mail at startup. all accunt settings are correct and right boxes checked
|
||
Comment 1•5 years ago
|
||
Are these POP3 or IMAP accounts?
I have two POP3, one IMAP account, and two newsgroup accounts all configured to "Check for new messages at startup" in my 74.0b2 on Windows 10 and Ubuntu Linux. All accounts are receiving mail at startup.
Do you have any extensions installed and have you tried safe mode? Use Help > Restart with Add-ons Disabled.
|
Reporter | |
Comment 2•5 years ago
|
||
This is a single IMAP account, I have "Check for new messages at startup" checked.
This was working great until the last update. I do not have any extensions , but I will try safe mode anyway
|
|
Reporter | |
Comment 3•5 years ago
|
||
I tried Safe Mode and it still does not work. Maybe deleting and settingup the account again will help?
|
||
Comment 4•5 years ago
|
||
What happens if you create a new profile with just that account?
|
|
Reporter | |
Comment 5•5 years ago
|
||
Wayne, it seems that when I upgrsaded to 76.0 b1 the problem went away. Maybe it was a corrupt file somewhere in the system or something that Windows 10 broke in one of its many not so good "updates"
Womdows has broken more than a few things in the last few forced updates, first my printing, then my networking, it is a crapshoot as to what they will damage with every update the cram down your throat, and Thunderbird was likely one of them
|
||
Comment 6•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 7•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 8•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 9•5 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal to S3.
Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.
|
|
||
Comment 10•5 years ago
|
||
Thanks for the update
Description
•