...
| Icon | Description | Meaning | Timeouts and general behaviour |
|---|---|---|---|
Sending Message | PrivateGSM is actually trying to send the Secure Message to its recipient via PrivateServer | If there is some network issue, then PrivateGSM starts the retry procedure: it tries to send 5 times the message to PrivateServer. If it fails at the fifth try (5 * TLSTimeout = 60 secs), then the message remains in the client queue waiting for one of the following triggers:
If more than 12 hours passed and the message is still in client queue waiting to be sent, then the message expires: a "Send error" notification is fired by PrivateGSM and the message is removed from local queue
| |
 | Message Enqueued | Secure Message has been enqueued in PrivateServer encrypted storage and will be delivered to recipient as soon as possible. | If delivery is not possible because the peer if offline, PrivateServer retries as soon as recipient registers for up to an expiration period (72h), before removing them definitely from the database. |
| Message Delivered | Secure Message has been delivered to recipient's device, who could have read it or not. | None | |
| Error sending Message | This status is a fall back for any other one and it's triggered both by timeouts and error responses. | None |
| Navbar |
|---|