1792788 - After getting new messages on startup, Thunderbird does not recheck every 10 minutes (IMAP), nor when manually selecting get messages

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[Hollo]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

1. Set up 2 IMAP accounts and tick "Check for new messages every 10 minues" checkbox.
2. Leave TB running.

Actual results:

Account 1: receive new messages on startup. After that, they will be never checked automatically, only upon manual click/keybind.
Account 2: receive new messages on startup. After that, never, not even when issuing manual check.

Expected results:

New messages should be checked for every 10 minutes automatically, without manually ordering it.

This feature was working fine in 91.10.0, both accounts were receiving messages every 10 minutes.
In 102.2.2, account1 was receiving new messages automatically for some time after startup and then stopped doing it, account2 was receiving them only on startup and only upon manual check afterwards.
102.3.0 produces the behavior described above.
Tried repairing every folder. No change.

Comment 1

[Wayne Mery (:wsmwk)]

Please see https://support.mozilla.org/en-US/kb/cannot-receive-messages

Comment 2

[Hollo]

Sorry I have not included that information. I have checked all those and several others I've found in other threads.
All my settings are correct (if they weren't, I wouldn't receive messages at startup either).
Web interface for both accounts are working and receiving/showing all new messages correctly.

Comment 3

[Thomas D. (:thomas8)]

• Hello Hollo (reporter), does this involve your computer going to sleep mode?
• If yes, problem also occurs without sleep mode in between?

Comment 4

[Hollo]

Hi Thomas, thanks for picking this up!
No, my computer never goes to sleep (the setting is disabled). I only have screensaver turned on and monitor sleep (the latter triggers like once a week) but this happens even if the screensaver is not triggered.

Comment 5

[Hollo]

Also the biggest issue here is that not only the periodic check fails on one of the accounts but that one won't react to manual rechecks either, it will only sync at startup and after that, if I want to check new messages, I have to restart TB every time.

Comment 6

[Magnus Melin [:mkmelin]]

Try Help | Troubleshoot mode. Also check the Error Console (Ctrl+Shift+J).

Comment 7

[Hollo]

Error console output on startup (warnings and errors only):
09:32:24.244 services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource.
09:32:24.604 : Component returned failure code: 0x80550013 [nsIMsgPluggableStore.createFolder]
09:36:33.782 Unknown property '-moz-border-radius'. Declaration dropped.

Will try to run it in Troubleshoot mode for a couple of days.

What should I look for in that mode (besides the console log) if the problem is still there?
Would an IMAP log be more helpful?

Comment 8

[Magnus Melin [:mkmelin]]

Just check if it works in troubleshoot mode or not.

Can you paste all of the nsIMsgPluggableStore.createFolder failure stack?

Comment 9

[Hollo]

09:32:24.604 : Component returned failure code: 0x80550013 [nsIMsgPluggableStore.createFolder] Pop3IncomingServer.jsm:135
createDefaultMailboxes resource:///modules/Pop3IncomingServer.jsm:135
discoverFolders resource:///modules/MailUtils.jsm:64
generateMap chrome://messenger/content/folderPane.js:2038
_rebuild chrome://messenger/content/folderPane.js:1892
load chrome://messenger/content/folderPane.js:195
InterpretGeneratorResume self-hosted:1422
AsyncFunctionNext self-hosted:632

Meanwhile getting some addon related logs, e.g.:
12:50:32.972 1664535032972 addons.xpi-utils WARN Add-on systray-x@Ximi1970 is not compatible with application version.
12:50:32.973 1664535032973 addons.xpi-utils WARN Add-on {9c21158b-2c76-4d0a-980a-c51fc9cefaa7} is not compatible with application version.

(And a lot more, with warious messages, while all addons are disabled.)

Comment 10

[Magnus Melin [:mkmelin]]

So https://hg.mozilla.org/releases/comm-esr102/file/tip/mailnews/local/src/Pop3IncomingServer.jsm#l135 -> NS_MSG_FOLDER_EXISTS

Are you sure those are imap accounts?

Comment 11

[Hollo]

Yeah I saw that too and I am 100% sure the affected accounts are both IMAP.
There is a POP3 account configured as well, I guess that's where that printout comes from.

Comment 12

[Hollo]

Update:
Account 1: seems to work in the last few days without changing anything, could be some server side problem, will keep monitoring.
Account 2: server was unreachable for a week so I haven't had a chance to test but today it's back and this is what I get when trying to check for new messages:
10:02:31.627 uncaught exception: Object
There is no stack and no other error messages. This is being printed only once, upon the first try of getting new messages after startup, after that nothing happens and the progress bar (bottom right) will get stuck at ~50% forever.

Comment 13

[Hollo]

Tested it in Troubleshoot mode for a day and it was working for a little while (maybe a few hours) but then got to the same state, not even trying to get new messages when pressing the button and status bar stuck (now at 100%).
Different error message this time, not sure if related:
21:21:29.339 2147942487 5 ContentDispatchChooser.jsm:291
handleURI Choo
openLinkExternally chrome://communicator/content/utilityOverlay.js:468
contentAreaClick chrome://communicator/content/contentAreaClick.js:226
onclick chrome://messenger/content/messenger.xhtml:1

Comment 14

[Hollo]

One more day of testing in Troubleshoot mode.
Acc2 stopped responding to "Get Messages" command, status bar stuck.
Error console completely empty.

Comment 15

[Hollo]

Is there something I can do to trace this bug or some workaround I can try?
It's getting unbearable since this is the literal most basic functionality that's broken.

Comment 16

[Wayne Mery (:wsmwk)]

Are you still seeing this in version 115?

Comment 17

[sisifosplight]

No, the problem already disappeared shortly after the bug was reported.

Comment 18

[Wayne Mery (:wsmwk)]

(In reply to sisifosplight from comment #17)

No, the problem already disappeared shortly after the bug was reported.

So this went away for you almost two years ago?

Comment 19

[Hollo]

For me, it never went away. Will test with version 115.

Comment 20

[sisifosplight]

Yes, indeed. Actually I remember the problem disappeared after uninstalling TB, cleaning up all the leftovers on the Windows system disk and in the Windows registry, and then installing it from scratch again. A lot of work, but it helped ;-)

Comment 21

[Phoenix]

(In reply to Hollo from comment #19)

For me, it never went away. Will test with version 115.

And the result is? :)

Comment 22

[Hollo]

(In reply to Phoenix from comment #21)

(In reply to Hollo from comment #19)

For me, it never went away. Will test with version 115.

And the result is? :)

I don't seem to have this problem anymore with 115.11.1.

Comment 23

[Phoenix]

Cool, nice to hear, closing then :)