使用 Amazon SES 和 Google Apps 的正确 SPF 记录是什么 [英] What is the correct SPF record for using both Amazon SES and Google Apps

问题描述

同时用于 Amazon SES 和 Google Apps 的正确 SPF 记录是什么:

What would be the correct SPF record to use for both Amazon SES and Google Apps together:

Google Apps 表示他们希望您在其中包含波浪号~":http://support.google.com/a/bin/answer.py?hl=zh-CN&answer=178723，但大多数其他示例使用短划线-"代替.

Google Apps says they want you to have the tilde "~" in it: http://support.google.com/a/bin/answer.py?hl=en&answer=178723, but most other examples have a dash "-" instead.

亚马逊想要:v=spf1 include:amazonses.com -all"

Amazon wants: "v=spf1 include:amazonses.com -all"

Google 希望:v=spf1 包括:_spf.google.com ~all"

Google wants: "v=spf1 include:_spf.google.com ~all"

我们目前有这个，将两者结合在一起:

We currently have this, combining both together:

TXT "v=spf1 include:amazonses.com include:_spf.google.com ~all"

TXT "v=spf1 include:amazonses.com include:_spf.google.com ~all"

SPF "v=spf1 include:amazonses.com include:_spf.google.com ~all"

SPF "v=spf1 include:amazonses.com include:_spf.google.com ~all"

1) 这是正确的 SPF 记录吗?

1) Is this the correct SPF record?

2) 我们是否遗漏了什么，对于 TXT 和SPF DNS 记录?这就是我们所拥有的，我们没有其他任何东西.

2) Are we missing anything, should this record be the exact same for both TXT & SPF DNS records? That is all we have, we don't have anything else.

我们只发送来自 Google Apps 和 Amazon SES 的电子邮件，不发送其他任何内容.

We only send email from Google Apps and Amazon SES, nothing else.

推荐答案

1. 发布 TXT 记录:

1. Publish a TXT record:

"v=spf1 include:_spf.google.com include:amazonses.com ~all"

Amazon SES 文档 说没有额外的 SPF 配置域所需，但结果证明将 include:amazonses.com 添加到记录会使 发件人 ID 也通过.即使发件人 ID 被考虑 过时，一些接收者可以实现它.

Amazon SES documentation says that no additional SPF configuration is required for a domain, but it turns out that adding include:amazonses.com to the record makes Sender ID pass as well. Even though Sender ID is considered obsolete, some receivers could implement it.

如果 Amazon SES 配置使用自定义 MAIL-FROM 子域，为子域发布另一个 TXT 记录:

If Amazon SES is configured to use a custom MAIL-FROM subdomain, publish another TXT record for the subdomain:

"v=spf1 include:amazonses.com ~all"

最好设置自定义子域以提高可交付性和客户体验.例如，域将显示在 Gmail 的 mailed-by 字段中.

It's good to have a custom subdomain set up for better deliverability and customer experience. For example, the domain will be displayed in the mailed-by field in Gmail.

您可以使用 -all 代替 ~all.在这种情况下，从 SPF 记录未涵盖的来源发送的电子邮件可能会被收件人拒绝.

You can use -all instead of ~all. In this case, emails sent from sources not covered in SPF record may be rejected by recipients.

根据 RFC 7208 的第 3.1 节:

According to Section 3.1 of RFC 7208:

SPF 记录必须仅作为 DNS TXT(类型 16)资源记录 (RR) [RFC1035] 发布.

SPF records MUST be published as a DNS TXT (type 16) Resource Record (RR) [RFC1035] only.

因此，SPF 记录类型现已过时.

Thus, SPF record type is now obsolete.

关于您的评论，这是一种测试 SPF 是否有效的简单方法:

Regarding your comment, here is one simple way to test whether SPF works:

• 从 Gmail 和 Amazon SES 测试电子邮件表单向 [e-mail] 发送电子邮件.
• 然后，搜索SPF check: pass的自动回复.

• Send emails to [e-mail] from both Gmail and Amazon SES Test Email form.
• Afterwards, search the automated reply for SPF check: pass.

这篇关于使用 Amazon SES 和 Google Apps 的正确 SPF 记录是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！