Vesta Control Panel - Forum

I'm using CentOS 7.4 droplet on DigitalOcean
fresh build droplet, I installed VestaCP

I configured Lets enycrpyt SSL via Vesta. I've found DKIM in one of the server files (I googled the loaction) and also configured SPF. On https://www.mail-tester.com/ I got 10/10.

Why I can't receive any emails? everytime I want to send I get email back from [email protected] that says that address doesnt exist.

I don't know what to do.

all tests you did are for outbound mails: DKIM, SPF, and the mailtester.

What are you MX records set to?
Does the email account actually exist (typo's)?

vanderheyde wrote:all tests you did are for outbound mails: DKIM, SPF, and the mailtester.

What are you MX records set to?
Does the email account actually exist (typo's)?

I have added google MX records

and also one that is mail.example.com

my hostname on server is "mail.example.com"

Can you give me the exact DNS entries please? Including the priorities (you can alter your domain name, of course).

vanderheyde wrote:Can you give me the exact DNS entries please? Including the priorities (you can alter your domain name, of course).

MX example.com mail handled by mail.example.com. 10 14400
MX example.com mail handled by aspmx.l.google.com. 1 1800
MX example.com mail handled by alt1.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt2.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt3.aspmx.l.google.com. 10 1800
MX example.com mail handled by alt4.aspmx.l.google.com. 10 1800

This directs all emails to google instead of your vesta server. I'm assuming google does not know the domain you're working with and doesn't have the email accounts. Hence the error stating the user does not exist.

Try setting mail.example.com to the highest priority (lowest number). It'll take a few hours for the DNS entries to propagate accordingly :

MX example.com mail handled by mail.example.com. 1 14400
MX example.com mail handled by aspmx.l.google.com. 2 1800
MX example.com mail handled by alt1.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt2.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt3.aspmx.l.google.com. 10 1800
MX example.com mail handled by alt4.aspmx.l.google.com. 10 1800

vanderheyde wrote:This directs all emails to google instead of your vesta server. I'm assuming google does not know the domain you're working with and doesn't have the email accounts. Hence the error stating the user does not exist.

Try setting mail.example.com to the highest priority (lowest number). It'll take a few hours for the DNS entries to propagate accordingly :

MX example.com mail handled by mail.example.com. 1 14400
MX example.com mail handled by aspmx.l.google.com. 2 1800
MX example.com mail handled by alt1.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt2.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt3.aspmx.l.google.com. 10 1800
MX example.com mail handled by alt4.aspmx.l.google.com. 10 1800

Ok I will do that and take a look in the morning to see if the problem is solved. Thank you for your help!

vanderheyde wrote:This directs all emails to google instead of your vesta server. I'm assuming google does not know the domain you're working with and doesn't have the email accounts. Hence the error stating the user does not exist.

Try setting mail.example.com to the highest priority (lowest number). It'll take a few hours for the DNS entries to propagate accordingly :

MX example.com mail handled by mail.example.com. 1 14400
MX example.com mail handled by aspmx.l.google.com. 2 1800
MX example.com mail handled by alt1.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt2.aspmx.l.google.com. 5 1800
MX example.com mail handled by alt3.aspmx.l.google.com. 10 1800
MX example.com mail handled by alt4.aspmx.l.google.com. 10 1800

I LOVE YOU! Holy cow you saved me a lot of hair from being pulled out. Thank you thank you thank you