We're using Cloudron to replace some of our company's pre-existing services, notably email. (And of course to add new ones.)
To date, mail for the company's domain has just been routed to a single GMail account, to which everyone who needs access shares log-in details for.
With Cloudron we have the ability to create personal and shared mailboxes. However, for the time being we want to keep the official company email on the GMail account, simply because everyone's used to that and we don't want to disrupt our main communication channel. Later when Cloudron has proved itself, we might persuade people to shift.
However, in setting this up we have encountered more obstacles than I expected.
The top-level question I have is, how have other people solved this?
Following are some of the angles we've looked at. I think my favourite would be the second one, if it were possible.
1. Configuring personal emails via an MX on a subdomain, leave the top-level domain as-is
Currently we have an MX record which points to the domain registrar's MTA, which then forwards everything to the one GMail account.
So the company domain would normally be configured by Cloudron to have itself as the primary MX server, if it is set to "Automatic" mode. This clobbers the MX record and the redirect that implements, so we're deferring that and keeping it on "Manual" until we resolve our problem.
One workaround might be to have Cloudron manage only the MX on a subdomain. I think I see how to do that using the "Change Dashboard Domain" panel, but it means our new personal emails have to use that subdomain, and I'd rather avoid that if possible.
2. Add a Cloudron shared IMAP inbox for the company email as an external GMail account
Another angle we've tried is to add a catch-all shared Cloudron mailbox to GMail as an external account. GMail used to support this, I think. Now I find it only supports external accounts which are hosted on:
- POP3 servers, or
- Special IMAP services which are supported by their "GMailify" service.
Arbitrary IMAP servers like Cloudron servers are apparently not supported by "GMailify" (see link below); and Cloudron does not support a POP3 service, which is the only other option GMail offers.
3. Forwarding the company email address to the GMail account
Maybe we could create a Cloudron mailing list and use that to forward email sent to the company address on to the GMail account's address...
However, I'm a bit concerned that GMail will then see all the spam and then blacklist our Cloudron server. I've experienced this previously in other cases, where a domain's email was naiively forwarded to a GMail mailbox. It seems a bit risky, even if Cloudron does set up the SPF, DMARC and DKIM, because mail to our main email address is then at the mercy of Google's algorithms.
Google's support document on this does not really reassure me:
4. Set Google as the MX for our domain
There is the option to defer outgoing delivery services to Google. I've not yet seen one to allow Google to set as the MX for Cloudron's domain. However, I would prefer not to, as part of the point is to move away from Google and to use open-source software. But this would be one of our final options.