我如何使我的spf能够“查看过去"?我的isp的废话A记录? [英] How do i get my spf to "see past" my isp's non-sense A-record?

查看:116
本文介绍了我如何使我的spf能够“查看过去"?我的isp的废话A记录?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我托管了许多不同的域,它们都使用我的(一个)邮件服务器发送和接收邮件.在发送邮件时,有时,我的邮件会被接收方拒绝,标记为可疑",或者直接进入垃圾邮件文件夹.

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.

有人告诉我,这两个问题均来自以下事实:我的SPF记录设置不正确,这是我已经尝试了好一阵子了.不幸的是,我对记录背后的机制和语法本身的基本了解使我有些措手不及,这就是为什么我在这里寻求帮助.

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:

  1. 我有两个域:mydomain.commyotherdomain.com.
  2. 两个域都有活动的子域,可以通过我的邮件服务器发送和接收邮件.
  3. 我的邮件服务器名为mail.mydomain.com
  4. 所有运行在IP地址为85.81.xxx.xxx的同一台物理服务器上.
  5. 我的ISP有一个半静态IP地址,例如它永远不会改变,但可以说不是我自己的. 85.81.xxx.xxx上的 whois 产生0x39Axxxx.dslpool.isp.com
  1. I have two domains: mydomain.com and myotherdomain.com.
  2. Both domains have active subdomains that send and receive mail through my mailserver.
  3. My mail server is named mail.mydomain.com
  4. All running on the same physical server with the IP address: 85.81.xxx.xxx.
  5. 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.xxx produces 0x39Axxxx.dslpool.isp.com

使用在 http://tools.bevhost.com/spf/上找到的工具得出以下结论:

Using the tool found at http://tools.bevhost.com/spf/ i end up with the following conclusion:

电子邮件来源:通过-85.81.xx.xx 决心 0x39Axxxx.dslpool.isp.com然后 再次解析为85.81.xx.xx.

Email Origin : Pass - 85.81.xx.xx resolves to 0x39Axxxx.dslpool.isp.com which then again resolves to 85.81.xx.xx.

发件人详细信息:通过- myname@myotherdomain.net指向 指向我的邮件服务器的MX记录 在mail.mydomain.net.

Sender Details : Pass - myname@myotherdomain.net points to a MX-record that points to my mail sever at mail.mydomain.net.

主机名HELO/EHLO:失败- mail.mydomian.not解析为 85.81.xxx.xxx解析为 0x39Axxxx.dslpool.isp.com

Host Name HELO / EHLO : Fail - mail.mydomian.not resolves to 85.81.xxx.xxx which resolves to 0x39Axxxx.dslpool.isp.com

因此,问题是:如果可能的话,我将如何为mydomain.commyotherdomain.com组成SPF条目,以忽略此冲突并允许我发送的邮件在spf时显示为有效被接收方确认?

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?

希望得到回应...

推荐答案

在这里,您应该在DNS v=spf1 +ip4:85.81.xxx.xxx -all中为所有域都具有此SPF条目,而在SPF字符串中则没有其他内容.

Here you should have this SPF entry in your DNS v=spf1 +ip4:85.81.xxx.xxx -all for all your domains, and nothing more in your SPF string.

请确保您为mail.maydomain.commydomain.com都具有这样的DNS条目, 因为mydomain.com的SPF条目对于subdomain.mydomain.com无效.

Make sure that you have such a DNS entry for mail.maydomain.com as well as mydomain.com, because the SPF entry for mydomain.com is not valid for subdomain.mydomain.com.

如果您有许多子域,则可以考虑为*.maydomain.com提供一个SPF条目.这将照顾域mydomain.com的sub或sub.sub或sub.sub.sub等域的所有域树.

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 domain mydomain.com.

这篇关于我如何使我的spf能够“查看过去"?我的isp的废话A记录?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆