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 💗

  • 2 Votes
    11 Posts
    316 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?

  • Category For User

    Solved Configure
    11
    12 Votes
    11 Posts
    263 Views

    3.5.1 has now been released. I’ve just deployed it, so safe to do so!

  • 2 Votes
    18 Posts
    452 Views

    @Panda You’ll need to do that with js. With some quick CSS changes, it looks like this

    d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png

    The colour choice is still really hard on the eye, but at least you can now read the text

  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    773 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.

  • 0 Votes
    3 Posts
    257 Views

    See https://sudonix.com/topic/226/issues-getting-flarum-to-work-on-new-host/28?_=1645013723672

  • 18 Votes
    53 Posts
    4k Views

    @JAC said in KeepSolid VPN Unlimited DEAL:

    although all are going to have their own flaws one way or another,

    Exactly that - none of them are going to suit every individual purpose. You have to read the reviews, decide what functionality you need, and then make a judgement call for yourself (and your own unique needs).

    There is no “wrong or right”, although I would steer clear of those that do not have a no-logs policy for privacy reasons alone.

  • 18 Votes
    36 Posts
    2k Views

    you are too fast 😉

  • 49 Votes
    213 Posts
    17k Views

    @crazycells briefly, yes. I think what concerns be the most with home brew VPN convective like this is a lack of security updates, and potentially leaving yourself open.

    I’ve yet to actually try it, but I know there are a variety of ways to achieve the same goal.