How to set up business email on your company domain
To use an address such as contacto@oseudominio.pt, you need to manage the domain and subscribe to or configure a compatible mail service. The domain, mailbox and website are separate services even when they appear on the same invoice. Start by knowing who controls access and which messages need retaining. Only then choose mailboxes, change configuration and test communication before publishing the new address.
By the end, you can:
- Distinguish the domain, mailbox and alias
- Prepare the move without deleting existing services
- Check sending, receipt and access recovery
Separate the three services before changing any record
Identify the domain registrar, the service managing DNS and email hosting. They may belong to different companies. Record institutional access and the owner without writing passwords in a shared spreadsheet. Also note where the website is hosted and which services send messages using the domain, such as forms or invoicing.
Zoho Mail’s domain-addition documentation distinguishes control verification from pointing mail records. This separation helps explain the process, but actual values depend on the account and service region. Do not copy generic settings from an old tutorial into a real account. Obtain the provider’s current instructions and confirm the domain’s identity before modifying DNS.
Choose mailboxes and aliases according to the work
A mailbox stores messages and has its own access; an alias may be another address associated with a mailbox, depending on service capabilities. A mailing list or group address distributes messages under different rules. Write down who should receive and reply to each kind of request. Do not create several mailboxes simply because there are several public names if the same person still does the work.
Consider continuity when someone leaves the team. Functional addresses, such as contacto or apoio, must not depend solely on one person’s memory. Define appropriate permissions and avoid indiscriminately sharing the same password. If the service offers delegation or groups, assess those options with the administrator. The aim is to let the company continue replying and know who has access to conversations.
| Need | Option to assess | Test |
|---|---|---|
| Person with their own work | Individual mailbox | Receive and reply with the correct sender |
| Another name for the same destination | Alias | Confirm receipt and reply address |
| Request handled by a team | Compatible group or shared mailbox | Check who receives it and prevents duplicate replies |
| Automatic website message | Authorised sending service | Send, reply and identify the support destination |
Prepare the change with a configuration copy
Before changing records, save an inventory of current DNS and confirm how to restore configuration if needed. Do not delete website records when changing email. The provider will state which records receive mail and which verify or authenticate sending. Different records have different functions, so replacing everything with a reduced configuration may interrupt services still needed.
Zoho’s verification guidance explains that authorised access to the DNS manager is required and the verification value is specific to the configured domain. The change should be applied by someone who understands the inventory. If you lack that access, obtain it through the registrant or provider. Do not bypass permissions or accept supposed verification requesting credentials through an unconfirmed channel.
Treat old messages as part of the project
Changing receipt of new messages does not automatically move history, contacts or calendars. Inventory what the team uses and the available export or migration tools. Confirm formats, limits and permissions before ending the old service. Keep protected copies and restrict access to people who need to carry out the transition.
Define a change window and someone responsible for monitoring mail on both sides while confirming the result. Also test applications on phones and computers. A mailbox accessible in the browser may not be correctly configured in the program the team uses daily. Do not promise a transition without interruptions before knowing the source service, access and volume to transfer.
Fictitious scenario: an architecture practice
A fictitious practice has a personal address on its business cards and receives customer proposals in a mailbox managed by a former provider. When organising the domain, it identifies that the website and email use different suppliers. The team decides to create a functional address for enquiries and individual mailboxes for each person’s work, with defined access and archiving rules.
Before changing its publicity, it sends test messages from two external services, replies and confirms the displayed sender. It checks attachments and form contacts. It discovers an automatic reply still uses the old address and corrects it. It keeps the source available while checking migrated messages. The scenario is fictitious and does not demonstrate any mail provider’s guaranteed capability, price or result.
Test sending, receipt and access recovery
Run separate tests: receive from outside, send externally, reply to a message and use every published alias. Check spam folders and the displayed name and address without concluding that one isolated test guarantees delivery to every recipient. If the website sends messages, test the form and the human reply that follows, because they may use different services and configurations.
Confirm account recovery and authentication factors through official procedures without exposing codes or secrets in a project worksheet. Keep support contacts and renewal responsibilities. A business mailbox helps organise communication when the company controls and can maintain it. A company domain alone does not certify the sender or eliminate fraud attempts or delivery problems.
- The public address receives messages and replies use the intended sender.
- Aliases and groups have documented destinations.
- Necessary history was checked before closing the source.
- The company can manage access and recover accounts through official channels.
Record email operations without exposing secrets
Use the worksheet to organise the service and assign responsibilities. Keep credentials in an appropriate manager with necessary access, and include only the secure management location in this worksheet. If contracting help, define included tasks: configuration, migration, user applications and incident assistance are not necessarily the same work.
Review the inventory when someone joins, leaves or the website changes. A new form may need sending authorisation, and a removed address may remain printed on old materials. Make these changes with a continuity plan and clear team information. Configuration then stops depending on an isolated intervention nobody can explain months later.
Worksheet for your project
Business email inventory Domain and registrant: Registrar, DNS and mail service: Published mailboxes, aliases and groups: Owner of each destination: History, contacts and calendars to transfer: Services sending with the domain: Previous configuration and restoration plan: Sending, receipt and reply tests: Recovery and authentication managed in a secure location: Renewal, support and next review:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
