Your own addresses for webmail and more
A team can give its people addresses on its own domain: webmail at mail.acme.com, the team manager at admin.acme.com, and (with those features) the public forums at forum.acme.com and the public wiki at wiki.acme.com. Each opens at the root of its address, with its own certificate.
Setting one up
- The name must be on one of the team's proven domains (a domain verified with its ownership record).
- In your DNS, add a CNAME from the name to the target the team manager shows (the platform's
sites.name, or the server's host name). A name that cannot have a CNAME, such as a domain's own apex, can instead point at the same addresses as the target. - In the team manager, Your own addresses on the team page: enter the names and choose Save addresses. Each is checked at once.
The card shows each name's check: points here, or not yet with what DNS has. Names are checked again every 30 minutes until they point here, and daily after that; Check now checks at once. Webmail and team manager names are used only once a check finds them pointing here, so the server never asks for a certificate it cannot get; the certificate is issued at the first visit.
From the command line:
corpsuite tenant sites set acme mailHost=mail.acme.com manageHost=admin.acme.com
corpsuite tenant sites check acme
Good to know
- Signing in on your own address is separate from the platform's own webmail address: a browser signed in on one is not signed in on the other.
- Links in mail the platform sends (password resets, invitations) still use the platform's addresses.
- A name is one site's: the same name cannot be both webmail and forums, or used by two teams.
- The operator sets the target under Settings → Host names and HTTPS (Teams point their own addresses at), for example
sites.mailo.citypointed at the server, so the server's own name can change without every team changing its DNS.
For the operator: a wildcard certificate
With DNS-01 set up (CORPSUITE_ACME_DNS_PROVIDER and CORPSUITE_ACME_DNS_ZONE, see Certificates), the server also keeps a wildcard certificate for its zone (*.mailo.city), and for the team-site bases under it (*.f.<base>, *.d.<base>). Every portal host and every <team>.f.<base> address is then served with it, with no certificate to issue per name.