A mail app must reliably attempt to fetch mail as instructed, and when that is not possible, it must inform the user of a problem. I know it's not intentional, but when an application does not fulfil its singular main purpose, that application is useless. Thunderbird is an eldritch behemoth of complexity second only to Firefox itself, and it's collapsing under its own weight. That's insane, all those resources to try to open a network connection and transfer a few kilobytes of data. Whilst this was happening, TB was using 50% CPU of one core on a beefy processor. Yes, I do have fully working IPv6 on this machine. Restarting TB did not help, but setting 6 to true did. The user is left with an outdated mailbox unless they notice the tiny unmoving progress bar and can figure out what it means. No indication of a problem, no error messages, nothing. It starts the process but gets stuck with a pulsing blue progress bar in the status bar. Today I discovered another problem fetching mail from an POP3 account. A restart was necessary to get TB to start fetching properly again. During this time I accumulated two weeks worth of missed mail and appointments! TB returned no errors, just pretended to fetch mail. Even Right-click->Get Messages returned seemingly empty-handed. At some point TB silently stopped doing so. I have multiple POP3 accounts set up to fetch minutely. Been using it for a decade now and v102 looked new and nice at first, but fatal bugs kept piling up since.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |