# L4 0.0.7

> Connecting a mail domain now happens inside the Server, with no steps in the Cloudflare dashboard and no sender address to find. This release has no database migration. Take the pre-update backup as usual.

Source: https://llll.gg/changelog/v0.0.7

Connecting a mail domain now happens inside the Server, with no steps in the Cloudflare dashboard and no sender address to find. This release has no database migration. Take the pre-update backup as usual.

## Mail

- **Email Routing turns on by itself.** **Server settings → Mail → Domains → Connect** now does it. The official installer asks for one more Cloudflare permission, Zone settings (write), and you can decline it. Without it, you turn Email Routing on in your Cloudflare dashboard as before.
- **Reset and confirmation emails work once a domain is connected.** They come from `no-reply` at that domain. To use another address, change **Sender address** in **Server settings → Authentication**.
- **A domain that already receives mail elsewhere is left alone.** Connecting it now stops with a clear message that asks for a subdomain, so the mail you already receive keeps arriving.
- **The next step is offered.** After you connect a domain, the form for your first Mailbox opens with that domain selected. A domain that can receive but not send shows **Receives mail, sending is off** and a **Finish connecting** button.

## Server address

- **Choose from your domains.** When the Server keeps Cloudflare access, **Add address** lists the active domains in the account, and you can put a subdomain in front of one.
- **Getting a domain.** If the account has no active domain, Mail and Server address link to Cloudflare to buy one or add one you already own.

## Docs

- [Custom domain](https://llll.gg/docs/cloudflare/custom-domain) now covers getting a domain.
- [Mail on Cloudflare](https://llll.gg/docs/cloudflare/mail) and [Costs and limits](https://llll.gg/docs/cloudflare/costs-and-limits) now say that sending email to anyone outside your Cloudflare account needs the Workers Paid plan, and that a new domain's mail may land in spam at first.
- The Owner and the person who creates a Mailbox get **Manage** automatically; the docs had said otherwise.

## Updating

- **Access kept from an older release does not gain the new permission.** An update from the Server's own settings keeps it. If **Connect** says Cloudflare did not turn on Email Routing, either update through the official installer with **Keep Cloudflare access on this Server** checked, or turn Email Routing on for that domain in your Cloudflare dashboard, then connect again.
- **A domain that is already connected keeps working.** Nothing changes for it. If you already set a sender address, it stays.
- Cloudflare: no resource, binding or Durable Object changes.
- VPS and Docker: redeploy the new image as usual. Mail on these runtimes is set up the same way as before.