Closed Bug 1912373 Opened 2 years ago Closed 2 years ago

Thunderbird "Get Messages" always returns "There are no new messages on the server" in status bar

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

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

Steps to reproduce:

I recently started using Thunderbird. I am running on Windows 10, with Thunderbird version 128.1.0esr (64-bit). I have only one email account: I am connected to ProtonMail via IMAP.

I tap the "Get Messages" icon.

Actual results:

"No new messages on server" flashes quickly in the status bar (almost too quickly to see). This ALWAYS happens, despite the facts that:

  • TBird SHOWS unread messages in the IMAP Inbox on the ProtonMail server.
  • TBird shows notifications when new messages arrive in the IMAP inbox.
  • Clicking on a new message notification allows me to read the message within TBird (but does not download it to my PC).

Expected results:

Should download messages, and remove them from the server. Or do I misunderstand what "Get Messages" means??

Should download messages, and remove them from the server. Or do I misunderstand what "Get Messages" means??

Get messages will just check if there are NEW messages on the server. It won't remove them for IMAP.
NEW messages are not the same as unread; it means messages Thunderbird didn't know about before.

Blocks: tb128found

Thanks for reporting this Chris and thanks for the explanation Magnus. I guess to add to the response, "Get Messages" means "Check for new messages on the server" and could perhaps do with a review of the icon used.

As the behaviour described is by design and aligns with the intended functionality of the system, I’m marking this as RESOLVED/INVALID.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.