我如何让我的SPF“看到过去”我的 ISP 的无意义 A 记录？
我托管着一系列不同的域，它们都使用我的（一个）邮件服务器来发送和接收邮件。发送邮件时，有时我的邮件会被接收端拒绝，被标记为“可疑”，或者直接进入垃圾邮件文件夹。
此外，在入站时，我会从垃圾邮件的随机受害者那里收到大量“回执”，其中我的一个域名已被使用，即使邮件从未触及我的邮件服务器。
有人告诉我，这两个问题都源于这样一个事实，即我的 SPF 记录设置不正确，我已经尝试修复这一问题很长一段时间了。不幸的是，我对记录背后的机制和语法本身的基本知识有些陌生，这就是我在这里寻求帮助的原因。
出于以下示例的目的，假设进行以下设置：
- 我有两个域：
mydomain.com和myotherdomain.com。 - 这两个域都有活动子域，可以通过我的邮件服务器发送和接收邮件。
- 我的邮件服务器名为
mail.mydomain.com - 全部运行在同一台物理服务器上，IP 地址为：
85.81.xxx.xxx。 - 我的 ISP 有一个半静态 IP 地址，例如它永远不会改变，但可以说不是我自己的。
85.81.xxx.xxx上的 whois 会生成0x39Axxxx.dslpool.isp.com
使用位于 http://tools.bevhost.com/spf/ 我最终得出以下结论：
电子邮件来源：密码 -
85.81.xx.xx决心0x39Axxxx.dslpool.isp.com然后 再次解析为85.81.xx.xx。发件人详细信息：通过 -
[电子邮件受保护]指向 指向我的邮件服务器的 MX 记录 在mail.mydomain.net。主机名 HELO / EHLO：失败 -
mail.mydomian.not解析为85.81.xxx.xxx解析为0x39Axxxx.dslpool.isp.com
因此，问题是：如果可能的话，我将如何为 mydomain.com 编写 SPF 条目和 myotherdomain.com 忽略此冲突并允许我发送的邮件在收件人验证 spf 时显示为有效？
希望得到答复...
I host a spread of different domains that all use my (one) mail-server to send and receive mail. When sending mails, sometimes, my mail gets rejected by the receiving end, marked to the recipient as "suspicious" or simply heads straight for the spam folder.
Also, on the inbound, I get a load of "return receipts" from random victims of spam, where one of my domain names has been used even though the mail never touched my mail server.
I have been told, that both issues stems from the fact, that my SPF record is not set properly which i have been attempting to fix for quite a while now. Unfortunately my basic knowledge of the mechanisms behind the record and the syntax itself escapes me somewhat, which is why I'm looking here for help.
For the purpose of the following example, assume the following setup:
- I have two domains:
mydomain.comandmyotherdomain.com. - Both domains have active subdomains that send and receive mail through my mailserver.
- My mail server is named
mail.mydomain.com - All running on the same physical server with the IP address:
85.81.xxx.xxx. - I have a semi-static IP-address with my ISP, e.g. it never changes but is per say not mine to call my own. A whois on
85.81.xxx.xxxproduces0x39Axxxx.dslpool.isp.com
Using the tool found at http://tools.bevhost.com/spf/ i end up with the following conclusion:
Email Origin : Pass -
85.81.xx.xx
resolves to0x39Axxxx.dslpool.isp.comwhich then
again resolves to85.81.xx.xx.Sender Details : Pass -
[email protected]points to a
MX-record that points to my mail sever
atmail.mydomain.net.Host Name HELO / EHLO : Fail -
mail.mydomian.notresolves to85.81.xxx.xxxwhich resolves to0x39Axxxx.dslpool.isp.com
So, the question is: If at all possible, how would I compose the SPF entries for mydomain.com and myotherdomain.com to disregard this conflict and allow my sent mails to appear valid when spf validated by the receiver?
Hoping for a response ...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在这里，您的所有域的 DNS
v=spf1 +ip4:85.81.xxx.xxx -all中应该有此 SPF 条目，并且 SPF 字符串中没有其他内容。确保您有
mail.maydomain.com和mydomain.com这样的 DNS 条目，因为
mydomain.com的 SPF 条目对于subdomain.mydomain.com无效。如果您有许多子域，您可以考虑为
*.maydomain.com设置 SPF 条目。这将处理mydomain.com域的 sub 或 sub.sub 或 sub.sub.sub 等域的所有域树。Here you should have this SPF entry in your DNS
v=spf1 +ip4:85.81.xxx.xxx -allfor all your domains, and nothing more in your SPF string.Make sure that you have such a DNS entry for
mail.maydomain.comas well asmydomain.com,because the SPF entry for
mydomain.comis not valid forsubdomain.mydomain.com.If you have many subdomains,you may consider to have an SPF entry for
*.maydomain.com. That will take care of all the domain tree that are sub or sub.sub or sub.sub.sub etc. domains of the domainmydomain.com.