Skip to content

is my DMARC configured correctly?

Solved Configure
3 2 1.9k
  • wrote on last edited by phenomlab
    #1

    Recently i have followed elastic email DMARC generator https://elasticemail.com/dmarc and configured at my DNS

    bd5b1b71-a564-4b16-9b71-2f35b91cf4b9-image.png

    emails are going to inbox, spf and all everything is working fine.

    But Google has sent me this email and I could not understand it. what does it mean?

    it has some xml file saying everything is pass does this mean it just a monthly or weekly email update?

    e9433582-35c1-4f56-ad59-79fd4ae87390-image.png

    <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>1611736858736883544</report_id>
    <date_range>
    <begin>1632441600</begin>
    <end>1632527999</end>
    </date_range>
    </report_metadata>
    <policy_published>
    <domain>mydomain.com</domain>
    <adkim>s</adkim>
    <aspf>s</aspf>
    <p>none</p>
    <sp>none</sp>
    <pct>100</pct>
    </policy_published>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>2</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>900.40.50.60</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>100.000.00.90</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>77.777.77.78</source_ip>
    <count>4</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    </feedback>
    
  • Recently i have followed elastic email DMARC generator https://elasticemail.com/dmarc and configured at my DNS

    bd5b1b71-a564-4b16-9b71-2f35b91cf4b9-image.png

    emails are going to inbox, spf and all everything is working fine.

    But Google has sent me this email and I could not understand it. what does it mean?

    it has some xml file saying everything is pass does this mean it just a monthly or weekly email update?

    e9433582-35c1-4f56-ad59-79fd4ae87390-image.png

    <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>1611736858736883544</report_id>
    <date_range>
    <begin>1632441600</begin>
    <end>1632527999</end>
    </date_range>
    </report_metadata>
    <policy_published>
    <domain>mydomain.com</domain>
    <adkim>s</adkim>
    <aspf>s</aspf>
    <p>none</p>
    <sp>none</sp>
    <pct>100</pct>
    </policy_published>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>2</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>200.100.45.55</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>900.40.50.60</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>100.000.00.90</source_ip>
    <count>1</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>default</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    <record>
    <row>
    <source_ip>77.777.77.78</source_ip>
    <count>4</count>
    <policy_evaluated>
    <disposition>none</disposition>
    <dkim>pass</dkim>
    <spf>pass</spf>
    </policy_evaluated>
    </row>
    <identifiers>
    <header_from>mydomain.com</header_from>
    </identifiers>
    <auth_results>
    <dkim>
    <domain>mydomain.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <dkim>
    <domain>elasticemail.com</domain>
    <result>pass</result>
    <selector>api</selector>
    </dkim>
    <spf>
    <domain>mydomain.com</domain>
    <result>pass</result>
    </spf>
    </auth_results>
    </record>
    </feedback>
    
    wrote on last edited by
    #2

    @hari nothing to worry about there. When you setup DMARC, it will also ask for an email address to send daily reports to. Google won’t be the only one sending these - you’ll get one from every domain that receives email from yours. Typically, it makes sense to redirect these to an unattended mailbox so they don’t clog up your main mailbox.

  • Hari Hari has marked this topic as solved on
  • phenomlab phenomlab unlocked this topic on
  • @hari nothing to worry about there. When you setup DMARC, it will also ask for an email address to send daily reports to. Google won’t be the only one sending these - you’ll get one from every domain that receives email from yours. Typically, it makes sense to redirect these to an unattended mailbox so they don’t clog up your main mailbox.

    wrote on last edited by Hari
    #3

    @phenomlab said in is my DMARC configured correctly?:

    you’ll get one from every domain that receives email from yours.

    Today I have received another mail from outlook DMARC, i was referring to your reply again and found it very helpful/informative. thanks again.

    I wish sudonix 100 more great years ahead!


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Nodebb and emails

    Solved Configure nodebb
    27
    5 Votes
    27 Posts
    10k Views
    phenomlab
    @Panda it will use SMTP. In all cases, I never use any plugin to send email. I’ll always send it raw.
  • Test of youtube embeds

    Solved Configure nodebb
    14
    11 Votes
    14 Posts
    5k Views
    Sampo2910
    @phenomlab Perfect!!! Many thanks.
  • How to deploy WordPress.org Developer theme

    Solved Configure wordpress theme github
    4
    1 Votes
    4 Posts
    3k Views
    phenomlab
    @Hari the real issue here is that I don’t think it can be used as a theme for WordPress because of the dependencies it clearly has, including its own Web server. My view here is that this is designed to be a complete development environment outside of the WordPress core.
  • mongodb backup problem

    Moved Configure mongodb
    3
    1
    1 Votes
    3 Posts
    1k Views
    phenomlab
    You might want to also review this post https://sudonix.org/topic/389/mongodb-backup-script
  • 6 Votes
    36 Posts
    15k Views
    phenomlab
    @justoverclock said in Digitalocean step by step guide to nginx configuration: i’m learning And that’s the whole point of this site If you don’t learn anything, you gain nothing.
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    5k Views
    phenomlab
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • how to change flarum configuration from apache to nginx?

    Solved Configure flarum
    3
    0 Votes
    3 Posts
    1k Views
    phenomlab
    See https://sudonix.com/topic/226/issues-getting-flarum-to-work-on-new-host/28?_=1645013723672
  • help me configuring cron job for fof/sitemap - flarum

    Solved Configure
    36
    18 Votes
    36 Posts
    13k Views
    DownPW
    you are too fast