after clean install ubuntu+vesta, not receiving emails
Posted: Thu Feb 27, 2020 8:04 am
Hi all,
I have been browsing the forum for answers, but decided to start a new thread.
Just installed a clear VPS on ovh, choosing Ubuntu 18.04 and then installed vestacp:
bash vst-install.sh --nginx no --apache yes --phpfpm no --named yes --remi yes --vsftpd no --proftpd no --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav yes --softaculous no --mysql yes --postgresql no
of course i added hostname (vpsxxxxx.ovh.net), email and password to vesta.
Installation went successful.
Everything seems to work fine, I have added a new domain (i will call it domain.app - which is also registered with ovh and has A records pointing to that vps), enabled letsencrypt and then created a mail account for that domain.
Was able to send email from roundcube webmail and message arrived to both google-powered email and non-google powered email.
In both cases, when i reply (from google and non-google mail) i receive a mailer-daemon reply from remote server:
<[email protected]>:
Connected to 193.70.18.144 but sender was rejected.
Remote host said: 530 5.7.1 Client was not authenticated
That 193.70.18.144 ip address seems to be one from ovh, so it looks like the message is arriving but ovh servers are rejecting it. so i reckon i should be adding something to dns zone of that domain within ovh website.
Should i also change something in bind dns in vesta ? Bind dns for domain.app has ns1.domain.tld. and ns2.domain.tld.
Obviously ovh dns zone for that domain has different ns.
please assist
I have been browsing the forum for answers, but decided to start a new thread.
Just installed a clear VPS on ovh, choosing Ubuntu 18.04 and then installed vestacp:
bash vst-install.sh --nginx no --apache yes --phpfpm no --named yes --remi yes --vsftpd no --proftpd no --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav yes --softaculous no --mysql yes --postgresql no
of course i added hostname (vpsxxxxx.ovh.net), email and password to vesta.
Installation went successful.
Everything seems to work fine, I have added a new domain (i will call it domain.app - which is also registered with ovh and has A records pointing to that vps), enabled letsencrypt and then created a mail account for that domain.
Was able to send email from roundcube webmail and message arrived to both google-powered email and non-google powered email.
In both cases, when i reply (from google and non-google mail) i receive a mailer-daemon reply from remote server:
<[email protected]>:
Connected to 193.70.18.144 but sender was rejected.
Remote host said: 530 5.7.1 Client was not authenticated
That 193.70.18.144 ip address seems to be one from ovh, so it looks like the message is arriving but ovh servers are rejecting it. so i reckon i should be adding something to dns zone of that domain within ovh website.
Should i also change something in bind dns in vesta ? Bind dns for domain.app has ns1.domain.tld. and ns2.domain.tld.
Obviously ovh dns zone for that domain has different ns.
please assist