- Más nuevo
- Más votos
- Más comentarios
Hi,
From what I understand you have 2 services to send mail: Kinsta and WorkMail. You use Kinsta to send out automated mails but want to use WorkMail as well?
In that case the MX record is only used to receive mail. Do you need to receive mail in Kinsta? If not: you can create the same email address in WorkMail and use that to receive the mail in WorkMail by pointing your MX record to WorkMail. If you want to receive mail on both services you will need to configure a forwarding/redirection rule to redirect mail from 1 service to another.
Kind regards,
Robin
Thank you Robin,
It’s mainly our French website admin who does the things. But he’s English isn’t good enough to ask here directly. What I understand is, that he had to create a second MX record on Amazon, when we wanted to have access through WorkMail. (WorkMail to send and receive, Kinsta to send only)
That means, that he had to enter that second MX in Kinsta, too (to have the company name I guess). Our admin was concerned, that the second MX would overwrite the first on Kinsta.
But the Kinsta support told us, that 2 MX entries for the same e-mail address are possible.
So it seems to work now...
Hi,
I'm sorry if my explanation was not 100% clear. Its not recommended to have multiple MX records unless they deliver to the same service. A MX record is used by mail senders to see where to deliver your mail. If you have 2 MX records that deliver to different services, 1 service might receive mail that needs to go to the other one. Senders will pick 1 MX record (with the lowest priority) and try to delivery the email. Only if that one does not respond it will try the other one.
In your case, since Kinsta only needs to send mail you can use WorkMails MX record. I would still recommend to create a user in WorkMail with the email addresses used in Kinsta to ensure you still receive bounce messages from mails sent from Kinsta.
Kind regards,
Robin
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años