If valid, has anyone here used or seen it successfully used? Is it not recommended? Just wondering why documentation seems to take an all (*) or domain-by-domain approach.
Thanks, *Davina N. Thomas* PwC | Contractor to PwC - PS Infrastructure Engineering Office: +1 813 351 2885 | Fax: +1 813 342 4948 Email: [email protected] PricewaterhouseCoopers LLP Tampa, Florida http://www.pwc.com/us Print less, think more. On Wed, Mar 22, 2017 at 12:17 PM, <[email protected]> wrote: > Send dmarc-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://dmarc.org/mailman/listinfo/dmarc-discuss > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dmarc-discuss digest..." > > > Today's Topics: > > 1. AUTO: Oliver Endrikat is out of the office (returning > 22.03.2017) (Oliver Endrikat) > 2. New to DMARC need help (Don Buchanan) > 3. Re: New to DMARC need help (Vladimir Dubrovin) > 4. "Subdomain" Wildcard in DMARC Report Authorization Records > (Davina Thomas (US)) > 5. Re: "Subdomain" Wildcard in DMARC Report Authorization > Records (Jacob Evans) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 21 Mar 2017 22:02:52 +0100 > From: Oliver Endrikat <[email protected]> > To: [email protected] > Subject: [dmarc-discuss] AUTO: Oliver Endrikat is out of the office > (returning 22.03.2017) > Message-ID: > <OFBE60D2F0.9A84ED32-ONC12580EA.00739EA3-C12580EA. > [email protected]> > > Content-Type: text/plain; charset=US-ASCII > > > I am out of the office until 22.03.2017. > > I will not read your message untik beeing back. > In urgent cases please direct separate message to [email protected]. > > > Note: This is an automated response to your message "dmarc-discuss Digest, > Vol 61, Issue 1" sent on 21.03.2017 20:00:00. > > This is the only notification you will receive while this person is away. > > > > ------------------------------ > > Message: 2 > Date: Wed, 22 Mar 2017 12:49:53 +0000 (UTC) > From: Don Buchanan <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [dmarc-discuss] New to DMARC need help > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Trying to implement a DMARC record for reporting purposes to start. I had > a simple TXT record put in place, but I am not getting reports, and believe > the record is not working as a DMARC record. > for mail domain : bloomingdales.com > Here is how I submitted the request to our 3rd party that hosts our > records.... > _dmarc.bloomingdales.com. IN TXT "v=DMARC1; p=none; rua=mailto: > [email protected]; sp=none; ri=86400" > What did I mess Up ? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://dmarc.org/pipermail/dmarc-discuss/attachments/ > 20170322/290528f3/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Wed, 22 Mar 2017 16:05:31 +0300 > From: Vladimir Dubrovin <[email protected]> > To: Don Buchanan <[email protected]>, "[email protected]" > <[email protected]> > Subject: Re: [dmarc-discuss] New to DMARC need help > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > According to DMARC standard, rua address must be either aligned with > domain (that is, to be located in bloomingdales.com) or publish > permissive DMARC record for reports, that is > bloomingdales.com._report._dmarc.macys.com in your case. So you have 2 > options: > 1. Publish TXT record bloomingdales.com._report._dmarc.macys.com with > value "v=DMARC1" > 2. Change rua address to something within bloomingdales.com (you can use > subdomains). > > > 22.03.2017 15:49, Don Buchanan via dmarc-discuss ?????: > > Trying to implement a DMARC record for reporting purposes to start. I > > had a simple TXT record put in place, but I am not getting reports, > > and believe the record is not working as a DMARC record. > > > > for mail domain : bloomingdales.com > > > > Here is how I submitted the request to our 3rd party that hosts our > > records.... > > > > _dmarc.bloomingdales.com. IN TXT "v=DMARC1; p=none; > > rua=mailto:[email protected]; sp=none; ri=86400" > > > > What did I mess Up ? > > > > > > _______________________________________________ > > dmarc-discuss mailing list > > [email protected] > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://dmarc.org/pipermail/dmarc-discuss/attachments/ > 20170322/18e3452c/attachment-0001.html> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: bjdgpddgdcgkbbfm.png > Type: image/png > Size: 1032 bytes > Desc: not available > URL: <http://dmarc.org/pipermail/dmarc-discuss/attachments/ > 20170322/18e3452c/attachment-0001.png> > > ------------------------------ > > Message: 4 > Date: Wed, 22 Mar 2017 10:55:57 -0400 > From: "Davina Thomas (US)" <[email protected]> > To: [email protected] > Subject: [dmarc-discuss] "Subdomain" Wildcard in DMARC Report > Authorization Records > Message-ID: > <CAJT_vRcoc4uFAFYBYhOe_HWZWctPw8w6nhsqB0DwFviaNh4t_g@ > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Instead of just an asterisk to accept all domains in a report authorization > record, is it possible to use a subdomain wildcard to have one subdomain > accept DMARC reports for all other subdomains, like the example below? > > *.otherdomain.com._report._dmarc.sub.otherdomain.com. TXT "v=DMARC1" > > I haven't seen anything directly allowing or excluding it either way. > > Thanks, > *Davina N. Thomas* > > ______________________________________________________________________ > The information transmitted, including any attachments, is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited, and all liability arising therefrom is disclaimed. If you > received this in error, please contact the sender and delete the material > from any computer. PricewaterhouseCoopers LLP is a Delaware limited > liability partnership. This communication may come from > PricewaterhouseCoopers LLP or one of its subsidiaries. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://dmarc.org/pipermail/dmarc-discuss/attachments/ > 20170322/63bf16d7/attachment-0001.html> > > ------------------------------ > > Message: 5 > Date: Wed, 22 Mar 2017 12:17:51 -0400 (EDT) > From: Jacob Evans <[email protected]> > To: "Davina Thomas (US)" <[email protected]> > Cc: [email protected] > Subject: Re: [dmarc-discuss] "Subdomain" Wildcard in DMARC Report > Authorization Records > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > yes that's valid, the lookup is always explicit so as long as dns answers > back with the TXT record you'll be good. > > such as > > dig +short TXT testdomain .otherdomain.com._report._ [ > http://dmarc.sub.otherdomain.com/ | dmarc.sub.otherdomain.com ] . > > answer: v=DMARC1 > > > > From: "Davina Thomas (US) via dmarc-discuss" <[email protected]> > To: [email protected] > Sent: Wednesday, March 22, 2017 10:55:57 AM > Subject: [dmarc-discuss] "Subdomain" Wildcard in DMARC Report > Authorization Records > > Instead of just an asterisk to accept all domains in a report > authorization record, is it possible to use a subdomain wildcard to have > one subdomain accept DMARC reports for all other subdomains, like the > example below? > > *.otherdomain.com._report._ [ http://dmarc.sub.otherdomain.com/ | > dmarc.sub.otherdomain.com ] . TXT "v=DMARC1" > > I haven't seen anything directly allowing or excluding it either way. > > Thanks, > Davina N. Thomas > > > The information transmitted, including any attachments, is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited, and all liability arising therefrom is disclaimed. If you > received this in error, please contact the sender and delete the material > from any computer. PricewaterhouseCoopers LLP is a Delaware limited > liability partnership. This communication may come from > PricewaterhouseCoopers LLP or one of its subsidiaries. > > _______________________________________________ > dmarc-discuss mailing list > [email protected] > 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) > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://dmarc.org/pipermail/dmarc-discuss/attachments/ > 20170322/2663fe31/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dmarc-discuss mailing list > [email protected] > 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) > > > ------------------------------ > > End of dmarc-discuss Digest, Vol 61, Issue 2 > ******************************************** > ______________________________________________________________________ The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you received this in error, please contact the sender and delete the material from any computer. PricewaterhouseCoopers LLP is a Delaware limited liability partnership. This communication may come from PricewaterhouseCoopers LLP or one of its subsidiaries.
_______________________________________________ dmarc-discuss mailing list [email protected] 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)
