Google Workspace Split Delivery Configuration
The general steps for setting up split delivery using Google Workspace as the primary server are as follows. You must be a Google Workspace administrator to perform these steps.
1. Configure DNS (MX Records)
Ensure your domain's MX records are configured to point to Google's mail servers. This makes Google Workspace the primary service that receives all incoming mail for your domain first.
One MX record pointing to smtp.google.com
2. Add the Non-Gmail Email Server as a Mail Route
You need to define your second email system (e.g., your old on-premise server) as a routable host in Google Workspace.
Sign in to your Google Admin console.
Go to Apps > Google Workspace > Gmail > Hosts (or Add Route).
Add a new route for your non-Gmail server.
Give it a descriptive Name (e.g., "Legacy Mail Server").
Enter the hostname or IP address of your non-Gmail server.
Specify the correct port (typically 25).
Save the new route.
I pointed to the mail.domain.com (the legacy server).
3. Set Up the Split Delivery Routing Rule
You'll create a routing rule that tells Google Workspace to check if a user exists in Gmail, and if not, forward the email to your secondary server.
In the Google Admin console, go to Apps > Google Workspace > Gmail > Routing.
Scroll to the Routing section and Configure or Add Another Rule.
In the Add setting box:
Provide a Name for the rule (e.g., "Split Delivery to Legacy Server").
Under Email messages to affect, check the Inbound box (and optionally Internal-receiving).
Under For above type of messages, do the following:
Select Modify message from the menu.
Check the Change route box.
Under Change route, select the non-Gmail server you added in Step 2.
Scroll down and click Show options.
Under Account types to affect, check the Unrecognized/Catch-all box and ensure Users and Groups boxes are unchecked.
This is the key step: It directs mail for any email address not found in your Google Workspace user list to be sent to your legacy server.
Click Save.
Another thing, you need to setup the email routing to the remote mail exchanger on cPanel.
No hay comentarios:
Publicar un comentario