GW Account owner email account with no gmail service

[alexgrutza]

For the "account owner" email in GW, I have it set up as my super admin account. Great right, not my daily driver? Well our Super Admin accounts don't have the Gmail service enabled, so emails sent to that (like google notifications) get bounced.... Well I thought about that, and have created a few settings to try and get any emails sent to that super admin account to be redirected to my actual daily driver, because again we don't want our super admins to have gmail.

So I have...

1. an address mapping (all incoming emails to superadmin@example.com map to dailydriver@example.com)
2. a routing rule for inbound,internal receiving going to superadmin@example.com to redirect to dailydriver@example.com 
3. i also have a compliance rule for ALL MATCH inbound,internel receiving going to superadmin@example.com and from workspace-noreply@google.com to redirect to dailydriver@example.com

So I ran a test, from my personal external gmail, sent to superadmin@example.com and the email came through. I ran another test from an internal domain account and it gets a bounce that the account can't receive messages.

So the emails from the workspace-noreply@google.com do not appear to be arriving because the superadmin@domain.com doesn't have gmail service and is being bounced.

Suggestions on how to get this scenario to work?

[Josh · Accepted solution]

We have a similar scenario where we use a routing rule to redirect the incoming message to a different non-domain address.

Having said that, none of our staff (myself included) have the Gmail service enabled on our workspace accounts. So we have a recipient address map setup that redirects all messages to our email accounts at a different domain. I just tested this, and the redirect from an internal account (same domain) worked fine.

The settings on the address map are simply 'all incoming messages' and 'Also route to original destination'. It just works.

If you were testing perhaps you needed to wait longer for the settings to fully propigate?

[alexgrutza]

Thanks for your response. I'm marking it as the answer though in our experience it didn't work when the internal account didn't have gmail enabled. There was another reason we ended up turning on the gmail service is that the service needs to be on for Gopher for Gmail and that required a super admin (I think) account. 

I'll keep the rules in place to route all gmails to the non-super admins for their super admin accounts