The one where mail can finally go somewhere. Skim has happily read your folders since forever, but putting a message into one? Not supported. Slightly awkward for an email client. Fixed.

New

• Move to folder new toolbar button, or V / Ctrl+K for a palette-style picker. Type, hit Enter, done.

• Create a folder while moving no folder named "Taxes" yet? Type it, it gets created and the mail lands in it. Works offline too, because of course the move rides the op queue like everything else. And no, Enter won't accidentally invent a folder while a real match is sitting right there that row never steals the highlight.

• Rename & delete your own folders a small button next to the list header. Your folders only; Skim won't let you rename Gmail's Inbox, because that ends badly.

• Deleting is only offered on empty folders IMAP DELETE takes everything inside with it on basically every provider except Gmail, and there's no undo. So we re-ask the server right before running it, in case mail snuck in between your click and the queue draining. Paranoid? Yes. Correct? Also yes.

The one where Skim finally admits your mailbox didn't begin 500 emails ago. Turns out there was mail before that. Who knew.

New

• Your whole mail history, actually downloaded. Until now the first sync grabbed the newest window (500 in the inbox, 200 elsewhere) and then only ever looked forward. Everything older sat on the server, invisible to search and to the assistant, forever. Skim now quietly walks each folder backwards in the background a bounded slice per pass, resuming exactly where it left off across restarts until it hits message number one. New mail never waits in line behind it.

• Install it the nerdy way. This repo now doubles as a Scoop bucket, updated straight from the release pipeline. (A WinGet manifest is wired up too, but it's still waiting in line at microsoft/winget-pkgs. Patience. )

Fixed

The one where Skim finally learns that not every mail server hides behind implicit TLS. Turns out port 143 has feelings too.

Fixed

• IMAP on port 143 now just works. Type 143 and Skim used to fire a TLS handshake straight at the server's plaintext greeting, then fall over with the delightfully unreadable received corrupt message of type InvalidContentType. Now Skim reads the port and picks the transport for you: 143 STARTTLS upgrade (connect in the clear, read the greeting, STARTTLS, then handshake credentials never leave before the tunnel's up), everything else implicit TLS, exactly as before. No toggle, no new setting, no "which encryption mode?" quiz. The client decides, because that's the whole point. (#19)

• Errors that speak human, not TLS. Server won't do encryption on 143? "Try IMAP port 993." Plaintext greeting where a secure port was expected? "This doesn't look like a TLS port." Localized in all 11 languages and real cert/timeout problems keep their own codes, so a genuine TLS failure never gets mislabeled as "wrong port."

I built Skim for myself. And it works better that any other email client for me.

But you're not me, right?