When a domain uses an external mailbox provider, configure both its public MX records and Webuzo local delivery behaviour. Otherwise messages generated by a website on the same server may still be delivered to an unintended local mailbox.
IN THIS ARTICLE
What you need before you begin
Obtain the exact MX, verification, SPF and DKIM instructions from the chosen mail provider. Inventory existing local mailboxes and preserve their contents before any migration. Confirm the authoritative DNS provider and the planned time for the mail cutover.
01 Use an external mail provider with a Webuzo domain
- Create and test destination mailboxes with the external provider before changing delivery. Plan transfer of old mail separately from DNS configuration.
- Publish the provider required MX records at the authoritative zone. Remove conflicting obsolete MX entries only after confirming the intended replacement.
- Open Webuzo end-user Email > Email Router and select the exact domain. Change its routing from the local server to the appropriate remote-mail option. Administrators can manage the same intent through Email Routing Configuration.
- Update SPF, DKIM and DMARC according to actual sending services. Keep one coherent SPF policy rather than adding multiple SPF records for different senders.
- Configure website forms and applications to submit through an authorized mail service. Public MX records control incoming delivery and do not automatically configure application SMTP.
- Keep the former mail service available for the planned overlap and reconcile messages that arrived during cached MX traffic.
Will MX changes move old messages?
No. MX changes influence future routing after caches refresh. Existing mail remains at its current storage location until you migrate or export it separately.
Test sending and receiving
Send to the domain from an external mailbox and from a website or account on the Webuzo server. Both should reach the external destination. Reply back, inspect headers and check that local queues are not retaining messages for the old path.
Troubleshoot unexpected results
If only same-server messages fail, inspect Email Router and application SMTP settings. If external senders fail, inspect authoritative MX, destination provisioning and recipient errors. Do not delete local mailbox data until migration and retention checks are complete.