To use a business address such as sales@example.co.ug, you need control of the domain, an email service and the correct DNS records. You can keep your existing website where it is while changing only the records needed for email.
Choose capacity and features first
Count the people who need their own mailbox and measure existing mail storage before choosing a plan. An alias or forwarder is not necessarily a separate mailbox. Bulamu Mail Launch, Grow and Scale offer 10, 25 and 50 mailboxes respectively, with total storage pools of 10, 25 and 50 GB. Space is shared across the plan, not allocated in full to each mailbox.
Check current Mail prices and limits. If you need Gmail with business administration and Google's collaboration tools, request an edition-specific Google Workspace quote. Confirm user count, commitment, renewal, setup and migration scope before accepting it.
Prepare access without changing live mail yet
- Identify the authoritative DNS provider. It may differ from the registrar or website host.
- Save the existing DNS records and list every service that sends mail for the domain, including forms and newsletters.
- Create the required destination mailboxes, aliases and forwarding rules.
- If old mail exists, agree its migration and verification before changing MX records.
Set up mail routing and authentication
MX records tell other servers where to deliver incoming mail. Use the exact records supplied for the selected service; do not mix old and new providers' records as an improvised backup. For Google Workspace, follow the records shown by Google for your setup.
SPF identifies authorised sending services. Combine the authorised senders into one valid SPF record for the hostname rather than creating competing SPF records. DKIM adds a domain signature to outgoing mail. Publish the provider-generated public record and enable signing as instructed; never publish a private key.
DMARC checks alignment with the visible From domain and describes how to handle failures. Start by understanding reports and verifying all legitimate senders before enforcing a stricter policy. Authentication helps receivers assess mail but does not guarantee inbox placement.
For cPanel, use Email Deliverability to inspect the suggested records. If DNS is hosted elsewhere, publish them there. Google's records apply to Google's service, not automatically to cPanel mail.
Connect devices and test
In cPanel, open Email Accounts → Connect Devices and use that mailbox's secure SSL/TLS settings. Use the full email address as the username. For Workspace, follow the account's Google sign-in and security instructions.
Test inbound and outbound mail with an external address, replies, attachments, aliases and your website's contact form. Review message authentication results and monitor queues or bounces after the DNS change. Keep passwords out of support messages; provide the sender, recipient, time and bounce text when reporting a fault.
Reviewed 3 October 2026. References: cPanel email authentication, secure mail-client setup, Google Workspace MX setup, and Google SPF setup.