QMail Link Revoke — Group 6, Code 89

Removes a device from the group, or cancels the group’s open invite for it. The row is deleted outright, so a revoked device comes back only through a fresh Invite and a new code.

LIVE FLEET-WIDE since 1 October 2026

The four device-link commands (86–89) are dispatched on every RAIDA and the inbox rewrite for linked devices is switched on. Verified against the server source and a live probe of the fleet on 6 November 2026. The link registry is local to each RAIDA: a client pairs its devices on the beacon RAIDA(s) it actually polls.

Quick reference

Command Group6 (QMail)
Command Code89 (0x59)
Server functioncmd_qmail_link_revoke in cmd_qmail.c
Body layout48-byte QMail preamble + payload (5) + terminator (2) = 55 bytes
TransportUDP or TCP
EncryptionAs for any other QMail command
AuthenticationCaller’s own coin; the caller must be the group admin
Success responseStatus 250, no payload

Device-link model

One user can run QMail on several devices, each holding its own identity coin, so rotating one device’s password (a POWN of that coin) never locks out the others. Devices link under an authority mailbox, which is the public address. A subordinate device’s coin is a device credential only, never a visible identity: while the rewrite is on, a subordinate’s Ping and Peek are served the authority’s inbox, and its Tell is stamped as coming from the authority (the client must already put the authority in the blob’s sender fields, or the Tell is refused with 198). Uploads are not rewritten; objects stay owned by the device coin that uploaded them.

Each group has exactly one admin, normally the authority itself. The admin is the only device that may list (88) or revoke (89). Every device authenticates each of these commands with its own coin in the preamble, exactly like any other QMail command. The registry is kept per RAIDA in that node’s directory database and is never replicated, so a client repeats the pairing on each beacon RAIDA it uses.

Housekeeping the server does on its own

A device idle for more than 24 months is unlinked. An authority idle for more than 24 months with an active subordinate passes admin to the most senior subordinate (succession). Expired invites are purged. These sweeps run at most once a day, triggered by the open DRD sync command (147). Both 24-month windows are deliberately long for the first year of use.

Request body

OffsetSizeFieldDescription
481sub_denDenomination of the device coin to remove.
49–524sub_snSerial number, big-endian.
53–542Terminator3E 3E.

Removes the active device row and/or the open invite for that coin in the caller’s group. Removing a device on one RAIDA does not remove it on the others; repeat the call on every beacon RAIDA.

Status codes

CodeSymbolMeaning
250STATUS_SUCCESSAccepted.
174ERROR_NOT_LINK_ADMINThe caller is not the admin of any group.
173ERROR_LINK_NOT_FOUNDThe named coin is neither a device nor an open invite of the caller’s group.
16ERROR_INVALID_PACKET_LENGTHBody length or terminator wrong.
40ERROR_INVALID_SN_OR_DENOMINATIONA denomination is outside −8…+6, or the request names an impossible relationship (see each command).
8ERROR_COIN_NOT_FOUNDThe preamble coin (or, for Invite, the invitee) is not an issued coin on this RAIDA.
200ERROR_INVALID_ANThe preamble Authenticity Number does not match this RAIDA’s record for the caller’s coin.
194ERROR_FILESYSTEMThe registry database could not be read or written. Transient; retry.
254ERROR_MEMORY_ALLOCServer allocation failure.

Common mistakes

Expecting the revoked device to be locked out of mail

Revocation only ends the link. The device still owns its coin; it just stops being served the authority’s inbox and can no longer send as the authority. A lost device should also be treated as a lost coin.