QMail Services (Group 6)
The live V2 messaging surface for uploading message stripes, notifying recipients, polling beacons, and downloading stored content.
Overview
Group 6 in the active reference set is the V2 QMail surface. It covers the message lifecycle end to end: upload data, notify the destination beacon, poll for notifications, inspect pending mail, and download content.
Shared V2 structures
| Structure | Developer note |
|---|---|
| qmail_v2_file_header_t | Fixed metadata header used when storing or reconstructing message/file content. |
| qmail_v2_address_entry_t | Address record used for sender/recipient routing data in V2 payloads. |
| qmail_v2_tell_req_t | Beacon-notification request for announcing pending mail. |
| qmail_upload2_req_t / qmail_download2_req_t | Dedicated upload/download request layouts. GUID identifiers are 16 bytes. |
Live commands
| Code | Name | Purpose |
|---|---|---|
| 70 | upload2 | Upload a stripe or object chunk for a message/file. |
| 71 | tell2 | Notify the recipient-side beacon that mail is waiting. |
| 72 | ping2 | Long-poll the beacon for pending notifications. |
| 73 | peek2 | Quick-check the beacon without long-poll behavior. |
| 74 | download2 | Download stored message or attachment data. |
70 — upload2
upload2 stores one stripe or content fragment under a message/file GUID. It is the write-side entry point before a message can be announced to the recipient.
| Request body element | Developer note |
|---|---|
| Message or file GUID | 16-byte identifier used to bind uploaded stripes to one logical object. |
| V2 file header | Carries the metadata needed to reassemble the uploaded content later. |
| Stripe or chunk payload | Opaque content fragment stored by the RAIDA for later download. |
71 — tell2
tell2 submits the delivery notice to the recipient-side beacon. Use it after the upload phase succeeds.
Operational sequence
The V2 flow is upload first, notify second. A successful tell2 does not replace the need for the uploaded content to already exist under the announced GUID.
72 — ping2
ping2 is the long-poll read path for beacon notifications. It is appropriate when the client wants near-real-time discovery of incoming mail.
Use this command when your client can tolerate waiting for pending notifications to arrive instead of requiring an immediate snapshot.
73 — peek2
peek2 is the fast inspection variant. Use it when the client wants an immediate snapshot of pending notifications without waiting for a long-poll window.
Unlike ping2, this is the non-blocking inspection path.
74 — download2
download2 fetches a stored stripe or object chunk so the client can reassemble the message, metadata, or attachment being retrieved.
| Request/response element | Developer note |
|---|---|
| Request GUID | Identifies the stored message or attachment being fetched. |
| Returned bytes | Opaque chunk content. Reassembly rules come from the V2 file header and higher-level client logic. |
Live surface note
This page intentionally documents only the audited V2 command set 70-74.