SSL Certificate

[nwww993]

Hello,
I want to know if DirectAdmin provides an SSL Certificate? If so, how do I get it and how do I install it? If not, where can I get an SSL Certificate and how would I install it on my panel. I want to make my website secure (all my forwarded emails go to spam due to this problem). I greatly appreciate any help I can get. Thanks.

 

[Richard G]

Hi.
Directadmin supports Letsencrypt as SSL Certificates
Check this:

Let's Encrypt For Domains | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

and

Automatic TLS Certificate For Server Hostname | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

all my forwarded emails go to spam due to this problem

That's almost certainly not due to SSL certificates, probably more likely due to (maybe missing) SPF and DKIM records.

Be aware that forwarding is not the best practice. Forwards tend to get into spamboxes more often. Because the forwarding system is not the original system, which is often treated as suspicious.
So you have to setup a good SPF, DKIM and DMARC system to have this prevented as far as possible.

 

[nwww993]

Hi.
Directadmin supports Letsencrypt as SSL Certificates
Check this:

Let's Encrypt For Domains | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

and

Automatic TLS Certificate For Server Hostname | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

That's almost certainly not due to SSL certificates, probably more likely due to (maybe missing) SPF and DKIM records.

Be aware that forwarding is not the best practice. Forwards tend to get into spamboxes more often. Because the forwarding system is not the original system, which is often treated as suspicious.
So you have to setup a good SPF, DKIM and DMARC system to have this prevented as far as possible.

Thank you for your reply, Richard. I'm not very experienced with all this, so I will take your advice and learn more about SPF and DKIM records to see if it will solve my problem. But the reason why I assumed it was my SSL Certificate is that when I used the forwarding feature in Gmail, it would not allow me to use TSL or SSL on either port 587 or 465 (Server returned error: "TLS Negotiation failed, the certificate doesn't match the host., code: 0") or (Couldn't reach server. Please double-check the server and port number.). It only allowed me to use port 25 with "Unsecure Connection".

 

[Richard G]

Ah I understand now what you mean. You might indeed be correct in that case.
But mailservers (so your server) connect with other mailservers on port 25. So I don't know where you get that notice from because the mailserver should not make a connection with gmail on port 587 or 465, unless your datacenter closed port 25.

when I used the forwarding feature in Gmail

You mean forward a mail to your mailserver? I never used that option myself.

You could start to create an SSL certificate for your hostname. It's good to have that anyway. So install letsencrypt and then check the 2nd link so you have a SSL certificate for your hostname, it's always good to have one anyway.
Maybe that also fixes your issue when connecting over a client port (465 or 587) instead of the server port.

 

[nwww993]

Ah I understand now what you mean. You might indeed be correct in that case.
But mailservers (so your server) connect with other mailservers on port 25. So I don't know where you get that notice from because the mailserver should not make a connection with gmail on port 587 or 465, unless your datacenter closed port 25.


You mean forward a mail to your mailserver? I never used that option myself.

You could start to create an SSL certificate for your hostname. It's good to have that anyway. So install letsencrypt and then check the 2nd link so you have a SSL certificate for your hostname, it's always good to have one anyway.
Maybe that also fixes your issue when connecting over a client port (465 or 587) instead of the server port.

thank you Richard for the informative reply. The reason why I used port 465 or 587 is that when I registered the emails with my domain it told me that my port was 587. But when I tried it only port 25 was functional and it told me that it is not secure. Now I will follow your advice and go ahead with the SPF and DKIM records and see if my problem will get resolved. And I also want to mention that I used to use my domain email provider on my previous website and had serious problems with spam and lack of storage. This is why I have decided to go ahead with Gmail as my mailserver since it has better filters and a lot more storage. I thank you again and will bother you again if my problem persists

 

[Richard G]

The reason why I used port 465 or 587 is that when I registered the emails with my domain it told me that my port was 587.

That is correct, but that is for use with an e-mail client. In that case you indeed need a SSL/TLS certificate to make use of those ports. I was under the impression that you were talking about server to server transfers from mail.
In some cases port 587 can be used without ssl/tls but best is to use it. In that case you indeed have to create ssl/tls certificate for your domain, which is also shown in one of the links if I'm correct.

If you are using a hoster, so the domain for your website, it's mostly that the storage space their is less then what you get with Gmail.