I have several users which using external email providers (gandi.net, ovh…) when the website it’s hosted by hestiaCP
The MX DNS are set correctly and that work fine.
But not for the mails sent from the hestiacp server to it’s own domain, for exemple from a contact form.
the contact form from the website domain.com can’t send mail to [email protected] because the server is trying to send it to himself instead of asking external MX
And that is the best practice, if you want the sent emails to have any chance to reach the inbox of the recipient. This is because most email providers reject non-authenticated emails, in an effort to combat spam. This can get pretty serious in situations of emails for password recovery emails and/or 2FA emails.
I was looking in the Web UI for the SMTP account for internal Hestia mails, but instead I found it on the command line with the commands v-add-sys-smtp and v-delete-sys-smtp. Just putting that information here, which may help others looking for that.