Deployed at https://cloudron.io/documentation/security/#privacy-control

This is fixed in 5.5

In some ways, I think this is what POP is for (I think) but we don't support it.

I put a package at https://git.cloudron.io/cloudron/php7.3-postgres-app/ . This is a PHP 7.3 app that has postgres.

@girish much appreciated... thanks for looking into it!

@jdaviescoates Yeah, removed it from our code for the next release. 5.5 should be out next week.

@Vladimir Can you check /home/yellowtent/boxdata/mail/vmail on the server? There is a directory for each mailbox. If you enter the mailbox, there is a sieve directory. You can just delete the entire directory to remove the rules and then restart the mail server, in case dovecot had cached it. (You can also do a quick grep on the address in the above directory to see if it's referenced anywhere else).

Thanks @marcusquinn ! There is a bug in the Cloudron code where we were using the wrong API call to list zones when validating the config. https://git.cloudron.io/cloudron/box/-/commit/45c49c975712ee4b3bbf306ca7492c60a41c4c57 was the fix.

@girish That's awesome news! Looking forward to v6.0 then! Keep up the awesome work

@joerodge I guess you got this sorted out by the time I approved your forum post? I can access your dashboard here: [image: 1596583897181-4100fcee-ca9a-4e59-8e1b-79bf989fc3d1-image-resized.png]

@alejandrolengua This documentation page is mostly geared towards setting up with different DNS providers, but this is a good place to start too as you'll need this to add new domains to your Cloudron server: https://cloudron.io/documentation/domains/

This got sorted out after waiting for DNS propagation.

Indeed I see that also as the last remaining artifact from the missing translation. I rebuilt and restarted nodebb but that didn't change this at least so far.

@girish Thanks a lot for this great support and that you want to take a look at it It's not a must have, but it come's very handy for monitoring my Cloudron instance and get warnings if something goes weird or reaches high loads. Netdata is also something i did not think about earlier, so maybe that will workout for me as well. I must say (apart from this topic), i am really 100% satisfied till so far about Cloudron and the active community that's behind it. Many answers to my questions i did already find here in the forums Also a big thanks to the Staff of Cloudron, that picks up problems really quick and solve's them as much as they can. I hope Cloudron will live for a long time in the upcoming future, because it's the solution i was looking for a long time Really glad i came accros all this and thanks to everybody

This is marked as solved but doesn't actually appear to be @girish @nebulon

@austinsonger Is the server also hosted in Azure? PTR records are not part of your DNS zone. They should instead be set from wherever your server is hosted (i.e whoever owns the IP address of the server) It seem Azure does not have a UI to set PTR records but you have to use the CLI - https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services . What you are trying to do is https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-hosting I think, this is not what we want. Quite confusing from Azure. Tagging @derek since he knows Azure stuff.

@girish That would be ideal! In fact if that can come in the next couple of months, I'll hold off my own DNS change until that's there. Because the whole "my." doesn't really conform to the standards that people expect when they need to enter in their server names for a mail server. I'd definitely love if Cloudron could use it's own "mail" subdomain and it's own certificate for the mail server portion so that I can still have clients connect to mail.<domain>.<tld> without impact since that's what I have told a dozen or so to do already over the last 1.5 years. And no, the decision wasn't anything to do with Cloudron or DigitalOcean really. My main reason for the move away from DigitalOcean isn't anything to do with Cloudron or DigitalOcean. If you're curious... the decision was mostly for two reasons: A movement from both myself and my clients to keep everything (as much as possible) in Canada. And my current DNS provider (LunaNode) has their infrastructure in Canada only (well France too, I believe). It's one of those "shop local" sort of things. The DNS provider I currently use has a great feature that I can take advantage of in the future when running a secondary Cloudron server as a mirror image of the first one (waiting for that clustering capabilities in the future, hint hint haha). The advantage is that they have monitoring tools I can use, and based on those monitoring tools they can automatically update DNS records to the other IP address if monitoring detects one of the servers as "down" for whatever reason. To me this is like the health checks in load balancing, but I don't have to pay for load balancing with this solution. I see this as a further advantage to using LunaNode for the DNS management. So yeah, nothing to do with Cloudron or DigitalOcean really, so no worries there. Just a decision made for various reasons (the biggest two above, but also a bit of my own OCD and others haha). I will keep my primary domain on DigitalOcean then for now if you think the SSL cert for the mail subdomain would arrive in the next couple of months. Because I think that's a fantastic idea, and I think that was something I mentioned or questioned back when I started using Cloudron because I was so surprised that it had to be "my." as that's not something that conforms to the standards of mail server hostnames, and I wanted to keep things more standard for my clients to avoid having to explain non-standard implementations. I say standard loosely here as I realize there's no official standard, but it's more a de-facto one that mail. is the subdomain to use, or imap., etc. Hope that helps.

@girish This is intentional because the root domain record can be in use on another server/app/website. Right, that makes sense. I added a redirect from the root domain and it solved all my problems. Thanks for the quick help.

@nebulon Big fan of Dark Mode, thanks for your work to add it!