- 最新
- 最多得票
- 最多評論
Hello,
I was able to reproduce the same way you have your configuration. In order to resolve this, please correct the TXT record for the custom mail from.
Currently it is =>
$ dig TXT info.csportneuf.qc.ca +short
""v=spf1 include:amazonses.com ~all""
Please change that (in the value in your dns settings) =>
"v=spf1 include:amazonses.com ~all"
The TXT records for other custom mail from are set in the same manner. For example:
$ dig TXT info.cqsb.qc.ca +short
"v=spf1 include:amazonses.com ~all"
Please wait for the change to propagate and test it. This should fix the issue.
Regards,
Gaurav @ AWS
Hi Gaurav,
Thanks for your reply and sorry for replying that late but i seem to have missed the email notification when you replied. Just discovered you had answered me!
According to my issue, i want to make sure i understand the right usage of the "quote" character.
In the AWS console, when you generate entries for TXT domain validation, DKIM Cnames and MX records, you do not use any "quotes" characters around the value you generate except for the TXT record for the SPF entry where you actually include the "quote" into the following value
=> "v=spf1 include:amazonses.com ~all"
When i ask my customer to add those entries into his DNS for validation, shall i ask them to NOT include the "quotes" or should they? My probleme seems to happen when the customers includes the quotes when entering the value into his DNS. If so, why do you include the quotes only into this entry into the AWS console?