Page 1 of 1

Setting up mail server when DNS is managed externally

Posted: Sat May 18, 2019 10:27 am
by bhavilajain68

So after a few days of work, I've finally got vesta CP working the way I want it to. But now I'm facing problems with mail server.

I can log into roundcube and send mail, it would even show up as sent, but is not actually received by the recipient, nor can i receive any emails.
Coming from shared servers, This is the first time I'm having to do all these set-ups, so please dont mind and do include the "Obvious" steps that need to be taken.

Setup info : AWS lightsail | Ubuntu 16.04 | VestaCP v0.9.8-24
DNS is managed by GoDaddy (I could not get the DNS to propagate fully using vanity name servers, even after 4 days of just letting it sit.)

I did see the docs at -> How to properly set up a Mail Server
But This guide follows a setup for vanity nameservers.

So My question is what records do i need to put in GoDaddy in order to make the mail server work?

This is the "Health Report" form mxtoolbox

Also, I've enabled ports 25, 143 and 587 on the lightsail instance. Do I need to open any other ports to enable ssl/tsl encryption?

My primary requirement is to be able to send email from within PHP using a script. (The script works, I've tried it on BigRock shared server).

Thanks in advance. :)

Re: Setting up mail server when DNS is managed externally

Posted: Mon May 27, 2019 8:06 pm
by HenrysCat
You will need a reverse DNS record on godaddy and then copy the DMARC, DKIM and SPF records from the vestacp to your godaddy DNS settings exactly as they are on vesta although without the quotes, this is impotrant, next ask AWS to unblock port 25, they don't always block but will throttle it which also leads to problems sending mail.