My understanding of Axigen, it allows even the free use license to support multiple domains. I personally have three domains I host at home, and those domains point to my IP.
However, SSL port assignments are only allowing one SSL cert to be assigned, and I have not been able to find where multiple domains can use their own SSL certificate.
For instance, the primary domain (domain1) with what I started, I can grab an LE SSL cert for that domain, and can assign the cert to the secure ports for secure authentication.
But domain2 and domain3, which are also hosted on the same server, aren’t allowed to use their certs. This causes an error in Outlook if I have more than one domain email address to connect to and get information - i.e, it only sees domain1 cert, even though I may have the other SSL certs on the mail server.
So I am confused - does the server actually support multiple domains or not? Or is this just a subdomain support system where we are only allowed one domain, with one certificate, but multiple subdomains? Am I missing something where I can use different domains with their respective certificates?
There is no mandatory requirements to access the data for domainX via a dedicated hostname bounded to that domain name. This means that you may use an access point related to domain1 (for example mail.domain1.tld) for domain1.tld but for other ones as well (like domain2.tld or domainY.tld).
I understand your point of view that it will be nice to have dedicated access points for each hosted domains (like mail.domainZ.tld for domainZ.tld) but this is very hard to maintain when you are hosting more domains (like more than 50) and when not all domains are under your control.
The way a single listener (like one set for IMAPS, like 1.2.3.4:993) will be able to handle more SSL certificates it is via SNI - and Axigen is currently supporting this only for WebMail service (check the Virtual Hosts section from that service).
There is a feature request posted on Axigen Product Community (here) for extending the SNI for the other protocols (like SMTP, IMAP and POP3) but till now it has only 12 votes.
The simple way to support SNI for the other services is to delegate the SSL part to a locally installed 3rd party software that is supporting SNI (like stunnel) and let the Axigen process the locally unencrypted traffic.
Thank you for the information. So, then really it doesn’t support multiple domains unless you’re just using Webmail. I don’t want to have to setup yet another service for something that by all standards, should be supported, or have been developed. It’s like it was developed halfway then stopped because… webmail is good enough?
The voting system is frankly … well, moot. Either it’s developed or it isn’t.
Regardless, thank you for this, I’ll need to find a different mail system supporting this feature.
Thank you from me too. I just spent six or so hours wondering why I could not get IMAP working for the second domain on its own certificate. I can work around now that I know it cannot be done without a third party prop.