Held until the other radio says "got it"
Every direct message you send is kept on your own node until the recipient's radio confirms it arrived. If it doesn't arrive, your node keeps trying, on its own, for 2 days by default (you can choose 5 or 15 days, or turn holding off).
The life of a message
Your phone doesn't need to stay connected. The node does all of this by itself.
A message that never gets a "got it" is dropped when the hold time runs out: 2 days unless you change it on the HOLD page.
When it tries again
A schedule that slows down over time, plus instant tries whenever delivery looks possible. One message per person goes at a time, oldest first.
The schedule
| Since last reachable | Tries |
|---|---|
| First 12 hours | about 5 min, then 15 min, then every 30 min |
| 12 hours to 2 days | every 3 hours |
| After 2 days | once a day |
| Out of coverage | at most every 2 hours |
Instant tries
| When | What happens |
|---|---|
| Person heard | Anything from them (advert, message, route update): their mail goes within seconds |
| Repeater in range | A repeater is heard directly: everyone gets one extra try, at most every 5 min |
| Back in coverage | Nothing heard for 20 min, then the mesh again: everyone is tried |
| Restart or wake | Everyone is tried within about a minute |
| Send now | Press the button: one extra try per person |
Extra tries never reset the schedule. If one fails, the next scheduled try stays where it was.
The "got it"
Every MeshCore radio sends a small confirmation (an ACK) the moment it receives a direct message. It's the same thing that turns the app's tick to Delivered. BoxOnPost waits for it, so the person you're messaging needs nothing special.
BoxOnPost resends your exact message, with its original time, so the other person sees when you really wrote it, and the confirmation matches. (From version 0.6, a late copy ends with ~BOP; see below.)
Its retries always go out by flood, passed on by every repeater, so the "got it" can find its way back even when you or they have moved.
"Delivered" means it reached their radio, not that they've read it.
Your inbox is protected too
Messages that arrive while your phone is away are saved to flash on a BoxOnPost node, so a dead battery or restart doesn't lose them.
If the inbox is ever completely full (256 messages), a BoxOnPost node won't say "got it" for a message it can't store. The sender sees Failed instead of a false Delivered, and if they run BoxOnPost, their node tries again later.
Two BoxOnPost radios
When both ends run BoxOnPost, a tiny ping goes first to find a fresh route, and a node coming back into coverage announces "I'm back" so mail waiting for it is delivered right away.
What's new
You choose how long messages are held: off, 2, 5 or 15 days, right on the radio. Since 0.7: BoxOnPost runs on MeshCore 1.18, the ThinkNode M1 has joined the Heltec radios, and every radio starts up with BoxOnPost on its screen.
The new HOLD page
One page sets how long a message is held without a “got it”: Off, 2, 5 or 15 days. New installs start at 2 days; radios updated from 0.7.x keep 5 days. The Pause, Sleep and Wake time pages are gone: HOLD Off pauses retries, and messages are still kept.
Built on MeshCore 1.18
Version 0.7 moved BoxOnPost onto MeshCore 1.18: security and stability fixes, a clock that survives restarts, and Wi-Fi alongside Bluetooth on Heltec radios. Everything BoxOnPost does works the same. Heltec V3 and V4 R8 hold 50 messages to leave memory for Wi-Fi.
ThinkNode M1, two ways
The e-ink M1 is ready to download, in two versions: Screen stays on keeps your name, messages and status readable when the backlight turns off; Stock blanks the screen like standard MeshCore. Text stays sharp and black, with no ghosting.
BoxOnPost on the start-up screen
Every radio now starts up showing BoxOnPost, “for MeshCore”, and the version, so you can see at a glance what's installed.
Three features that make held messages easier to follow, on both ends.
No double messages
If the "got it" is lost on the way back, the sender's mailbox sends the message again. A BoxOnPost radio remembers what it has already received: the repeat isn't shown twice, but it still answers "got it", so the sender stops trying. Works with the phone app closed. Between BoxOnPost radios only.
"~BOP" on late deliveries
A message the mailbox delivered late ends with ~BOP, so the reader knows it was held for them and wasn't just written. Messages that go straight through don't get it. At the length limit, the tag is left off rather than cutting your words.
The BoxOnPost Status channel
Your radio adds a private channel to the app with one-line notes, like ✓ Delivered to Don: "Are you coming tonight…" (2h late), or a warning if the mailbox was full or the hold time ran out. The app's "failed" can also switch to delivered. The channel lives only on your radio, nothing is sent over the air on it, it uses an empty slot, and you can rename or mute it.
Get version 0.7.3 on the Firmware page. More in the Guide: new in 0.7.3, 0.7.2, 0.7.1, 0.7 and 0.6.
Limits
| Kept for | 2 days without a "got it" (choose Off, 2, 5 or 15 days on the HOLD page), then dropped |
| Per person | The newest 10; an 11th pushes out the oldest (shown on screen) |
| Total held | 100 messages on the Heltec V4, 50 on the Heltec V4 R8 and V3, 64 on the ThinkNode M2, M5, M7, M9, 48 on the Heltec T114 and ThinkNode M1, M3 |
| Mailbox full | New messages are still sent, just not held. Other people's held mail is never dropped to make room |
| Channels | Only direct messages are held. Channel messages have no "got it" in MeshCore |
| Privacy | Held and uncollected messages are stored as plain text on the radio itself |