Skip to content

is my DMARC configured correctly?

Solved Configure
  • 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
  • @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
  • How to deploy WordPress.org Developer theme

    Solved Configure
    4
    1 Votes
    4 Posts
    293 Views

    @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
    3
    1 Votes
    3 Posts
    180 Views

    You might want to also review this post

    https://sudonix.org/topic/389/mongodb-backup-script

  • Getting Eror When Started NodeBB

    Solved Configure
    7
    2 Votes
    7 Posts
    368 Views

    @phenomlab yes i did.

    i deleted one of plugin then it started to work normally.

  • mongodb replica set

    Configure
    11
    2 Votes
    11 Posts
    370 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?

  • Upgrade issues

    Solved Configure
    2
    2 Votes
    2 Posts
    142 Views

    Use this code

    git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x

    And you will have the latest version without specifying it

    https://docs.nodebb.org/configuring/upgrade/

  • Code block hard to read with light theme

    Solved Configure
    9
    2 Votes
    9 Posts
    282 Views

    @Panda I see why - if you check the browser console, there’s an error logged there. This is from one of my VM’s

    image.png

    There is a decision tree that pulls the value of the editor theme from the saved browser settings on each load, but that fails if the theme has never been changed, and the user has the default (in your case, you are using light mode, so it serves “flatly” by default, but the editor itself is never set and returns null

    This below code changes that

    /* If savedTheme is undefined it will return null - based on this, we assume that the user has the default theme selected and never changed it, so we'll need to force that here */ if(!savedTheme) { var savedTheme = "flatly"; }

    If you reload your browser and test again, it should work properly.

  • 6 Votes
    36 Posts
    2k 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.

  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    796 Views

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