Create CNAME record for mail.<CloudronDomain> and get cert with SNIs to allow connections over various mail.<domains>
d19dotca last edited by
I think it'd be great if we could have users connect to mail.<theirDomain> instead of mail.<mainCloudronDomain>. Right now, they need to connect to something like mail.<mainCloudronDomain> instead of their own, which can create confusion and isn't as nice as it could be.
Setting up a CNAME alone isn't doable because the certificate shown by Cloudron mail.<mainCloudronDomain> needs to include the hostnames (via SNI I believe?) that matches the one they'd use in their mail clients such as mail.<theirDomain>.
Would love to see that functionality added to Cloudron along with setting up the CNAME records in all domains which aren't the primary domain so that each user on exampleA.com can connect to mail.exampleA.com instead of mail.<mainCloudronDomain>.
I like the idea. If I understand correctly, this feature is "Add domain aliases for email server" (similar to how apps have it).
d19dotca last edited by d19dotca
@girish Yes, that's a better way of saying it, haha. I wasn't really articulating myself as well as I normally do today. But yes, essentially making mail server aliases would be fantastic and allow for a better user experience especially for our own downstream customers.