Back to Community Threads
10
SSL-hostname prefix on a per-domain basis
Idea shared by Stephan Hafner - 1/3/2024 at 4:16 AM
Proposed
Hi

I would like to have the option for each domain to determine or expand the SSL-hostname prefix on a per-domain basis.

It would help to reduce the request for let's encrypt.

Thx a lot
Stephan

3 Replies

Reply to Thread
1
+1
Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
1
+1
Sabatino Traini Chief Information Officer Genial s.r.l. Martinsicuro - Italy
1
After various tests I decided that for the moment I will update without using the automatic generation of certificates, but maintaining the old model with certifytheweb


I firmly believe in the need to decide for each domain whether or not to activate SSL on a personalized hostname, but also to be able to decide for each domain which hostname to use (inheriting from the default domain)

Tests are not made differently even using hybrid situations, buying certificates. As you can see here

I had several difficulties with using wildcard certificates and I had to find a workaround to make everything work.

I await future developments
Sabatino Traini Chief Information Officer Genial s.r.l. Martinsicuro - Italy
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Configure an Alternative Linux Web Server for SmarterMailSmarterMail > Server Configuration and Management
Configure a Smarthost Gateway in SmarterMailSmarterMail > Server Configuration and Management
Multiple Automatic SSL Certs for the Same HostnameSmarterMail > Troubleshooting
Automatic SSL Certificates on a New SmarterMail ServerSmarterMail > Server Configuration and Management
Troubleshooting SmarterMail Automatic SSL CertificatesSmarterMail > Troubleshooting