Thunderbird loops on some internal discrepancy while not really fetching incoming messages or just a random-ish subset.
I initially thought it was a problem of me having … (read more)
Thunderbird loops on some internal discrepancy while not really fetching incoming messages or just a random-ish subset.
I initially thought it was a problem of me having way too much mail in local mailboxes, but it appears that it happens on low volumes as well.
I run Thunderbird on OpenBSD/amd64 (recent snapshots) under xfce. My wife (the lower volume user) runs Thunderbird on Ubuntu 22.04 LTS.
The problem is, Thunderbird is "processing" for days on end, fetching (via pop3) what appears to be only a subset of messages (sometimes only a single one, over and over) from the mail server.
I have been observing this behavior for years, but always put it down to me running -current and only achieving a not frequently coredumping Thunderbird after cranking up stacksize in /etc/login.conf. Now it turns out that this is not OpenBSD or -current specific.
It turns out that the lower volume user, on Ubuntu Linux, is now seeing the same behavior, with the odd result that a message that was sent to us both last Monday evening (today is Thursday) has not yet been fetched by her Thunderbird while the program keeps fetching over and over a message from the local newspaper sent and previously received in April of last year.
The problem looks to be somewhat related to fetching large-ish numbers of messages. My last attempt here had Thunderbird report it downloaded 6 of 709 messages, it then proceeded to move some of them from Inbox to another folder according to a filter, and after some tens of seconds the bottom of the window displays "Downloading message 9 of 702", seemingly stuck there.
Then again, the accumulation of unfetched messages is in large part due to Thunderbird only seeing to itself for hours and days on end while messages keep turning up on the mail server.
Please let us know any debugging steps that can be taken at our end in order to fix this.