Some messages matter, just not right now. A budget draft can wait until Friday morning. A travel confirmation can wait until the evening you pack. Most email tools handle snooze by moving messages into another folder, slapping on a provider label, or depending on a server feature that only one mailbox type supports.

Orvia Snooze takes a quieter path. It records a local schedule on your Mac. The message keeps its real folder, date, star, labels, and thread. Inbox simply stops showing it until the time you chose. When it comes back, it reappears as important, unread, and pinned until you open it.

Common approach

  1. Move the message to another folder
  2. Or rely on a provider-only snooze API
  3. Hope every mailbox behaves the same
  4. Risk losing track of the original place
→

Orvia Snooze

  1. Keep the message where the server already has it
  2. Hide it from ordinary Inbox views
  3. Return it at your chosen time
  4. Mark it important, unread, and pinned until opened

Try it once

One button to schedule, one moment waiting, then the mail returns. This demo does not contact a mail server.

Demo · Snooze

In the app: toolbar Snooze → header clock opens a temporary list → due mail returns important, unread, and pinned.

How to use it in Orvia

While it waits, open the temporary Snoozed list from the dynamic clock in the list header to reschedule, return now, or undo. No permanent sidebar tab is required.

What “returned” means

When the time is due, the message reappears in Inbox with three temporary cues:

  • Important: it matches the high-priority style you already use.
  • Unread: even if you had read it, it asks for attention again.
  • Pinned until opened: opening clears the emphasis without moving the message again.

The original server date does not change. Ordering uses a stable local return time.

Why local presentation

Mailboxes differ. Some providers offer native snooze; many do not. Labels and folder moves create churn that is hard to reverse cleanly across Outlook, QQ, 163, custom IMAP, and Gmail. A local record gives the same behavior on every account Orvia supports, with zero server folder thrash.

That choice has a clear boundary: Snooze does not sync across devices by itself. Another Mac or iPhone does not automatically inherit the schedule unless a future shared-state design is added. On this Mac, the schedule is complete—inspect, reschedule, return, undo—without inventing another provider dialect.

Limits worth knowing

  • Snooze is local presentation state, not a server move and not a provider-native API wrapper.
  • If the local identity of a message cannot be rebound safely after a sync replacement, Orvia cancels the schedule rather than guessing from subject or sender.
  • Search and Starred can still surface scheduled mail; they may show that it is due later.
  • Notifications help, but due reconciliation does not depend on a notification successfully delivering.

Snooze ships with the quieter mail work in recent releases—including Classic 0.5.3. See the changelog for the exact channel you use, and download when you are ready to try it on real mail.