Google Workspace Gmail Routing vs Default Routing: Differences, Use Cases, Configuration and Best Practices
Google Workspace gives administrators powerful control over how email enters, leaves, and moves within an organization. Two settings that frequently confuse ...
Google Workspace gives administrators powerful control over how email enters, leaves, and moves within an organization. Two settings that frequently confuse administrators are:
Admin Console → Apps → Google Workspace → Gmail → Routing
and
Admin Console → Apps → Google Workspace → Gmail → Default Routing
At first glance, these settings appear very similar. Both can affect message delivery, recipients, mail servers, and other aspects of Gmail mail flow.
However, they are intended for somewhat different purposes.
A simple way to understand them is:
Default Routing = Define the organization's broad/default mail-delivery behavior.
Routing = Create more specific, conditional, departmental, user-specific, or exception-based mail-flow rules.
Google describes Default Routing as the mechanism for configuring the default mail delivery for an organization. The Routing setting can then be used for more specialized delivery rules or to override that default behavior.
This distinction becomes particularly important in environments using split delivery, dual delivery, catch-all addresses, mail gateways, external mail servers, migration systems, archiving systems, or special forwarding requirements.
What Is Default Routing in Google Workspace?
Default Routing controls the default delivery behavior for incoming email in a Google Workspace organization.
You can access it from:
Google Admin Console → Apps → Google Workspace → Gmail → Default Routing
Default Routing is especially useful when you want to establish a broad mail-delivery policy that applies to a large portion of your domain.
For example, an organization may want incoming messages to be delivered to both:
- Google Workspace Gmail
- An existing on-premises mail server
This is a typical dual-delivery scenario.
Another organization might be migrating users gradually from an old email platform to Google Workspace. Default Routing can form part of the overall delivery architecture.
What Is Gmail Routing?
The Routing setting is available at:
Google Admin Console → Apps → Google Workspace → Gmail → Routing
Routing provides administrators with more granular control over messages.
Rules can be created according to factors such as:
- Inbound messages
- Outbound messages
- Internal sending
- Internal receiving
- Specific recipients
- Specific senders
- Organizational units
- Configuration groups
- Address lists
- Account types
- Recognized users
- Groups
- Unrecognized or catch-all addresses
- Envelope recipients
- Alternate mail routes
Routing can therefore be thought of as the more flexible rule-processing layer for special mail-flow requirements.
Routing vs Default Routing: Quick Comparison
| Feature | Default Routing | Routing |
|---|---|---|
| Primary purpose | Establish default mail delivery | Create specialized mail-flow rules |
| Scope | Broad/default organization delivery | Granular and conditional |
| Best for | Default delivery architecture | Exceptions and special requirements |
| Dual delivery | Yes | Can also be used in applicable configurations |
| Split delivery | Common use case | Can participate in advanced configurations |
| User-specific rules | Less ideal | Better suited |
| Department-specific rules | Less ideal | Better suited |
| Catch-all scenarios | Possible | Commonly used and documented by Google |
| Unrecognized recipients | Can be handled | Can be specifically targeted |
| Outbound routing | Not its primary role | Yes |
| Internal message handling | More limited purpose | More granular |
| Add/change recipients | Available depending on configuration | Yes |
| Change route | Yes in applicable configurations | Yes |
| Conditional processing | More delivery-oriented | More flexible |
| Exception rules | Not its primary purpose | Recommended approach |
| Organizational policies | Default mail architecture | Specialized policies |
The Most Important Difference
Suppose your company has 500 users.
You want all incoming email to be delivered to Gmail and also copied to another email system.
That is a broad organizational delivery policy.
Default Routing is a logical place for this type of configuration.
Now suppose only the CEO's messages need to be copied to an executive assistant.
That is a special exception.
Routing is the better fit.
Conceptually:
Default Routing
What should normally happen to our organization's email?
Routing
What special rule should apply when particular conditions are met?
Example 1: Organization-Wide Dual Delivery
Suppose your company is migrating from an existing mail server to Google Workspace.
During migration, you want every incoming message delivered to:
Google Workspace Gmail
and
Existing company mail server
This is a classic dual-delivery requirement.
Default Routing can be used as part of the organization's default delivery architecture.
This avoids having to create individual forwarding rules for hundreds of users.
Example 2: Different Users on Different Mail Systems
Consider a company where:
- 70 employees use Google Workspace.
- 30 employees remain on an existing mail server.
Incoming mail needs to reach the correct system depending on the recipient.
This is known as split delivery.
Google Workspace routing architecture can direct messages to the appropriate mail system based on the recipient.
This is particularly useful during:
- Email migrations
- Company mergers
- Hybrid email deployments
- Gradual Google Workspace adoption
- Legacy mail-server transitions
Example 3: Copy One User's Messages to Another Mailbox
Suppose:
receives email normally, but the organization also needs a copy delivered to:
This is a specialized requirement rather than the organization's default mail-delivery behavior.
The Routing setting is normally the more appropriate place for such a rule.
A routing rule can identify the required recipient and add another recipient.
Example 4: Route Messages to Another Mail Server
Suppose your company uses an external security gateway, archive server, ticketing system, CRM, or another SMTP server.
You may create a mail host/route and then configure Gmail Routing to send matching messages through that route.
Examples include:
Google Workspace → Security Gateway → Internet
or:
Internet → Google Workspace → Internal Mail Server
or:
Gmail → Archive/Journaling System
Routing provides the granular controls required for these configurations.
Example 5: Catch-All Email Address
A catch-all address receives email sent to addresses in your domain that do not correspond to recognized recipients.
For example, assume your domain is:
example.com
and valid users are:
sales@example.com
support@example.com
Someone accidentally sends email to:
If a catch-all configuration exists, the message could instead be delivered to:
Google currently documents configuring this type of catch-all behavior through:
Apps → Google Workspace → Gmail → Routing
The rule can be configured to affect the Unrecognized/Catch-all account type.
This is an important administrative distinction because Routing lets you specifically target unrecognized recipients.
Example 6: Reject Unknown Email Addresses
Some organizations do not want a catch-all mailbox.
Instead, they want email sent only to legitimate, designated Google Workspace addresses.
For example:
accounts@example.com → Accepted
support@example.com → Accepted
randomname@example.com → Rejected
If no catch-all or other routing rule intercepts the message, mail addressed to a nonexistent Google Workspace recipient will normally fail rather than being delivered to an arbitrary mailbox.
This is often preferable from a security and administration perspective because catch-all mailboxes can collect:
- Spam
- Dictionary attacks
- Typing mistakes
- Automated marketing email
- Phishing attempts
- Messages sent to obsolete addresses
Therefore, administrators should not create a catch-all rule unless there is a genuine business requirement.
Message Types Available in Routing
One major advantage of Gmail Routing is the ability to specify which message direction should trigger a rule.
Common choices include:
Inbound
Messages arriving from outside your organization.
Example:
customer@gmail.com → sales@example.com
Outbound
Messages sent by your users to recipients outside your organization.
Example:
sales@example.com → customer@gmail.com
An outbound routing rule might send messages through:
- A security gateway
- An email archive
- A compliance service
- A third-party SMTP server
Internal - Sending
Messages being sent internally by users in your organization.
Internal - Receiving
Messages being received internally by users in your organization.
These options provide much more granular control when an administrator needs rules to behave differently depending on message direction.
Recognized Users vs Unrecognized Recipients
Another important concept in Gmail Routing is the account type affected by a rule.
A routing rule can be designed for categories such as:
Users
Actual Google Workspace user accounts.
Example:
Groups
Google Groups addresses.
Example:
Unrecognized/Catch-all
Addresses that Google Workspace does not recognize as existing users or groups.
Example:
when no such user or group exists.
This setting is particularly important when creating catch-all configurations.
What Is an Envelope Recipient?
Administrators should understand the difference between the visible email address and the SMTP envelope recipient.
During SMTP delivery, the sending server identifies the destination using an SMTP command similar to:
RCPT TO:user@example.com
This is the envelope recipient.
Routing rules can inspect or modify the envelope recipient.
For example:
Original envelope recipient:
Changed envelope recipient:
The message can therefore be redirected without requiring the sender to know that the delivery destination changed.
Replace Recipient vs Add Recipient
This distinction is extremely important.
Replace Recipient
If the original recipient is:
and the rule changes the recipient to:
the effective delivery is redirected toward the new destination according to the rule.
Conceptually:
sales@example.com → manager@example.com
Add Recipient
If you add another recipient instead, the message can be delivered to both destinations.
Conceptually:
plus:
This is useful for:
- Monitoring
- Archiving
- Department copies
- Migration
- Backup delivery
- Ticketing systems
- Compliance systems
Always verify whether your requirement is redirect, copy, or dual delivery before creating the rule.
Routing Rules Can Modify Messages
Routing isn't limited to choosing a destination.
Depending on the configuration, administrators can modify how messages are processed.
Examples include:
- Add recipients
- Change envelope recipients
- Change routes
- Require secure transport
- Apply address-list conditions
- Apply envelope filters
- Route messages to alternate hosts
- Control message delivery based on direction
This makes Routing one of the most powerful Gmail administration features.
Organizational Units and Routing
Routing can also be useful when different departments require different mail-flow behavior.
For example:
Management OU
Messages may require additional archiving.
Accounts OU
Messages may need to be copied to a compliance system.
Sales OU
Certain messages may need to enter a CRM.
General Users OU
Normal Gmail delivery.
This type of granular configuration is where Routing is generally more suitable than establishing everything as Default Routing.
Configuration Groups
Google Workspace can also use configuration groups for certain Gmail settings.
This gives administrators additional flexibility when users requiring a special configuration don't fit neatly into an organizational-unit structure.
For example, employees from several departments might need a special routing policy.
Rather than restructuring OUs simply for that requirement, an administrator may be able to apply the appropriate configuration using a supported configuration group.
Address Lists
Address lists are useful when a routing policy should apply—or should not apply—to particular senders or domains.
For example, an organization could maintain trusted domains and use them as conditions or exceptions in relevant Gmail rules.
This is much easier to administer than repeatedly entering the same addresses into multiple rules.
Default Routing Is Not Simply "Old Routing"
A common misconception is:
Default Routing = old version
and
Routing = new version
That is not the correct conceptual model.
Both settings exist because they serve different administrative purposes.
Think of them as layers:
Layer 1 – Default Routing
Defines broad/default mail delivery.
Layer 2 – Routing
Handles specialized requirements, exceptions, and more granular mail-flow rules.
Google explicitly describes Routing as capable of creating specialized delivery rules or overriding Default Routing behavior.
Can the Same Requirement Sometimes Be Achieved Using Either Setting?
Yes.
This is one reason administrators become confused.
There is some overlap between the capabilities of Routing and Default Routing.
For certain mail-flow designs, similar outcomes may be possible using either setting.
However, the fact that something can be configured in both places does not mean both designs are equally easy to understand or maintain.
A good administrative principle is:
Use Default Routing for broad/default delivery architecture.
Use Routing for specialized conditions, exceptions, user/group/OU-specific requirements, and granular message handling.
This produces a mail-flow configuration that future administrators can understand more easily.
Recommended Design Example
Consider an organization migrating from an old email server.
The architecture might be:
Internet
↓
Google Workspace
↓
Default Routing
↓
Normal organizational delivery / migration architecture
Then specialized rules can be layered on top:
Routing Rule 1
CEO email → Add executive assistant
Routing Rule 2
Support email → Add ticketing platform
Routing Rule 3
Selected department → Archive server
Routing Rule 4
Specific outbound messages → Security gateway
This creates a cleaner separation between the organization's default mail architecture and its exceptions.
Which One Should You Use?
Use Default Routing when your requirement sounds like:
"This should be the normal/default delivery behavior for most or all of our organization's incoming mail."
Use Routing when your requirement sounds like:
"When these particular conditions are met, I want Gmail to do something different or additional."
When to Use Default Routing
Consider Default Routing for:
- Organization-wide mail delivery
- Broad dual-delivery architecture
- Migration-related delivery
- Hybrid mail environments
- Default recipient-routing architecture
- Large-scale delivery to multiple systems
- Broad recipient-based delivery policies
When to Use Routing
Consider Routing for:
- Specific users
- Specific departments
- Specific groups
- Specific sender/recipient conditions
- Catch-all configurations
- Unrecognized recipients
- Adding recipients
- Redirecting recipients
- Special outbound routing
- Internal message routing
- External gateways
- Archiving
- CRM forwarding
- Ticketing systems
- Specialized compliance workflows
- Exceptions to normal delivery
Important Warning About Routing Rules
Routing rules affect production email flow.
An incorrectly configured rule can potentially:
- Redirect email to the wrong mailbox
- Duplicate messages
- Prevent expected delivery
- Send confidential messages to unintended recipients
- Route messages through the wrong mail server
- Create mail loops
- Cause unexpected bounce messages
- Affect hundreds or thousands of users
Therefore, routing changes should be planned carefully.
Best Practices for Google Workspace Administrators
1. Document Every Routing Rule
Give every rule a meaningful description.
Instead of:
Rule 1
use:
Copy Support Mail to CRM
or:
Route Legacy Users to Exchange Server
This makes future troubleshooting significantly easier.
2. Keep Default Routing Simple
Avoid filling Default Routing with numerous special-case rules if those rules are really exceptions.
Keep the organization's baseline delivery architecture easy to understand.
3. Use Routing for Exceptions
Special users, departments, gateways, archives, and other conditions are generally easier to manage through Routing.
4. Avoid Unnecessary Catch-All Rules
If your organization only wants email delivered to valid addresses, you usually do not need a catch-all.
This helps reduce unwanted mail.
5. Test With Dedicated Accounts
Before applying a new rule widely, test it using controlled accounts or an appropriate OU/configuration group whenever possible.
6. Check Existing Rules Before Adding New Ones
Before troubleshooting Gmail delivery, inspect:
Default Routing
and
Routing
as well as other applicable Gmail compliance and gateway settings.
Multiple rules can affect the same message.
7. Understand Redirect vs Copy
Before creating a rule, decide whether the original recipient should:
- Continue receiving the message
- Stop receiving the message
- Receive the message along with another recipient
- Have the message routed to another mail server
These are different requirements.
8. Maintain a Mail-Flow Diagram
For complex Google Workspace environments, maintain documentation such as:
Internet → Google Workspace → Gmail
or:
Internet → Google Workspace → Gmail + Legacy Server
or:
User → Google Workspace → Security Gateway → Internet
This makes troubleshooting considerably easier.
Troubleshooting Routing Problems
If messages are being delivered incorrectly, check the following areas.
Check 1: Default Routing
Go to:
Admin Console → Apps → Google Workspace → Gmail → Default Routing
Look for rules that may affect the recipient.
Check 2: Routing
Go to:
Admin Console → Apps → Google Workspace → Gmail → Routing
Check all applicable rules.
Check 3: Organizational Unit
Verify which OU contains the affected user.
Check 4: Configuration Groups
Check whether a configuration group is applying a different Gmail policy.
Check 5: Account Type
Determine whether the destination is:
- User
- Group
- Alias
- Unrecognized recipient
Check 6: Message Direction
Determine whether the message is:
- Inbound
- Outbound
- Internal sending
- Internal receiving
Check 7: Envelope Recipient
The address displayed in an email client does not always tell you everything about SMTP routing.
Check the actual recipient and routing behavior using Google Workspace email investigation/log tools available with your edition.
Check 8: MX Records
Routing rules only become useful when messages are actually reaching the intended Google Workspace mail infrastructure.
Incorrect DNS/MX configuration can therefore cause delivery problems before your intended Gmail routing architecture can work properly.
Routing vs Default Routing: Decision Table
| Requirement | Recommended Starting Point |
|---|---|
| Default delivery for organization | Default Routing |
| Dual delivery for most users | Default Routing |
| Migration mail architecture | Default Routing |
| Hybrid email environment | Default Routing |
| Special rule for one employee | Routing |
| Department-specific rule | Routing |
| Copy CEO mail to assistant | Routing |
| Route support mail to CRM | Routing |
| Catch-all mailbox | Routing |
| Handle unrecognized recipients | Routing |
| Special outbound gateway rule | Routing |
| Add another recipient | Routing |
| Route specific messages to another server | Routing |
| Create an exception to default delivery | Routing |
| Complex conditional mail flow | Routing |
Frequently Asked Questions (FAQ)
1. What is the main difference between Routing and Default Routing in Google Workspace?
Default Routing establishes the organization's broad/default incoming mail-delivery behavior, while Routing is intended for more specialized and conditional delivery rules.
2. Which setting should I use for normal Google Workspace email?
If all users simply receive email in their normal Gmail mailboxes, you may not need to create custom routing rules at all.
3. Which setting should I use for a catch-all address?
Google currently documents catch-all configuration through:
Apps → Google Workspace → Gmail → Routing
where a rule can target Unrecognized/Catch-all recipients.
4. What happens if I don't configure a catch-all?
Email addressed to a nonexistent recipient will generally be rejected rather than being delivered to an arbitrary mailbox, assuming no other routing configuration handles that address.
5. Can Default Routing and Routing both be active?
Yes.
They can be used together as part of the same Google Workspace mail architecture.
6. Which one takes priority?
Do not assume that whichever rule appears first in the Admin Console automatically wins.
Google Workspace mail processing can involve multiple applicable settings and rule conditions. Routing can also be used to create specialized rules or override Default Routing behavior.
When troubleshooting, review the complete mail-flow configuration rather than considering a single rule in isolation.
7. Can Routing apply only to one user?
Yes. Routing provides conditions and scope controls that can be used to create targeted mail-flow behavior.
8. Can Routing apply to an organizational unit?
Yes, applicable Gmail Routing settings can be scoped according to organizational structure and supported configuration mechanisms.
9. Can I route outgoing messages?
Yes. Gmail Routing supports outbound message processing.
For example:
User → Gmail → Third-party gateway → Recipient
10. Can I route email to another SMTP server?
Yes.
Administrators can define mail hosts/routes and configure appropriate Gmail routing to send matching messages through another server.
11. Can I send one message to two mailboxes?
Yes.
This can be achieved through appropriate dual-delivery or additional-recipient configurations, depending on the requirement.
12. Is Default Routing only for old Google Workspace configurations?
No.
Default Routing remains a distinct Google Workspace mail-delivery configuration concept. It should not simply be viewed as an obsolete version of Routing.
13. Can Routing override Default Routing?
Google describes Routing as a way to create more specialized delivery rules or override Default Routing behavior.
This is one of the most important concepts to understand when designing mail flow.
14. Should every Google Workspace domain have Default Routing rules?
No.
A normal Google Workspace organization may not require custom Default Routing at all.
Do not create routing rules simply because the options exist.
15. Should I create a catch-all mailbox?
Only when there is a genuine business requirement.
Catch-all addresses can collect significant amounts of spam and mail sent to incorrect addresses.
16. What is an unrecognized recipient?
An unrecognized recipient is an address in your domain that Google Workspace does not recognize as an applicable valid recipient, such as a configured user or group.
For example:
17. What is an envelope recipient?
It is the SMTP delivery recipient used during mail transport.
Conceptually:
RCPT TO:user@example.com
Routing rules can use envelope-recipient information to determine how a message should be processed.
18. Can I redirect an old employee's email to another user?
Yes, but the best method depends on whether the account still exists, whether the requirement is temporary or permanent, licensing considerations, and whether you need forwarding, aliases, address mapping, Groups, or routing.
Avoid automatically using a catch-all for this purpose.
19. Can I copy incoming emails to an archive mailbox?
Yes. Appropriate routing configurations can add recipients or route copies to other systems depending on your requirements.
20. Can a bad routing rule stop email delivery?
Yes.
Incorrect routing can cause rejection, duplication, misdelivery, routing loops, or delivery to unintended destinations.
Routing changes should therefore be tested carefully.
Final Summary
Google Workspace administrators should not treat Routing and Default Routing as interchangeable settings even though their capabilities overlap.
The easiest conceptual distinction is:
Default Routing = Organization's baseline/default mail-delivery architecture
Routing = Specialized rules, conditions, exceptions, and advanced message handling
For example:
"All company email should follow this delivery architecture."
→ Start with Default Routing
"Only messages matching this particular condition should behave differently."
→ Use Routing
For a clean Google Workspace configuration, keep the default mail-flow architecture simple and use Routing for targeted exceptions and specialized requirements.
Administrators should also remember that many organizations using Gmail normally do not require either a complicated Default Routing configuration or dozens of custom Routing rules. Create a rule only when there is a clear business, migration, security, compliance, forwarding, or delivery requirement.
Tags
#GoogleWorkspace #Gmail #GmailRouting #DefaultRouting #GoogleWorkspaceRouting #EmailRouting #GoogleAdmin #GoogleAdminConsole #GmailAdmin #EmailAdministration #GoogleWorkspaceAdmin #MailRouting #MailFlow #EmailDelivery #GmailSettings #GoogleWorkspaceSettings #DualDelivery #SplitDelivery #CatchAll #CatchAllEmail #EmailForwarding #MailForwarding #InboundEmail #OutboundEmail #InternalEmail #EmailGateway #MailGateway #SMTP #SMTPRouting #GoogleWorkspaceSMTP #GmailSMTP #EmailSecurity #GoogleWorkspaceSecurity #EmailMigration #GoogleWorkspaceMigration #MailServer #EmailServer #MXRecords #DNS #EmailTroubleshooting #GmailTroubleshooting #GoogleWorkspaceTips #GoogleWorkspaceGuide #GmailGuide #GoogleWorkspaceTutorial #GmailTutorial #ITAdmin #SystemAdministrator #WorkspaceAdmin #GoogleWorkspaceSupport
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.