Phase 8.7 — Moving the platform's email

The provider handling mail for the platform's own domain has been steadily tightening what the free tier allows.

The limits now bite in several directions at once: mailbox storage cut to a single gigabyte, one address only with no aliases, basic security options, and a cap on how many messages can be sent or received in a day.

That last one is the real problem. Notification email, password resets and account verification all share the same daily allowance, so a busy day of alerts can quietly exhaust the budget that a password reset needs. Same as the notification work in 8.6 — the failure is silent, and you find out because something you expected never arrived.

What this phase does

• Move the domain's mail to a provider whose limits match how the platform actually uses email.
• Restore what the current tier removed: room in the mailbox, aliases for separating roles, and proper security controls.
• Separate machine-sent mail from personal mail, so alert volume can never consume the allowance a password reset depends on.

Expect a short cutover while mail routing changes. Addresses do not change, and nothing needs to be done on your side.