It's incorrect. If you want reports for domain1.com are sent to e-mail
address in domain2.com, domain2.com must publish a record

*domain1.com._report._dmarc.domain2.com. TXT "v=DMARC1"

*to indicate it's willing to receive the reports for domain1.com*
*



21.02.2018 12:51, Randal Pinto via dmarc-discuss пишет:
> Hello Yeo,
>
> If you want *domain1.com <http://domain1.com>* to report to
> *domain2.com <http://domain2.com>* you have to add the following DNS
> entry to *domain1.com <http://domain1.com>*:
>
> Name: *domain2.com._report._dmarc*
> Value: *"v=DMARC1;"*
>
> This will authorise *domain2.com <http://domain2.com>* to receive
> DMARC reports on behalf of *domain1.com <http://domain1.com>*
>
> Best,
> Randal
>
>
> On 21 February 2018 at 09:29, Yeo via dmarc-discuss
> <dmarc-discuss@dmarc.org <mailto:dmarc-discuss@dmarc.org>> wrote:
>
>     Hi all,
>
>      
>
>     I would like to change the DMARC report to my another domain IT
>     support to check.
>
>     After I changed, I noticed it failed the DMARC external validation. L
>
>      
>
>     When a report generator has an aggregate report to send to
>     example.com <http://example.com>, it will consult example.com
>     <http://example.com>‘s DMARC record and extract the address above.
>     Since the domain in that address is not example.com
>     <http://example.com> or its organizational domain
>     <https://dmarc.org/wiki/Glossary#Organizational_Domain>, it would
>     have to make an authorization check first. It would take that
>     domain the report is for (example.com <http://example.com>), and
>     the domain that the rua field references (otherdomain.com
>     <http://otherdomain.com>), and construct a new name like this:
>
>      
>
>     “example.com._report._dmarc.otherdomain.com
>     <http://dmarc.otherdomain.com>”
>
>      
>
>     May I know how to create the this DNS record? Any sample?
>
>      
>
>     *Thanks.*
>
>     * *
>
>     *Regards,*
>
>     *Yeo*
>
>      
>
>
>     _______________________________________________
>     dmarc-discuss mailing list
>     dmarc-discuss@dmarc.org <mailto:dmarc-discuss@dmarc.org>
>     http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>     <http://www.dmarc.org/mailman/listinfo/dmarc-discuss>
>
>     NOTE: Participating in this list means you agree to the DMARC Note
>     Well terms (http://www.dmarc.org/note_well.html
>     <http://www.dmarc.org/note_well.html>)
>
>
>
>
> -- 
> Randal Pinto
> Founder & COO
> +447703108205 <tel:+447703108205>
> @randalpinto <https://twitter.com/randalpinto>
>
> *Red Sift
> <https://redsift.com/?utm_source=rp&utm_medium=email_signature> powers OnDMARC
> <https://ondmarc.com/?utm_source=rp&utm_medium=email_signature>*
> 5th Floor, 43 Whitfield Street, W1T 4HD, London, UK.
>
> *News*: OnDMARC wins Cyber Security Start-Up of the Year
> <https://medium.com/postmasters/ondmarc-makes-its-mark-in-the-cyber-security-awards-2017-c512c1860f6d>
>  | OnDMARC
> joins G-Cloud 9
> <https://www.digitalmarketplace.service.gov.uk/g-cloud/services/856003973521292>
>
>
> _______________________________________________
> dmarc-discuss mailing list
> dmarc-discuss@dmarc.org
> http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>
> NOTE: Participating in this list means you agree to the DMARC Note Well terms 
> (http://www.dmarc.org/note_well.html)


-- 
Vladimir Dubrovin
@Mail.Ru

_______________________________________________
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)

Reply via email to