Does DA comes with Emails up and running out of the box?

sindinero

Verified User
Joined
May 4, 2022
Messages
8
Hi

We, got a VPS with DA pre-installed and we're finding the emails can't be sent.

Our sysadmins say the mail server has to be setup before emails can come and go from our VPS.

Im' amazed to find out that this control panel does not come with email system pre-installed or pre-configured.

Does it has to be really set up by the end users (us)? Or am i missing something?

In case it has to be completely configured by us, could you point us to a comprehensive explanation on how to do that?

Thanks to anybody taking the time to reply on this question.

Best regards.
AI
 
Unless your VPS has some kind of special requirement (like they block the normal set of email ports), as @Active8 says, add domain, add email addresses - DA does this "out of the box".
 
Hello, thanks.

We got mail.domain.tld resolving to this VPS's ip address.

The email accounts are working through the mail server already, so that's not a problem anymore.

However, when emails are sent to external address, they come with a warning saying the SSL certificate could not be verified.

I just looked at the certificate and it says the mail server is using a valid certificate.

The warning about the SSL not verified appears in Outlook, iphones, and Gmail as well.

This is what gmail says about it:

What could be causing these issues?

Best regards.
AI
 
What is the exact warning your receive? Is is about about SSL (encryption) or about authentication? If it's about authentication, it probably means you don't have DKIM and/or SPF set up. And indeed, if I do a DNS check of the domain in your sslshopper.com link, these records don't seem to be present.

1) DKIM: enable it in Directadmin (under E-Mail accounts), copy the x._domainkey.yourdomain.com TXT-record from your Directadmin DNS zone to your zone at GoDaddy
2) SPF: add a valid SPF-record containing the IP of your server to your zone at GoDaddy
 
Thanks a lot, I can confirm that DKIM and SPF records where added to the DNS zone at godaddy as suggested.

Now emails arrive without warning.

However, when configuring the email account in Outlook we get a warning message saying that the SSL certificate can't be proved.

You can take a look in the images attached to this message, thanks a lot for your time and help.
 

Attachments

  • SSL-Certificate2.PNG
    SSL-Certificate2.PNG
    130.9 KB · Views: 8
  • SSL-Certificate1.PNG
    SSL-Certificate1.PNG
    156.6 KB · Views: 9
Seems like your mail clients are seeing your server hostname certificate vps.domain.com instead of your domain certificate mail.domain.com, which causes a certificate common name mismatch. You can either

- use your server hostname vps. as incoming / outgoing mailserver or
- generate a LE certificate including the mail. subdomain for your domain under SSL Certificates
 
Not clear in your screenshots, but you are using mail.sindinero.mx as incoming and outgoing server?
 
I see an DNS issue

MX
Error
MX RecordsOh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
 
I can confirm that DKIM and SPF records where added to the DNS zone at godaddy as suggested.
And on your DA box I hope, because they have to be there too for Exim to work with them.

Then, like @Active8 said, no MX record present.
And last, no correct rDNS/PTR record present. At this time your rDNS/PTR record is pointing to some hosted.by.domain.com but it should point to either your hostname (vps.domain.com) or your mail server mail.domain.com.
So that also needs to be fixed.
 
Back
Top