My practical scenerio:
I have an external account admin@mydomain_com registered with Google.
By default, MIAB creates automatically an internally alias admin@ mydomain_com.
I setup host mail server MIAB mail.mydomain_com and email account as xxx@mydomain_com
====> How to route local recipient to admin@mydomain_com hosted in Google server.
-Local sender sends to local recepients through local (mail.mydomain_com) as usually. So when local sender sends to admin@mydomain_com, it will process internally, and external account admin@mydomain_com hosted by Google do not receive.
My expectation: External account admin@ mydomain_com hosted by Google can receive email from local sender.
What I have done:
-Setup transport_maps with “admin@ mydomain_com delay:[AWS SES]:587” but it seems doesn’t work, still process internally. (Check syslog and it shows that email doesn’t go to AWS SES interface)
-Setup transport_maps with “mydomain_com relay:[AWS SES]:587”, then all emails from local senders to local recipients will be relayed to AWS SES interface, HOWEVER, then to Google , then go back to SES AWS and the status = bounced.
+In this case, event send to admin@mydomain_com, we still encounter status=bounced.