域报告被拒绝没有明显的原因

问题描述

有人能解释一下谷歌(和其他人)在这里抱怨的是什么吗?在 policy_published 下有一个拒绝,但其他一切都通过。非常感谢您的任何建议!

有关信息:我们确实有用于接收邮件的邮件服务器 (mail.berlepsch.com),但我们通过亚马逊的 ses(简单电子邮件服务)发送邮件。

<?xml version="1.0" encoding="UTF-8" ?>
<feedback>
  <report_metadata>
    <org_name>google.com</org_name>
    <email>noreply-dmarc-support@google.com</email>
    <extra_contact_info>https://support.google.com/a/answer/2466580</extra_contact_info>
    <report_id>2189708791472768567</report_id>
    <date_range>
      <begin>1625356800</begin>
      <end>1625443199</end>
    </date_range>
  </report_metadata>
  <policy_published>
    <domain>schlossberlepsch.de</domain>
    <adkim>r</adkim>
    <aspf>r</aspf>
    <p>reject</p>
    <sp>reject</sp>
    <pct>100</pct>
  </policy_published>
  <record>
    <row>
      <source_ip>54.240.8.80</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>pass</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>schlossberlepsch.de</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>schlossberlepsch.de</domain>
        <result>pass</result>
        <selector>rbg4amwunrsndx5cvm374lmc7lodm5by</selector>
      </dkim>
      <dkim>
        <domain>amazonses.com</domain>
        <result>pass</result>
        <selector>ug7nbtf4gccmlpwj322ax3p6ow6yfsug</selector>
      </dkim>
      <spf>
        <domain>mail.schlossberlepsch.de</domain>
        <result>pass</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>54.240.8.45</source_ip>
      <count>2</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>pass</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>schlossberlepsch.de</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>schlossberlepsch.de</domain>
        <result>pass</result>
        <selector>rbg4amwunrsndx5cvm374lmc7lodm5by</selector>
      </dkim>
      <dkim>
        <domain>amazonses.com</domain>
        <result>pass</result>
        <selector>ug7nbtf4gccmlpwj322ax3p6ow6yfsug</selector>
      </dkim>
      <spf>
        <domain>mail.schlossberlepsch.de</domain>
        <result>pass</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>54.240.48.130</source_ip>
      <count>2</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>pass</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>schlossberlepsch.de</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>schlossberlepsch.de</domain>
        <result>pass</result>
        <selector>rbg4amwunrsndx5cvm374lmc7lodm5by</selector>
      </dkim>
      <dkim>
        <domain>amazonses.com</domain>
        <result>pass</result>
        <selector>ug7nbtf4gccmlpwj322ax3p6ow6yfsug</selector>
      </dkim>
      <spf>
        <domain>mail.schlossberlepsch.de</domain>
        <result>pass</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>54.240.8.99</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>pass</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>schlossberlepsch.de</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>schlossberlepsch.de</domain>
        <result>pass</result>
        <selector>rbg4amwunrsndx5cvm374lmc7lodm5by</selector>
      </dkim>
      <dkim>
        <domain>amazonses.com</domain>
        <result>pass</result>
        <selector>ug7nbtf4gccmlpwj322ax3p6ow6yfsug</selector>
      </dkim>
      <spf>
        <domain>mail.schlossberlepsch.de</domain>
        <result>pass</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>54.240.48.131</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>pass</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>schlossberlepsch.de</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>schlossberlepsch.de</domain>
        <result>pass</result>
        <selector>rbg4amwunrsndx5cvm374lmc7lodm5by</selector>
      </dkim>
      <dkim>
        <domain>amazonses.com</domain>
        <result>pass</result>
        <selector>ug7nbtf4gccmlpwj322ax3p6ow6yfsug</selector>
      </dkim>
      <spf>
        <domain>mail.schlossberlepsch.de</domain>
        <result>pass</result>
      </spf>
    </auth_results>
  </record>
</feedback>

解决方法

暂无找到可以解决该程序问题的有效方法,小编努力寻找整理中!

如果你已经找到好的解决方法,欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@)

相关问答

错误1:Request method ‘DELETE‘ not supported 错误还原:...
错误1:启动docker镜像时报错:Error response from daemon:...
错误1:private field ‘xxx‘ is never assigned 按Alt...
报错如下,通过源不能下载,最后警告pip需升级版本 Requirem...