Overview of mail flow best practices for Google Workspace — Part 3
Google Workspace gives you the flexibility in determining the best methods on how email is delivered to your organisation’s users. Most organisations want Google Workspace to manage all their mailboxes and filtering, but due to the nature of existing messaging architectures some organisations may require more complex mail flow setups to make sure that they comply with specific regulatory or business needs.
There are typically 3 scenarios of mail to ensure delivery to Inbox or to Internet. Routing may vary depending on the existing infrastructure and the roadmap of the organisation. Choose one of the following methods that suits the organisation or business needs.
- Manage all users and mail flow using Google Workspace — Part1
- Manage mail flow using a third-party mail gateway with Google Workspace — Part2
- Manage mail flow with mailboxes in multiple locations — Google Workspace, SaaS, and on-premises — Part3
This article is about, managing mail flow with mailboxes in multiple locations the 3rd scenario.
Scenario 3: Manage mail flow with mailboxes in multiple locations — Google Workspace, 3rd Party cloud hosted mailing and on-premises.
1. Usually configured when: Organisation is migrating to Google Workspace and wants to keep some mailboxes on an on-premises server or Microsoft 365 and use Google Workspace as a spam filtering solution and would like to send emails from on-premises servers to the internet via Google Workspace. Google Workspace sends and receives all messages.
In the above scenario the MX is pointed to Google Workspace where email processing is done. Data Loss Prevention, Data Retention/Archiving is achieved on Google Workspace.
Incoming
All incoming emails from Internet are routed to Google Workspace. Emails are delivered to mailboxes that are on GWS.
Mails are routed to on-premises or 3rd party cloud hosted mailing solution based on where the mailboxes are hosted.
Outgoing
Internal emails between on-premises, GWS & 3rd Party cloud hosted mailing are exchanged.
Emails to internet from on-premises, GWS & 3rd Party cloud hosted mailing solution are routed via Google Workspace to Internet directly
2. Usually configured when Organisation is migrating to Google Workspace and wants to keep some mailboxes on an on-premises server or 3rd Party hosted mailing and want to use the filtering and compliance solutions on GWS but all outgoing messages need to be routed through on-premises servers
In the above scenario the MX is pointed to Google Workspace where email processing is done. Data Retention/Archiving is achieved on Google Workspace.
Incoming
All incoming emails from Internet are routed to Google Workspace. Emails are delivered to mailboxes that are on GWS.
Mails are routed to on-premises or 3rd party cloud hosted mailing solution, based on where the mailboxes are hosted.
Outgoing
Internal emails between on-premises, GWS & 3rd Party cloud hosted mailing are exchanged.
Only Internet emails are routed to DLP via on-premises server. All outgoing emails to internet are routed from On-Premises server to a 3rd Party DLP where emails are checked and actioned.
Emails from DLP are routed to Internet directly
3. Usually configured when Organisation is migrating to Google Workspace and wants to keep some mailboxes on an on-premises server or 3rd Party hosted mailing and want to use the filtering and compliance solutions that are already configured on-premises but all incoming and outgoing emails are routed through on-premises servers
Incoming
All incoming emails from Internet are routed to email gateway for spam/phish checks.
From Mail Gateway, mails are routed to on-premises server. Emails are delivered to users who are hosted on-premises
Emails are routed to GWS/3rd Party cloud hosted mailing based on mailbox location
Outgoing
Internal emails between on-premises, GWS & 3rd Party cloud hosted mailing are exchanged. Only Internet emails are routed to DLP via on-premises server.
All outgoing emails to internet are routed from On-Premises server to a 3rd Party DLP where emails are checked and actioned.
Emails from DLP are routed to Internet
4. Usually configured when Organisation is migrating mailboxes to Google Workspace and want to keep some mailboxes on an on-premises server or 3rd Party hosted mailing and also want to use the filtering and compliance solutions that are already configured on-premises email environment. All incoming emails are routed through on-premises servers and outgoing via Google Workspace.
Incoming
All incoming emails from Internet are routed to email gateway for spam/phish checks.
From Mail Gateway, mails are routed to on-premises server. Emails are delivered to users who are hosted on-premises
Emails are routed to GWS/3rd Party cloud hosted mailing based on mailbox location
Outgoing
Internal emails between on-premises, GWS & O365 are exchanged.
All outgoing emails to internet from O365 or On-Premises are routed to Internet via GWS
