Sent but not saved The mail

Sent but not saved The mail server accepts the email. The app fails to save it.

Now a “Try again” button could send it twice.

That’s the failure case behind one of today’s ReachLog updates.

In my React/Next.js app, I added “Save to history” for emails whose SMTP acceptance is recorded but whose message is missing from local history. It restores the original sender, recipient, thread and send date without sending another email or scheduling another follow-up.

The button is the visible part. Underneath it, the recovery has to respect everything that happened afterwards:

• Repeating recovery must not create another history entry. • Recovering an older email must preserve newer replies, drafts and follow-ups. • Switching to another target for the same recipient must not bypass the unresolved-send block.

The recovered message and its audit event are saved together. The interface also distinguishes a failed send from an accepted email that still needs its local record repaired.

This is the kind of application work I enjoy: connecting what the interface says to what the integration and database actually know.

A useful error state should tell someone what happened, what remains unresolved, and what their next click will do.