Setup
One routing rule, in a console you already administer.
Ten minutes, no MX change, and you can undo it in under a minute. Read only the section for your provider.
Before you start
- Administrator access to Google Workspace or Microsoft 365 for the domain.
- Access to the DNS zone for that domain, to add one TXT record.
- One email address that should hear about a rescue.
Verifying the domain
Nabvia gives you a TXT record when you add a domain. Add it at your DNS host and Nabvia checks it. This proves you control the domain and nothing else; it does not affect mail, because a TXT record is not an MX record.
Jump to your provider
Google Workspace
Google's default routing lets you catch messages for addresses that do not resolve, without touching any mailbox that does.
Open default routing
In the Google Admin console, go to Apps, then Google Workspace, then Gmail, then Routing, then Default routing.
1 minutes
Add a setting that matches your domain
Choose Add setting. Match on the envelope recipient, matching the domain you are protecting.
2 minutes
Limit the rule to unrecognized addresses
In the routing options, restrict the setting to unrecognized or catch-all addresses only. This is the control that keeps the rule away from every real mailbox.
1 minutes
Send to Nabvia and save
Set the action to change the envelope recipient to your tenant address at inbound.nabvia.com, then save. Google applies routing changes within about an hour.
1 minutes
- The rule matches on the envelope recipient for your domain.
- The action changes the recipient to your tenant address at inbound.nabvia.com.
- The scope is restricted to unrecognized addresses only, so no real mailbox is affected.
Microsoft 365
Microsoft 365 needs the domain marked as an internal relay before it will hand an unknown recipient to a connector.
Set the accepted domain to internal relay
In the Exchange admin center, go to Mail flow, then Accepted domains, and change the domain type from Authoritative to Internal relay.
2 minutes
Add a connector to Nabvia
Go to Mail flow, then Connectors, and add a connector from Office 365 to your organization's email server, using the smart host inbound.nabvia.com with TLS required.
3 minutes
Scope the connector to that domain
Restrict the connector to the accepted domain you just changed, so nothing else in your tenant is affected.
1 minutes
Validate and save
Run the built-in connector validation, then save. Microsoft applies the change within about an hour.
2 minutes
- The rule matches on the envelope recipient for your domain.
- The action changes the recipient to your tenant address at inbound.nabvia.com.
- The scope is restricted to unrecognized addresses only, so no real mailbox is affected.
What you should see in the first hour
- Send a message to a deliberately wrong address on your domain, from an outside account.
- Confirm that message does not bounce back to the sender.
- Confirm the notification arrives, from an address at notify.nabvia.com.
- Send a message to a real address on your domain and confirm it lands normally.
Add the rule. Stop losing mail.
Ten minutes in a console you already administer, and your normal delivery is untouched.
- 14-day trial, no card
- Never your MX