On 12/5/24 12:51 PM, Nick Lock via mailop wrote:
On Thu, 5 Dec 2024 at 10:29, Matthew Richardson via mailop <mailop@mailop.org <mailto:mailop@mailop.org>> wrote:John Levine wrote:- >All of the instructions for setting up mail at Google say to change the MX first >before you've set up any mailboxes, which makes no sense -- how will it know >what to do with the mail? > >Can someone who's done this before give me some hints? TIA. Having only done a migration to Google once, my notes from the job back in 2021 unhelpfully read:- >it did not seem to allow the setup [of the domain] to be completed before >the MX was changed to route the email - [client] was happy with the risk - >for larger migrations, this would be problematic The domain was fairly new with only one mailbox hosted elsewhere, which mitigated the risk. I did not manage to find a better solution, but did not have much time for research. Hopefully Martin Hasenbein's suggestion will work, and I will keep a note of it lest I need to do another migration to Google in the future. Our migration was done back in 2018, so the current details may vary slightly - but Martin's experience with receiving a 'test' domain matches ours. It was entirely possible to pre-allocate mailboxes and settings in the test domain, and then bring the main domain into the Google account later on. I recall that once the main domain was correctly verified with Google, and associated with the account, all existing user accounts received "username@$(main.domain)" as an alias automatically. The 'Primary Domain' of the account may need altering after verification, though? However, we performed the migration slightly differently as we were moving the domain away from our own mail system. With Google Workspace it is possible* to configure Gmail routing to redirect all mail for unknown users to another MX - which allowed us to move the MX record early in the migration by routing all mail that didn't hit a Google routing rule back into our mail system. This gave us a great deal of additional time to re-create our legacy mail routing configuration in Google, without losing any incoming mail.
I think it should not be required to change MX to verify the domain with Google; we recently (~1 month ago) moved a domain to GWorkspace, we verified the domain and configured it on GWorkspace, moved data from old server, then changed MX record. The only issue we encountered was that Google IMAP was slow and their migration tool was slower. Giovanni
* If your Google product has the capability - Apps -> Google Workspace -> Settings for Gmail -> Hosts -> Add Route Enter the details of the "old" MX server. The "name" field will be referenced in the next step. In the options, we also enabled "Require mail to be transmitted via a secure (TLS) connection (recommended)" and "Require CA-signed certificate (recommended)" Apps -> Google Workspace -> Settings for Gmail -> Default Routing -> Add rule Section 1: Match 'All Recipients' Section 2: Enable 'Route: Change the route' and under that also enable 'Suppress bounces from this recipient'. The dropdown at the end of the Route section should be changed from 'Normal Routing' to the host set up above. Section 3: Choose 'Perform this action only on non-recognised addresses' Best Regards, Nick. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
