Menu
In G Suite's Gmail advanced settings, there is a place for Routing and a separate tab for Default Routing. The settings are not in sync. What is the difference between them?
I am trying to setup special routings like catch-all and the some guides told me to do it in Routing while some showed me how to do it in Default Routing.
578
Default routing also lets you specify an account as a catch-all address. Catch-all behavior is configured with a default route set up to redirect messages for unrecognized users. Default routing to unrecognized users affects users who don't exist, suspended users, and those with Gmail turned off.
Gmail Vs. The services are limited, but free. G Suite – G Suite is a paid service, and ownership of the account lies with the person who created it – or is given admin rights. Because of this, G Suite is essentially the paid version of Gmail and Google accounts, but with access to a few more business tools.
There are a few key differences that set Google Workspace and Gmail apart: Gmail is free to use, whereas Google Workspace is a chargeable service; Google Workspace plans range from $6–$18 per user, per month. Gmail users have full administrative control over their email and Google Account login credentials.
There is now another routing option called "Recipient Address Maps". Google's docs still appear to be silent on when to use which type. Please see below for a discussion of what each seems to be good for. To answer your specific question, I think you can achieve the exact same result with Routing Rules and Default Routing Rules, assuming you do not need the extra power provided by Routing Rules (see below).
Routing Rules are the most powerful of the three types. They are not particularly well suited for forwarding many addresses as the UI is not setup to scale to have lots of rules. They CAN be used to implement “catchall” rules to route all otherwise unrecognized addresses. They can be specified per-OU. They can apply to inbound as well as outbound messages. Unlike the other rules, they can match against the sender. You can specify lists of addresses for them to apply to. They can distinguish between messages originating from internal vs. external senders.
Default Routing Rules sit between the other two in terms of power. They are appropriate for handling forwarding of large number of specific addresses. 1000 Default Routing rules may be specified and the admin UI is well suited for large numbers of rules. They can be used to implement “catchall” rules to route all otherwise unrecognized addresses. They are global (not specifiable per-OU). They apply only to inbound messages. They cannot distinguish between internally vs externally originating messages. They support explicit prioritization between different Default Routing Rules.
Recipient Address Maps are the most limited of the three (really just mapping from address A to address B) but seem to be the most appropriate for handling forwarding of large number of specific addresses. They support mapping up to 5000 addresses and the admin UI is well suited for large numbers of rules. I do NOT believe that they support a “catchall” to route all otherwise unrecognized addresses. They appear to be global (not specificable per-OU). They can apply to all incoming messages or only externally-originating messages.
88
answered Oct 20 '22 22:10
I've contacted the GSuite support (mail and phone) because I had the exact same question. This is the answer I received from them (translated from german):
Es gibt einen Unterschied zwischen Standard-Routing und Routing. Beim Standard-Routing erstellen Sie das gesamte Routing für die Domäne. Im Standard-Routing haben Sie die Möglichkeit, den verschiedenen Regeln Priorität zuzuweisen, was beim Routing nicht möglich ist. https://support.google.com/a/answer/2368153?hl=de#ordering
There is a difference between "Default-Routing" and "Routing". With "Default-Routing" you can create routes for the whole domain. With "Default-Routing" you can add priorities for the ruleset, which is not possible with "Routing".
Vor einem Jahr gab es etwas namens User Level Routing. Es war auf Benutzerebene verfügbar und wurde über die Admin-Konsole> Benutzer erstellt. Diese Option wurde veraltet und der Abschnitt Routing wurde erstellt, wenn alle zuvor erstellten Benutzer Routings sichtbar waren. https://support.google.com/a/answer/2685650?hl=de
Until last year (2017) there was also "User-Level-Routing". It has been available on user-level and could be created under "Admin > Users". (and now comes the weird sentence) This option has been deprecated and the section "Routing" has been created, if (when?) all formerly created User-Routings were visible.
Mit Routing können Sie keine Priorität festlegen, und Sie können es nicht zum Erstellen bestimmter Routing Vorgänge auf Domänenebene verwenden.
With "Routing" you cannot add priorities and you cannot use it for creating certain routing-procedures on domain-level.
@williamli: were you able to get further insights?
Best, Chris
20
answered Oct 20 '22 21:10
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
