# Email hosting or forwarding for your domain?

Canonical URL: https://xuid.ru/blog/domain-email-vs-forwarding/

Language: en

Published: 2026-11-10. Category: Domains.

Choose between email forwarding and a mailbox for your own domain. Understand sending, receiving and access before ordering .RU or .SU email.

An address such as editor@your-domain.ru can lead to an existing inbox or to its own mailbox. The right choice depends on how you want to receive mail and reply to it.

Registering the domain gives you the name. Email service is a separate part of the setup, even when you buy both from the same company.

## Receiving and replying are different requirements

| Option | Useful when | Check before choosing |
| --- | --- | --- |
| Forwarding | You want incoming messages delivered to an inbox you already use | Where replies come from and how the destination handles forwarded mail |
| Hosted mailbox | You want to send and receive as your domain address | Storage, sending allowance, access methods and account recovery |
| Alias | You want another address routed to an existing mailbox | Whether it can also be used as a sender and who can read its mail |

Consider a small publication with editor@ and subscriptions@. One editor may want both addresses in the same mailbox. A larger team may need separate access and a shared process for subscription enquiries. Decide who reads and replies before ordering addresses.

Forwarding alone doesn't establish an outgoing email service for your domain. Cloudflare distinguishes forwarding from sending and receiving through an SMTP provider in its [email-record guidance](https://developers.cloudflare.com/dns/manage-dns-records/how-to/email-records/). Fastmail also explains how forwarding can interact with email authentication in its [domain-hosting guidance](https://www.fastmail.help/hc/en-us/articles/360058753274-Why-should-I-host-my-domain-at-Fastmail).

## Use the access method that suits the team

xUID's [email service](https://xuid.ru/services/smtp/) offers SMTP for outgoing mail, IMAP or POP3 for incoming access, and webmail in a browser. Send the domain and mailbox addresses you need to get current pricing and limits.

Include whether an application will send messages too. A website's password resets and member notifications have different sending patterns from a person answering a few enquiries. Agree the requirements rather than assuming a mailbox includes any volume of automated mail.

You can also use another provider. The [Proton Mail guide](https://xuid.ru/blog/ru-su-proton-mail/) covers connecting your .RU or .SU domain to that service.

## Put the DNS records in the right account

Your email provider supplies the records needed for its service. Add them wherever the domain's DNS zone is managed, which may be separate from the registrar or website host. Follow that provider's current instructions for mail routing and sender authentication.

If you change nameservers, preserve the email records as part of the move. Test receiving and replying with an external address before closing the old service. The [website and email migration checklist](https://xuid.ru/blog/move-website-and-email/) keeps those tasks together.

For a new project, [choose your domain](https://xuid.ru/domains/) first, then send the mailbox names and intended use in your email enquiry. You can price the two services together while keeping their renewal and support details clear.