Cloudron Forum

@ianhyzy Yes, the explanation for this behavior is here - https://docs.cloudron.io/apps/nextcloud/#email (at the bottom). Happy to clarify further.

@d19dotca great, thanks 🙂

As long as the IP doesn't change from my. to mail. no clients need immediate reconfiguration.

The Reverse DNS is something that I also wanted to change for vanity reasons, but not at the expense of email.

Now I can. 👏 😹

@girish I originally tried that with no success, I figured that the Ghost CLI command initiated some other process or method

This is almost docs-worthy, under some kind of home-hosting section. 👍

why not simply manage a local cloudron.local domain in hosts or local DNS then?

@saikarthik said in IMAP port and server settings for LAMP app mail client:

What I blurred out in the picture is actually a valid cloudron mailbox ID.

Yes, but it seems there is some extra text before it like Test User: "Test User". Can you remove that and try?

added a Feature Request for #2 -- please upvote https://forum.cloudron.io/topic/5027/pop3-gmail-polling-support

@nebulon That's not to say that I don't think Cloudron shouldn't receive webhooks for other reasons. I'm surprised you aren't using them for your multi-cloudron dashboard actually (to update the status of "subcontainers" from all servers instantly).

@marcusquinn they don't , no.

This has helped me in version Cloudron v7.3.2

@p44 Where is this button? In the feeds or in preferences? I can't seem to find it in my installation.

@jdaviescoates ok, good

@girish That's awesome news! Looking forward to v6.0 then!

Keep up the awesome work 🙂

@marcusquinn I think DNS automation (provider specific) atleast needs to come from elasticemail itself ideally. It's not possible to keep track of all the DNS records each provider wants to set and if it's even available with API. It's basically impossible to test on our side atleast.

@girish Yes I did, and the problem with the certificates is now fixed. Thank you!

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

I've added a task in gitlab for this now at https://git.cloudron.io/cloudron/box/-/issues/738

This is implemented in Cloudron 6 ! https://forum.cloudron.io/topic/3205/what-s-coming-in-6-0-take-2/99

@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.