v3.5.7

MailFlow v3.5.7

One deep fix for connection-limited mail providers, plus two merged community contributions. Thanks to @amalroymj, whose four rounds of precise testing shaped the Yahoo work, and to @Hui-161 and @salmonumbrella for the features.

Fixed: living politely under a provider's session limit (Yahoo)

• Marking mail read no longer costs a login (#474). Yahoo limits how many IMAP sessions an account may hold at once. Flag changes (read, star) in the inbox now run over the connection MailFlow already keeps open, the way Thunderbird does it, instead of opening a new login the provider may refuse. An open tab retrying a single mark-read could previously keep the account in Yahoo's bad graces indefinitely.
• Recovery escalates honestly. A successful login no longer resets the retry backoff; a successful sync does. Yahoo accepts logins while starving the session afterwards, which kept MailFlow retrying every 30 seconds forever instead of backing off long enough for the provider to recover.
• Flag changes for one account are applied strictly in order, so a slow earlier change can never overwrite a newer one.

Added: community contributions

• Keyboard triage and mailbox navigation (#483, @salmonumbrella): j/k selection, star/read/archive/reply keys, two-key sequences like gi, Ctrl+1..9 mailbox switching, a ? help overlay, and rebindable keys in Settings. Shortcuts never fire while you are typing.
• Alias-forwarding unwrap for 33Mail (#475/#488, @Hui-161): mail forwarded through 33Mail now shows the real sender, classifies by the original message's own headers instead of the forwarder's, and records the receiving alias so replies can use it. Only genuine 33Mail wrappers are unwrapped; imitation display names are ignored.

Upgrading

ghcr.io/maathimself/mailflow-backend:latest points at 3.5.7, published for amd64 and arm64. No migration is required beyond the automatic one for the 33Mail sender fields.