Email not pass the email server validation

Hi team,

i have rare issue with one email mmgnservices.net after check the email server on https://www.mail-tester.com/ i got the result very low 3.5 of 10.
after check the errors it say not MX record for mail.mmgnservices.net and not A record for mmgnservices.net.
but both record exist in hestia under DNS i dont know what is the issuee any help with that?

Do you’ve got a proper setup for your nameservers? Or do you use a external service for dns?

yes i have proper nameserver also i have under same heatia other 2 domain with emails accounts same nameserver and work fine just mmgnservices.net has issue

look this
MMGNSERVICES.NET
https://mxtoolbox.com/SuperTool.aspx?action=mx%3Ammgnservices.net&run=toolpage

HAVANACAFE863.COM

https://mxtoolbox.com/SuperTool.aspx?action=mx%3Ahavanacafe863.com&run=toolpage

both sites have same name server ns158.servivoip.dns.com and ns159.servivoipdns.com

if you want to use the hestia-server as your dns-server for your domain you need to have your domains ns-records pointing to it. as the mxtoolbox results show, your domains have no such thing, hence there is no name-resolution happening at all.

check with your domain-provider, how to setup external DNS addresses for your domains correctly :wink:

PS: https://www.name.com/support/articles/205934547-Changing-nameservers-for-DNS-management

1 Like

PPS: neither the servers ns158.servivoip.dns.com (typo with the dot?)
nor ns158.servivoipdns.com or ns159.servivoipdns.com do have their own nameserver resolution set up (or at least propagated yet) properly.

i think is BIND issue is under hestia any command line to check DNS by terminal?

nslookup is the way to go

fixed i have created two new NS ns160.servivoipdns.com and ns161.servivoipdns.com and set both to mmgnservices.net on name.com.

now i got this error DKIM Signature Verified Signature Did Not Verify

v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mmgnservices.net; s=mail; h=Message-ID:Subject:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=9S1XoNEHVXjTmYxMGWdGngusbgNKMBhlxn/sDQggVZQ=; b=ipMr7R1FWk1c/p0sg/52TOaQj +M3iVCk6VACF2F8T33tsiuB/azvIl2ut9WYs9i9U4f/Pjax87vx40o2oX2Gulaa0m6S0T7Ymj12RZ Yn+S50O81rNYlWRO9vFxgRLHTUDFE7HWAAGrlAblBgol/aWvhA72bPDqf1EF0vkpu+dhE=;

you can check the DKIM entry of your domain with the v-list-mail-domain-dkim-dns command from your console… mxtoolbox does not find any DKIM entry at all right now, so you either disabled it in the meantime or didn’t enable/propagate one?

OK i have checked and look valid DKIM

why when i will setup my email client i cant setup POP and SMTP with my domain mmgnservices.net i have generated SSL for it on WEB and Mail.
i are getting this error
Unrecognized Certificate
hostname on certificate didnt match mmgnservices.net != hcp.servivoipdns.com

Reject Key or Accept Key

If i setup with hcp.servivoipdns.com it is OK work perfect

Please any update on this?

I just tested this on one of my productive servers, running hestia 1.0.6:

I’ve enabled mail ssl (you need to have webmail and mail.domain.tld dns records, then click edit mail, tick ssl and let’s encrypt box, save) and use the default dns and mail settings from hestia. With this settings, I’ve sent a mail from webmail.domain.tld to mailtester and get instantly a 10 out of 10:

OK i have checked and look valid DKIM

why when i will setup my email client i cant setup POP and SMTP with my domain mmgnservices.net i have generated SSL for it on WEB and Mail.
i are getting this error
Unrecognized Certificate
hostname on certificate didnt match mmgnservices.net != hcp.servivoipdns.com

Reject Key or Accept Key

If i setup with hcp.servivoipdns.com it is OK work perfect

why do you use mmgnservices.net instead of mail.mmgnservices.net? Please check to do a propper client setup.

Thanks dns record for mail.mmgnservices.net was missing.