Skip to content

is my DMARC configured correctly?

Solved Configure
3 2 793
  • 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>
    

    @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.

  • Hariundefined Hari has marked this topic as solved on
  • phenomlabundefined 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.

    @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? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • Spam spam spam

    Solved Configure nodebb
    6
    2 Votes
    6 Posts
    508 Views
    @Panda said in Spam spam spam: ok, yes Ive seen the queue, it shows IP, but doesnt have a field for comments from registrant. It’s not designed for that. It merely serves as a gateway between posts appearing on your form or not. @Panda said in Spam spam spam: It would be better if nodebb had this plugin included in ACP list, as not only then do you know its approved and should work, but many people cant or dont want to use CLI on the server That’s a question for the NodeBB devs but in all honesty you can’t not use the CLI when installing nodebb so to be this isn’t a big deal.
  • Opening links in nodebb widget

    Solved Configure nodebb
    6
    4 Votes
    6 Posts
    1k Views
    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe> This works first time every time on your site as intended.
  • MogoDB v6 to v7 upgrade

    Solved Configure nodebb
    5
    1 Votes
    5 Posts
    865 Views
    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.
  • mongodb backup problem

    Moved Configure mongodb
    3
    1
    1 Votes
    3 Posts
    563 Views
    You might want to also review this post https://sudonix.org/topic/389/mongodb-backup-script
  • Getting Eror When Started NodeBB

    Solved Configure bug
    7
    1
    2 Votes
    7 Posts
    855 Views
    @phenomlab yes i did. i deleted one of plugin then it started to work normally.
  • mongodb replica set

    Configure mongodb docker ansible
    11
    2 Votes
    11 Posts
    1k Views
    @veronikya said in mongodb replica set: The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly Solution: Edit the /etc/resovel.conf file Add 127.0.0.53 One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?
  • 6 Votes
    36 Posts
    4k Views
    @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.
  • help me configuring cron job for fof/sitemap - flarum

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