OptMsg Release Notes v1.1.2

OptMsg v1.1.2 is our reliability release. We went after the things you have to be able to trust without thinking about them: that a message you sent actually went, that your mailbox shows you the truth, and that your bill matches your plan. Here’s what changed.

Send with confidence

The biggest work in this release is in the send path. Previously, in some situations a message could be marked as Sent before delivery had truly been confirmed. That’s now been reworked end to end.

• “Sent” means sent. A message is only marked Sent once delivery has actually been confirmed — not before.
• Oversize messages tell you honestly. If a message is too large to deliver, you’ll be told at the time, rather than seeing it sit in Sent having never arrived.
• Clear attachment limits. Attachment size limits now reflect what can genuinely be delivered, with a larger allowance for messages that stay inside OptMsg.
• Retries do the right thing. If you edit and resend a message that already went out, it’s treated as a new message instead of quietly altering the original.
• Everyone on a mixed message can reply-all. When a message goes to both OptMsg and outside addresses, the recipient list now stays intact for everyone.
• An Outbox you can see. Messages that need another attempt are visible and retryable, instead of disappearing.

A mailbox that keeps its word

• Unread counts match what’s in the folder. The badge and the list now agree.
• The unread filter behaves. Turning it on no longer marks messages read, hides the one you’re reading, or keeps already-read messages pinned to the list.
• Reading on a phone doesn’t skip ahead. Moving through your inbox no longer silently marks the next message read.
• Messages to yourself behave normally. No more duplicate copies, and they stay where you’d expect in Sent.
• Folders load, or tell you why. A failed first load now offers a retry instead of spinning forever.
• Restoring from Trash just works, without a false error message.
• Images inside messages display properly, including messages received earlier that were affected — those have been repaired.

Billing that adds up

• Upgrades charge correctly. Moving from the free Reader plan to a paid plan now bills properly.
• Your transaction history is complete. Reactivations, refunds, cancellations and plan changes all appear, with the right amounts.
• Adding a card doesn’t change your billing card unless you ask it to.
• A payment problem doesn’t cut you off immediately. If a renewal fails, you keep full access while your bank retries — and you’ll hear from us before anything changes.
• Clearer plan information. The Reader plan’s description and the days-remaining count are now accurate, and one-time plans no longer claim to renew.

Getting started, without dead ends

• You can always finish signing up. Stepping away part-way through — including at the payment step — no longer locks you out of the account you just created.
• Pick up where you left off. An incomplete sign-up now resumes reliably, rather than expiring quietly.
• Choosing the free plan says the right thing. You’re no longer told you purchased something when you didn’t.
• A redesigned card form. Adding or changing a card now happens in-page, scrolls properly on small screens, and accepts input reliably.
• The Enter key submits the login form — a small thing, on the very first screen.
• Passkeys on more than one device. You can now add a passkey on a second device.

Privacy and account safety

• Sender addresses are shown accurately. We now read the real sending address rather than the display name attached to it, which makes messages that imitate someone else easier to spot.
• Images in messages are more tightly scoped, so they can’t be used to reach content they shouldn’t.

Accessibility

• Screen-reader support on tablets. The main navigation is now reachable on iPad in landscape.
• Form fields announce themselves properly across sign-up, profile and compose.
• Larger, more consistent tap targets on the controls that were hardest to hit.
• Phone-number autofill works on iOS.

Steadier under the hood

A batch of resilience work you shouldn’t notice — which is the point. Brief database interruptions no longer affect the service beyond the moment they happen, busy periods return a clear “try again shortly” instead of a generic error, and an expired session now prompts a clean sign-in rather than looping.

As always, thanks for the reports — a good number of the fixes above came directly from members telling us something looked wrong.