cPanel & WHM Version 102 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Remove Mail Subdomain from AutoSSL

oldchili shared this idea 7 months ago
Not Planned

I would like to completely remove mail. subdomain from AutoSSL. I've disabled the "Service subdomains" option in WHM >> Tweak Settings, but AutoSSL still creates the mail subdomain.

I think we should have an exclusive list of what subdomains AutoSSL will control.

Replies (6)

photo
1

While there isn't a global option to control this, you can choose what domains are covered in the cPanel >> SSL/TLS Status page.

photo
1

Yes, we use that. But I think at a higher level excluding this mail subdomain altogether makes more sense. I don't think we should assume that all customers use mail. I know for us, we have 0 mail accounts and never use cPanel for mail.

photo
2

That makes sense - I've updated the status now.

photo
1

This would be great!

It'd also maybe be good to have an easy way to disable it on multiple accounts with that subdomain already set, even if it was doable through shell. We—as I imagine others will too—have hundreds of websites with mail subdomain AutoSSL coverage already set due to this default even if the mail is not there, so it's either barrage of emails about "potential reduced coverage" or update manually every single account as they pop up.

photo
1

Yea, I am having this issue on websites that don't even have a mail subdomain, even in the DNS. Maybe they did at one point but not anymore so being able to remove it right from the AutoSSL interface would be amazing. Just really tired of getting an inbox full of SSL failure messages, which makes it really difficult to know which ones are website breaking or just inbox busting.

I had to resort to just disabling all the email notifications from AutoSSL for now which is clearly not a great option. Since now I have to manually track any issues with SSLs.

photo
1

We have some ideas in the future that we hope will better solve the root problem here. It's not currently on our roadmap, but it is definitely on our radar to make sure this kind of situation doesn't happen to administrators in the future when changes occur that could cause a false negative like many experienced with the recent AutoSSL changes.

Leave a Comment
 
Attach a file