Sounds like you want to do what I've done then.
Your biggest issue will be email as I'm assuming you don't have a static public IP.
I thought about doing what you're talking about - using gmail. I'd not recommend it .. I've got a gmail account that I've only ever used to send email once - a test account I set up to test the send/receive on my own set up .. and it still gets inundated with spam, so unless you want to have spam filling your inbox, I'd not recommend it.
I originally used DYN.COM for my email as it was part of the registration package, but the email aspect got taken over by DuoCircle, and I have to say I'm extremely pleased with it .. I have the email gateway with them, and the SMTP service, paying for 150 emails per day which I find is more than sufficient. Once the single MX record and SPF and DKIM are defined it just sits there working. Costs me a total of $140 pa - not expensive for email peace of mind.
The email gateway is brilliant; I don't see any spam; it all gets blocked before it gets anywhere near my server, and using SSL between the two only allowing an authenticated connection (using a long, random password), anyone trying to hack their way in to my server directly (bypassing the DuoCircle gateway) fails authentication. So no spam, and no successful hacks for the past 5 years.
Steve Beardall wrote:
When you say "configure", do you mean create an MX record at my domain registrar that forwards emails to Gmail(Google)? I don't think that would works because Google requires authentication when you relay messages to their SMTP server.
No I don't. Quite often, providers like whoever you've got your website hosted by, provide a number of ways of handling email - either by creating inboxes on their site (which you pays extra for), or provide you with (eg) a dozen email addresses that you can define forwards for to the email host of your choice .. gmail for example.
What I'm suggesting, is that you look at what email features are provided to your by your hosting service .. if you have the 'forward' capability, you just need to automatically forward emails to (your example) firstname.lastname@example.org on to the gmail account of your choosing. Then, in gmail, you define cleanmy.cloud as a legitimate domain from which you can send emails. You then either just use the web gmail client, or set up your account/authenticated smtp logins from your desktop client using your normal gmail login. No MX setups whatsoever.
Ok; it all becomes clear .. and it's down to date/time sort on the /app/software_updates page(!).
I DO have the latest kernel, BUT the page 'lies'.
If you expand the number of rows to show (eg) 200 .. all becomes clear. If you sort oldest-first, then everything appears in the correct order.
Sort of LATEST first though .. then you get (eg)
Jul 3, 4, 5, ...17,18,19, THEN June 2, 3, 4, etc (!!!!) - you'll also want to check the time field too ...(!)
July 19,18,...6,5,4,June 30,29,28 ... 2,1
Something odd is going on; I've just checked my 3 systems, and NON of them are showing the kernel as outstanding. The server with the most apps is showing the last update as back on June 26 (app-storage-2.6.15-1.v7).
I'm confused; unless I've completely misunderstood what you're trying to do, why not just configure the (remote) domains to forward emails directly instead of introducing another re-direction?
Nick; be aware that the upgrade of Nextcloud to v16 requires the addition of a number of additional db indices. They can be installed via an occ command.
RE: the 4-byte utf-8 issue; it probably depends on what the original version of Nextcloud used in the (original) app is. The message shows up in the admin page of Nexcloud - it works without the table setting, but if the table doesn't have the capability, you just get a warning to say that emojis won't be supported - probably not important as is appears to be in the email part of Nextcloud, but I personally like to get rid of as many warning as possible. There's also a warning that a recommended php module (imagick) is missing, but I've not looked into that ATM.
RE: the ldap line about 4-byte utf-8 .. if that's what I think it is, it's also common to the latest version of Nextcoud .. the MariaDB tables for Nextcloud (and, I suspect, kopano) require the 4-byte capability to support emojis. It only applies to those tables and is easier to put in place and it's a one-time conversion - I've got the latest version of Nextcloud living in its own virtual web subdomain running php 7.2 (on a COS7 server using the 7.2 option of the php-engine app).
You didn't look very hard. I went to the knowledgebase page, hit 'v' and oh look; there's 'Virtualbox'. I searched the page for 'kvm' and oh look: there's 'Install Virtualisation using KVM'.
I'm not an employee of ClearOS so I don't have to be polite - a bit like you. You seriously need to pull your neck in if you want help. Quodos to Nick for his restraint; I've found him to be extremely helpful.