Hello! So I just bought my account yesterday and am using my own personal test domain, so this isn’t a pressing issue but I was hoping to figure out what is going wrong before I move over my main email domains. I set up my DNS MX records for talanda.cloud and my CNAME records to route my domain mail.talanda.cloud and webmail.talanda.cloud to my appropriate mail server per the custom hostname tutorial (I’m on the arrow server). My server itself has a wildcart set from Let’s Encrypt for talanda.cloud and *.talanda.cloud so initially, the SSL settings under the Portal dashboard was set to “use server’s certificates” and I changed it to Let’s Encrypt for mail and webmail only. I then waited for it to propagate, tested the mail & webmail settings, and at this point I believe both mail and webmail worked on https (with mail just giving that apache is functioning message and webmail routing securely to roundcube)
So then I wanted to use Crossbox as my main webmail, so I followed that tutorial which changed both mail.talanda.cloud and webmail.talanda.cloud to mail.mxlogin.com in DNS. After that processed, I noticed the mail subdomain going to a page that said “That host is not allowed” on http, and https not working because it gave a BAD CERT error, where it says the cert found is only for mail.mxlogin.com. Adding an exception for that, it gives the same error on https. On webmail, the http version auto redirects to https, but the https also gives that same ssl bad cert error. Adding an exception again, the page loads but then the mail gives a loading error. After messing with that for a while I gave up and wanted to confirm the basic setup was at least still working, and I reverted mail and webmail back to the main arrow server directly. After that, webmail is back to working over https (for roundcube) but mail still doesn’t work on https (even though I understand that it’s not meant to be viewed with a browser but that confirms the cert isn’t applying), and the http version is back to saying apache is functioning rather than that host is not allowed.
For additional detail on Crossbox, I did go in and make an email@example.com account, I went and customized the branding, it did the test on checking the mail.talanda.cloud domain validity and approved & put my custom branding live. So all of that DID work, and I do see it when I went to webmail.talanda.cloud when I did have the DNS set as such, but the lack of the mail actually loading was obviously a deal breaker.
So I can go back and forth on my DNS settings (I’m using porkbun which was a super low TTL of 300 so it’s not that bad trying to make changes) and would be happy to try to walk through and figure out what caused this and what I need to do to resolve. I wonder if it was the swap from SSL settings from use server to let’s encrypt or something that went wrong in that. I saw another thread where jarland said fixing the issue involved recreating the whole account - since this is my test personal domain I have no problem redoing it if that’s the case, but I really do need to know what went wrong with all of this so I can pull over my more important domains successfully. I think I went over all my steps but please let me know if I can clarify and provide more information anywhere.