MailFlow v3.5.4
A follow-up to v3.5.3 for @amalroymj, who tested that release against Yahoo and reported precisely what it did and did not fix.
Fixed: IMAP connections to a provider that is refusing them
-
A provider could keep an account stuck at the shortest retry delay forever (#474). When a mail server accepts your account's main connection while refusing extra ones, MailFlow read the successful connection as the account being healthy and reset its failure count. The backoff restarted at 30 seconds every time instead of climbing, so the server was never given long enough to recover. Refusals on background connections now keep their own count, which only a successful background connection clears.
-
Background body loading could take the whole connection budget. Loading message previews asked for one more connection for every remaining message in the folder, and started again on every folder view. On an account whose provider was refusing, that consumed the connections everything else needed, which is why deleting mail failed at the same time as messages failed to load. It now stops at the first refusal and waits before trying again.
-
Your mail sync is no longer held back by background work. A refused background connection used to be able to pause your account's syncing for minutes at a time, escalating toward hours, even though your account's own login was working. Background work backs off now; your mail keeps flowing. Pressing Reconnect clears both, so it does what it looks like it does.
-
Three more log lines were hiding the reason for a failure. Backfill and the folder checks reported a bare
Command failedinstead of what the server actually said. They now show the server's own explanation and its response code, like the rest of the logs since v3.5.3.
Upgrading
ghcr.io/maathimself/mailflow-backend:latest points at 3.5.4, published for amd64 and arm64.
A note on verification
Nobody on the maintainer side has a Yahoo account. These fixes are verified against the mechanism, the reporter's logs, and the test suite, not against Yahoo itself. If your provider behaves this way, reports are welcome.