Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Kuch/Mitchell/D. via dmarc-discuss 
Thanks, Brandon for filing the bug. I'll offer the following for 
consideration...

We, internet service operators, must categorically stop referring to domains 
levels (first, second, third, etc.) and instead evaluate based on the public 
suffix of any given domain. The Public Suffix List [0] allows us to do just 
that.

The US. zone is not strictly a two-level domain, although many two and three 
level domains exist. In fact, a vast majority of the "independently 
authoritative" zones are at the second level but many others exist at the third 
and fourth levels. RFC1480 provides some historical context about where 3 & 4 
level names exist.  Essentially, the two characters postal abbreviation for a 
state marks the boundary. The third level domains, under the "second level" 
state code, can be registered independently.

For example, lib.mi.us. is deligated to Merit Network and royal-oak.mi.us. is 
deligated to MultiParadigm. Both organizations offer fourth level registrations 
of their respective zones.

tln.lib.mi.us. is registered and used by The Library Network independent of all 
other fourth level lib.mi.us. domains. At the same time, ci.royal-oak.mi.us. is 
registered and used independently by The City of Royal Oak, MI.

If DMARC specifies that we should "ignore TLDs"; it should most certainly be 
interpreted as "ignore public suffixes" as the definition of "top-level" is 
contextual.

 - - Mitchell

[0] https://publicsuffix.org/

- Original Message -
From: "Brandon Long via dmarc-discuss" 
To: st...@wordtothewise.com
Cc: "DMARC Discussion List" 
Sent: Friday, October 27, 2017 6:45:58 PM
Subject: Re: [dmarc-discuss] Google not sending aggregate reports for my .US
TLD

yeah, seems reasonable, I'll file a bug. 

Brandon 


On Fri, Oct 27, 2017 at 3:44 PM Steve Atkins via dmarc-discuss < [ 
mailto:dmarc-discuss@dmarc.org | dmarc-discuss@dmarc.org ] > wrote: 



> On Oct 27, 2017, at 3:15 PM, Tyler South via dmarc-discuss < [ 
> mailto:dmarc-discuss@dmarc.org | dmarc-discuss@dmarc.org ] > wrote: 
> 
> The domain in question is [ http://cssi.us/ | cssi.us ] 
> 
> Thanks for any assistance you can provide. 
> 

Looks reasonable to me. 

v=DMARC1;rua=mailto: [ mailto:983a6a4164b9...@rep.dmarcanalyzer.com | 
983a6a4164b9...@rep.dmarcanalyzer.com ] ,mailto: [ mailto:dmarc...@cssi.us | 
dmarc...@cssi.us ] ;ruf=mailto: [ mailto:983a6a4164b9...@for.dmarcanalyzer.com 
| 983a6a4164b9...@for.dmarcanalyzer.com ] ,mailto: [ mailto:dmarc...@cssi.us | 
dmarc...@cssi.us ] ; p=reject; fo=1; sp=none 

[ http://tools.wordtothewise.com/dmarc/check/cssi.us | 
http://tools.wordtothewise.com/dmarc/check/cssi.us ] 

Maybe someone at Google can take a look? 

Cheers, 
Steve 

> On Fri, Oct 27, 2017 at 5:08 PM, Tyler South < [ mailto:tsou...@gmail.com | 
> tsou...@gmail.com ] > wrote: 
> Hey everyone, 
> 
> 
> We’ve been trying to track down what could possibly be causing this issue. 
> Google nevers send an aggregate report for our .US domain. 
> 
> 
> 
> We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have 
> yet to get a single report from Google. 
> 
> 
> We use this very same .US domain to receive DMARC reports, both aggregate and 
> forensic, for about ten other domains that we manage. Google sends us 
> aggregate reports about those domains every day. 
> 
> 
> So we do get aggregate reports from Google for other domains in which we are 
> setup as the rua.We just don't get them for our own domain. 
> 
> 
> The DMARC record for our domain is, "v=DMARC1;rua=mailto: [ 
> mailto:aggrepo...@x.us | aggrepo...@x.us ] ;ruf=mailto: [ 
> mailto:forrepo...@x.us | forrepo...@x.us ] ; p=reject; fo=1; sp=none" 
> 
> 
> We have modified it several times in failed attempts to resolve this issue. 
> We tried changing the RUA to other domains and services such as DMARCAnalyzer 
> and we have pretty much tried everything as far as changing tags in the DMARC 
> record goes. 
> 
> 
> Here is a copy of a DMARC record for a domain that google DOES send reports 
> for to us, "v=DMARC1;rua=mailto: [ mailto:aggrepo...@x.us | 
> aggrepo...@x.us ] ;ruf=mailto: [ mailto:forrepo...@x.us | 
> forrepo...@x.us ] ; p=reject; fo=1;" 
> 
> 
> We can’t figure out any pattern to this madness. 
> 
> 
> I mentioned our domain being a .US TLD repeatedly because I’m almost 
> convinced there is a bug that has something to do with reports not being 
> generated for a .US TLD. 
> 
> 
> Can anyone else with a .US TLD confirm you get reports from Google? 
> 
> 
> 
> If anyone has any ideas we’d really appreciate your time. This has been 
> driving us mad. 
> 
> 
> Thanks.

___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Dave Crocker via dmarc-discuss 

On 10/27/2017 3:51 PM, Steve Atkins via dmarc-discuss wrote:

The p= tag must come immediately after the v=DMARC1. Google is apparently 
ignoring your record while the other receivers are ignoring the spec.

...



I recommend moving the p= tag to be right after v=DMARC; and see what happens.

/me goes to fix his tools



There's a meta-lesson here, given how relatively mature and heavily-used 
DMARC is, which ought to make it surprising that this sort of thing pops 
up this late.


But I can't figure out what sort of productive statement to make to 
describe the lesson or what to do about it...


d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Steve Atkins via dmarc-discuss 

> On Oct 27, 2017, at 3:33 PM, John Wilson via dmarc-discuss 
>  wrote:
> 
> Tyler,
> 
> The p= tag must come immediately after the v=DMARC1. Google is apparently 
> ignoring your record while the other receivers are ignoring the spec.
> 
> https://tools.ietf.org/html/rfc7489#section-6.4
> 

Oh, good catch. I'd completely forgotten about that nit.

> I recommend moving the p= tag to be right after v=DMARC; and see what happens.

/me goes to fix his tools

Cheers,
  Steve
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Brandon Long via dmarc-discuss 
yeah, seems reasonable, I'll file a bug.

Brandon


On Fri, Oct 27, 2017 at 3:44 PM Steve Atkins via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

>
> > On Oct 27, 2017, at 3:15 PM, Tyler South via dmarc-discuss <
> dmarc-discuss@dmarc.org> wrote:
> >
> > The domain in question is cssi.us
> >
> > Thanks for any assistance you can provide.
> >
>
> Looks reasonable to me.
>
> v=DMARC1;rua=mailto:983a6a4164b9...@rep.dmarcanalyzer.com,mailto:
> dmarc...@cssi.us;ruf=mailto:983a6a4164b9...@for.dmarcanalyzer.com,mailto:
> dmarc...@cssi.us; p=reject; fo=1; sp=none
>
> http://tools.wordtothewise.com/dmarc/check/cssi.us
>
> Maybe someone at Google can take a look?
>
> Cheers,
>   Steve
>
> > On Fri, Oct 27, 2017 at 5:08 PM, Tyler South  wrote:
> > Hey everyone,
> >
> >
> > We’ve been trying to track down what could possibly be causing this
> issue. Google nevers send an aggregate report for our .US domain.
> >
> >
> >
> > We get aggregate reports from AOL, Yahoo, and Outlook on occasion but
> have yet to get a single report from Google.
> >
> >
> > We use this very same .US domain to receive DMARC reports, both
> aggregate and forensic, for  about ten other domains that we manage. Google
> sends us aggregate reports about those domains every day.
> >
> >
> > So we do get aggregate reports from Google for other domains in which we
> are setup as the rua.We just don't get them for our own domain.
> >
> >
> > The DMARC record for our domain is, "v=DMARC1;rua=mailto:
> aggrepo...@x.us;ruf=mailto:forrepo...@x.us; p=reject; fo=1;
> sp=none"
> >
> >
> > We have modified it several times in failed attempts to resolve this
> issue. We tried changing the RUA to other domains and services such as
> DMARCAnalyzer and we have pretty much tried everything as far as changing
> tags in the DMARC record goes.
> >
> >
> > Here is a copy of a DMARC record for a domain that google DOES send
> reports for to us, "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:
> forrepo...@x.us; p=reject; fo=1;"
> >
> >
> > We can’t figure out any pattern to this madness.
> >
> >
> > I mentioned our domain being a .US TLD repeatedly because I’m almost
> convinced there is a bug that has something to do with reports not being
> generated for a .US TLD.
> >
> >
> > Can anyone else with a .US TLD confirm you get reports from Google?
> >
> >
> >
> > If anyone has any ideas we’d really appreciate your time. This has been
> driving us mad.
> >
> >
> > Thanks.
> >
> >
> > ___
> > 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)
>
>
> ___
> 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)
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Peter Bowen via dmarc-discuss 
On Fri, Oct 27, 2017 at 3:27 PM, Steve Atkins via dmarc-discuss
 wrote:
>
>> On Oct 27, 2017, at 3:20 PM, Brandon Long  wrote:
>>
>> Isn't .us usually considered a 3 level tld, like .uk and .au?  And DMARC 
>> says to ignore tlds.
>
> Neustar decided second level domains were more valuable 15 years ago or so, 
> and it's mostly sold as a generic two level TLD now.
>
> Given the history there are still a lot of three and four level hostnames in 
> there (states, .fed.us, .nsn.us, ...), and the weird 
> {ci,co,city,...}...us stuff so it's probably one of the more 
> complex bits of organizational domain identification code.

The us TLD is horribly complex.
https://github.com/publicsuffix/list/pull/276 provides a hint of the
complexity -- there are more than 2000 non-overlapping suffixes for
.us and they vary.  For example k12.az.us is a registered domain while
k12.ca.us is a suffix for registered domains.  There are also "hybrid"
names due to the delegated managers system, where portions of the US
namespace are delegated to registrars who use completely separate
rules for registration.

Good luck on figuring out the domain boundaries under .us ;)

Thanks,
Peter

___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Steve Atkins via dmarc-discuss 

> On Oct 27, 2017, at 3:15 PM, Tyler South via dmarc-discuss 
>  wrote:
> 
> The domain in question is cssi.us
> 
> Thanks for any assistance you can provide.
> 

Looks reasonable to me.

v=DMARC1;rua=mailto:983a6a4164b9...@rep.dmarcanalyzer.com,mailto:dmarc...@cssi.us;ruf=mailto:983a6a4164b9...@for.dmarcanalyzer.com,mailto:dmarc...@cssi.us;
 p=reject; fo=1; sp=none

http://tools.wordtothewise.com/dmarc/check/cssi.us

Maybe someone at Google can take a look?

Cheers,
  Steve

> On Fri, Oct 27, 2017 at 5:08 PM, Tyler South  wrote:
> Hey everyone,
> 
> 
> We’ve been trying to track down what could possibly be causing this issue. 
> Google nevers send an aggregate report for our .US domain.
> 
> 
> 
> We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have 
> yet to get a single report from Google.
> 
>  
> We use this very same .US domain to receive DMARC reports, both aggregate and 
> forensic, for  about ten other domains that we manage. Google sends us 
> aggregate reports about those domains every day.
> 
> 
> So we do get aggregate reports from Google for other domains in which we are 
> setup as the rua.We just don't get them for our own domain.
> 
>  
> The DMARC record for our domain is, 
> "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> p=reject; fo=1; sp=none"
> 
>  
> We have modified it several times in failed attempts to resolve this issue. 
> We tried changing the RUA to other domains and services such as DMARCAnalyzer 
> and we have pretty much tried everything as far as changing tags in the DMARC 
> record goes.
> 
> 
> Here is a copy of a DMARC record for a domain that google DOES send reports 
> for to us, 
> "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> p=reject; fo=1;"
> 
>  
> We can’t figure out any pattern to this madness.
> 
>  
> I mentioned our domain being a .US TLD repeatedly because I’m almost 
> convinced there is a bug that has something to do with reports not being 
> generated for a .US TLD. 
> 
>  
> Can anyone else with a .US TLD confirm you get reports from Google?
> 
> 
> 
> If anyone has any ideas we’d really appreciate your time. This has been 
> driving us mad.
> 
>  
> Thanks.
> 
> 
> ___
> 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)


___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread John Wilson via dmarc-discuss 
Tyler,

The p= tag must come immediately after the v=DMARC1. Google is apparently
ignoring your record while the other receivers are ignoring the spec.

https://tools.ietf.org/html/rfc7489#section-6.4

I recommend moving the p= tag to be right after v=DMARC; and see what
happens.

Good luck!


On Fri, Oct 27, 2017 at 3:15 PM, Tyler South via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

> The domain in question is cssi.us
>
> Thanks for any assistance you can provide.
>
> On Fri, Oct 27, 2017 at 5:08 PM, Tyler South  wrote:
>
>> Hey everyone,
>>
>>
>> We’ve been trying to track down what could possibly be causing this
>> issue. Google nevers send an aggregate report for our .US domain.
>>
>>
>> We get aggregate reports from AOL, Yahoo, and Outlook on occasion but
>> have yet to get a single report from Google.
>>
>>
>>
>> We use this very same .US domain to receive DMARC reports, both aggregate
>> and forensic, for  about ten other domains that we manage. Google sends us
>> aggregate reports about those domains every day.
>>
>>
>> So we do get aggregate reports from Google for other domains in which we
>> are setup as the rua.We just don't get them for our own domain.
>>
>>
>>
>> The DMARC record for our domain is, "v=DMARC1;rua=mailto:aggreport
>> s...@x.us;ruf=mailto:forrepo...@x.us; p=reject; fo=1; sp=none"
>>
>>
>>
>> We have modified it several times in failed attempts to resolve this
>> issue. We tried changing the RUA to other domains and services such as
>> DMARCAnalyzer and we have pretty much tried everything as far as changing
>> tags in the DMARC record goes.
>>
>>
>> Here is a copy of a DMARC record for a domain that google DOES send
>> reports for to us, "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:
>> forrepo...@x.us; p=reject; fo=1;"
>>
>>
>>
>> We can’t figure out any pattern to this madness.
>>
>>
>>
>> I mentioned our domain being a .US TLD repeatedly because I’m almost
>> convinced there is a bug that has something to do with reports not being
>> generated for a .US TLD.
>>
>>
>>
>> Can anyone else with a .US TLD confirm you get reports from Google?
>>
>>
>> If anyone has any ideas we’d really appreciate your time. This has been
>> driving us mad.
>>
>>
>>
>> Thanks.
>>
>
>
> ___
> 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)
>
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Steve Atkins via dmarc-discuss 

> On Oct 27, 2017, at 3:20 PM, Brandon Long  wrote:
> 
> Isn't .us usually considered a 3 level tld, like .uk and .au?  And DMARC says 
> to ignore tlds.

Neustar decided second level domains were more valuable 15 years ago or so, and 
it's mostly sold as a generic two level TLD now.

Given the history there are still a lot of three and four level hostnames in 
there (states, .fed.us, .nsn.us, ...), and the weird 
{ci,co,city,...}...us stuff so it's probably one of the more 
complex bits of organizational domain identification code.

Cheers,
  Steve

> 
> Brandon
> 
> 
> On Fri, Oct 27, 2017 at 3:01 PM Steve Atkins via dmarc-discuss 
>  wrote:
> 
> > On Oct 27, 2017, at 2:08 PM, Tyler South via dmarc-discuss 
> >  wrote:
> >
> > Hey everyone,
> >
> >
> > We’ve been trying to track down what could possibly be causing this issue. 
> > Google nevers send an aggregate report for our .US domain.
> >
> >
> >
> > We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have 
> > yet to get a single report from Google.
> >
> >
> > We use this very same .US domain to receive DMARC reports, both aggregate 
> > and forensic, for  about ten other domains that we manage. Google sends us 
> > aggregate reports about those domains every day.
> >
> >
> > So we do get aggregate reports from Google for other domains in which we 
> > are setup as the rua.We just don't get them for our own domain.
> >
> >
> > The DMARC record for our domain is, 
> > "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> > p=reject; fo=1; sp=none"
> 
> p=reject and sp=none?
> 
> >
> >
> > We have modified it several times in failed attempts to resolve this issue. 
> > We tried changing the RUA to other domains and services such as 
> > DMARCAnalyzer and we have pretty much tried everything as far as changing 
> > tags in the DMARC record goes.
> >
> >
> > Here is a copy of a DMARC record for a domain that google DOES send reports 
> > for to us, 
> > "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> > p=reject; fo=1;"
> >
> >
> > We can’t figure out any pattern to this madness.
> 
> It does sound like something at Google and something in your DMARC record may 
> not be playing nice together. Do you get forensic reports for that domain?
> 
> >
> >
> > I mentioned our domain being a .US TLD repeatedly because I’m almost 
> > convinced there is a bug that has something to do with reports not being 
> > generated for a .US TLD.
> 
> You might get more useful advice if you share what the relevant domains are, 
> so we can look up what DMARC records you're publishing (and maybe check logs 
> for those domains).
> 
> Cheers,
>   Steve
> ___
> 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)


___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Brandon Long via dmarc-discuss 
Isn't .us usually considered a 3 level tld, like .uk and .au?  And DMARC
says to ignore tlds.

Brandon


On Fri, Oct 27, 2017 at 3:01 PM Steve Atkins via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

>
> > On Oct 27, 2017, at 2:08 PM, Tyler South via dmarc-discuss <
> dmarc-discuss@dmarc.org> wrote:
> >
> > Hey everyone,
> >
> >
> > We’ve been trying to track down what could possibly be causing this
> issue. Google nevers send an aggregate report for our .US domain.
> >
> >
> >
> > We get aggregate reports from AOL, Yahoo, and Outlook on occasion but
> have yet to get a single report from Google.
> >
> >
> > We use this very same .US domain to receive DMARC reports, both
> aggregate and forensic, for  about ten other domains that we manage. Google
> sends us aggregate reports about those domains every day.
> >
> >
> > So we do get aggregate reports from Google for other domains in which we
> are setup as the rua.We just don't get them for our own domain.
> >
> >
> > The DMARC record for our domain is, "v=DMARC1;rua=mailto:
> aggrepo...@x.us;ruf=mailto:forrepo...@x.us; p=reject; fo=1;
> sp=none"
>
> p=reject and sp=none?
>
> >
> >
> > We have modified it several times in failed attempts to resolve this
> issue. We tried changing the RUA to other domains and services such as
> DMARCAnalyzer and we have pretty much tried everything as far as changing
> tags in the DMARC record goes.
> >
> >
> > Here is a copy of a DMARC record for a domain that google DOES send
> reports for to us, "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:
> forrepo...@x.us; p=reject; fo=1;"
> >
> >
> > We can’t figure out any pattern to this madness.
>
> It does sound like something at Google and something in your DMARC record
> may not be playing nice together. Do you get forensic reports for that
> domain?
>
> >
> >
> > I mentioned our domain being a .US TLD repeatedly because I’m almost
> convinced there is a bug that has something to do with reports not being
> generated for a .US TLD.
>
> You might get more useful advice if you share what the relevant domains
> are, so we can look up what DMARC records you're publishing (and maybe
> check logs for those domains).
>
> Cheers,
>   Steve
> ___
> 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)
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Tyler South via dmarc-discuss 
The domain in question is cssi.us

Thanks for any assistance you can provide.

On Fri, Oct 27, 2017 at 5:08 PM, Tyler South  wrote:

> Hey everyone,
>
>
> We’ve been trying to track down what could possibly be causing this issue.
> Google nevers send an aggregate report for our .US domain.
>
>
> We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have
> yet to get a single report from Google.
>
>
>
> We use this very same .US domain to receive DMARC reports, both aggregate
> and forensic, for  about ten other domains that we manage. Google sends us
> aggregate reports about those domains every day.
>
>
> So we do get aggregate reports from Google for other domains in which we
> are setup as the rua.We just don't get them for our own domain.
>
>
>
> The DMARC record for our domain is, "v=DMARC1;rua=mailto:aggreport
> s...@x.us;ruf=mailto:forrepo...@x.us; p=reject; fo=1; sp=none"
>
>
>
> We have modified it several times in failed attempts to resolve this
> issue. We tried changing the RUA to other domains and services such as
> DMARCAnalyzer and we have pretty much tried everything as far as changing
> tags in the DMARC record goes.
>
>
> Here is a copy of a DMARC record for a domain that google DOES send
> reports for to us, "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:
> forrepo...@x.us; p=reject; fo=1;"
>
>
>
> We can’t figure out any pattern to this madness.
>
>
>
> I mentioned our domain being a .US TLD repeatedly because I’m almost
> convinced there is a bug that has something to do with reports not being
> generated for a .US TLD.
>
>
>
> Can anyone else with a .US TLD confirm you get reports from Google?
>
>
> If anyone has any ideas we’d really appreciate your time. This has been
> driving us mad.
>
>
>
> Thanks.
>
___
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)

Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Steve Atkins via dmarc-discuss 

> On Oct 27, 2017, at 2:08 PM, Tyler South via dmarc-discuss 
>  wrote:
> 
> Hey everyone,
> 
> 
> We’ve been trying to track down what could possibly be causing this issue. 
> Google nevers send an aggregate report for our .US domain.
> 
> 
> 
> We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have 
> yet to get a single report from Google.
> 
>  
> We use this very same .US domain to receive DMARC reports, both aggregate and 
> forensic, for  about ten other domains that we manage. Google sends us 
> aggregate reports about those domains every day.
> 
> 
> So we do get aggregate reports from Google for other domains in which we are 
> setup as the rua.We just don't get them for our own domain.
> 
>  
> The DMARC record for our domain is, 
> "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> p=reject; fo=1; sp=none"

p=reject and sp=none?

> 
>  
> We have modified it several times in failed attempts to resolve this issue. 
> We tried changing the RUA to other domains and services such as DMARCAnalyzer 
> and we have pretty much tried everything as far as changing tags in the DMARC 
> record goes.
> 
> 
> Here is a copy of a DMARC record for a domain that google DOES send reports 
> for to us, 
> "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:forrepo...@x.us; 
> p=reject; fo=1;"
> 
>  
> We can’t figure out any pattern to this madness.

It does sound like something at Google and something in your DMARC record may 
not be playing nice together. Do you get forensic reports for that domain?

> 
>  
> I mentioned our domain being a .US TLD repeatedly because I’m almost 
> convinced there is a bug that has something to do with reports not being 
> generated for a .US TLD. 

You might get more useful advice if you share what the relevant domains are, so 
we can look up what DMARC records you're publishing (and maybe check logs for 
those domains).

Cheers,
  Steve
___
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)

[dmarc-discuss] Google not sending aggregate reports for my .US TLD

2017-10-27 Thread Tyler South via dmarc-discuss 
Hey everyone,


We’ve been trying to track down what could possibly be causing this issue.
Google nevers send an aggregate report for our .US domain.


We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have
yet to get a single report from Google.



We use this very same .US domain to receive DMARC reports, both aggregate
and forensic, for  about ten other domains that we manage. Google sends us
aggregate reports about those domains every day.


So we do get aggregate reports from Google for other domains in which we
are setup as the rua.We just don't get them for our own domain.



The DMARC record for our domain is, "v=DMARC1;rua=mailto:aggrepo...@x.us
;ruf=mailto:forrepo...@x.us; p=reject; fo=1; sp=none"



We have modified it several times in failed attempts to resolve this issue.
We tried changing the RUA to other domains and services such as
DMARCAnalyzer and we have pretty much tried everything as far as changing
tags in the DMARC record goes.


Here is a copy of a DMARC record for a domain that google DOES send reports
for to us, "v=DMARC1;rua=mailto:aggrepo...@x.us;ruf=mailto:
forrepo...@x.us; p=reject; fo=1;"



We can’t figure out any pattern to this madness.



I mentioned our domain being a .US TLD repeatedly because I’m almost
convinced there is a bug that has something to do with reports not being
generated for a .US TLD.



Can anyone else with a .US TLD confirm you get reports from Google?


If anyone has any ideas we’d really appreciate your time. This has been
driving us mad.



Thanks.
___
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)

Re: [dmarc-discuss] 2 questions about evaluating DMARC reports -- recommendations ?

2017-10-27 Thread John R Levine via dmarc-discuss 

bits in a database at https://www.taugh.com/rddmard


Typo.  As you might expect it's really https://www.taugh.com/rddmarc


Regards,
John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
___
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)

Re: [dmarc-discuss] 2 questions about evaluating DMARC reports -- recommendations ?

2017-10-27 Thread Pete Holzmann via dmarc-discuss 
On 26 Oct 2017 John Levine via dmarc-discuss said...
>I give away some scripts that read dmarc reports and put the
>interesting
>bits in a database at https://www.taugh.com/rddmard

Typo? I don't see anything there :(


___
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)