Rasel MailExpiry, exhausted quota and downgrades: what happens?
Current resource, sharing and sending behavior without assumed deletion or automatic renewal.
Editorial update: October 30, 2026In this guide
Term and manual renewal
The paid term ends at the displayed date. This release has no automatic payment collection; renewal requires a request and payment confirmation. Approving the same selection before expiry extends the term; approving different resources schedules them for its end. Server time is authoritative, not necessarily midnight on your phone.
After paid access expires
| Area | Current behavior |
|---|---|
| Effective plan | Without a current paid or effective scheduled term, free entitlements apply. |
| Existing mail and mailboxes | Expiry does not automatically delete existing messages or mailboxes. |
| New resources | Must fit current limits; retained excess resources do not create extra free capacity. |
| Team and OAuth | Shared and external read access need an eligible owner plan and can be refused after expiry. |
| Custom-domain sending | Workspace and website-API custom-domain sending need the relevant paid entitlement. |
Downgrades and full storage
A reduction below reserved resources is not approved. Reducing a mailbox allocation requires its contents to fit and valid mail-server usage measurements. The system does not empty mail to force a smaller plan. Review allocations, mailboxes, aliases and domains before requesting a downgrade.
Website sending has a separate term
Website quota is purchased separately but still requires a paid base plan at use time. Each recipient counts. Packs added in the same period expire at that period’s end, with no rollover. A 402 needs current-quota checks; a 429 concerns request rate. queued mail can fail if its period expires before submission; accepted and unknown are not automatically safe to resend.