Some feedback, if anybody's interested...
Yesterday's 'proof of concept' dry run, using a spare .com domain name, went smoothly. The domain I used has no website which complicated things as google ask for a token file to be posted on the home page for authentication. That wasn't possible, so I elected an alternative which is to update the SPF record which worked fine, but will have side effects which may or may not be beneficial (search for SPF if you're interested. I'd never heard of SPF til yesterday
).
Today I did it for real with my primary domain name, which does have a website, much easier.
The only minor annoyance was that you have to configure five MX (DNS mail routing) records for the domain, via the registrar's control panel. Google tell you exactly what they are so cutting & paste via clipboard should avoid mistakes .. well, no. Google list the MX records in upper case, whereas my registrar needs them in lower case. Plenty of opportunity for error there then, typing them all in again!
One other thing to watch out for is that, on completion of setup the 'catch-all' email address, which I regard as quite important, is still empty so I assume poorly addressed incoming email would just evaporate. I'd have thought it more sensible to default to the username that did the setup? Anyway, it's easily changed once you find the setting.
- 7LM