So, the problem isn't strictly the CNAMEs, its the fact that the same page with the same path is served on all of the domains on that server.
If you restricted serving of the link-tracking link to the domain it was supposed to be for, it would only have affected that domain. I've submitted your escalation, though often there's a faster response to the automated systems and mechanisms. Brandon On Wed, Jan 9, 2019 at 2:11 PM Brandon Long <bl...@google.com> wrote: > If you send me a list of affected domains, I can raise an internal > escalation to the safe browsing team so they can see if the rules are > working as expected or not. > > Brandon > > On Wed, Jan 9, 2019 at 10:48 AM Tim Starr <timstar...@gmail.com> wrote: > >> We have a case of many clients' link-tracking domains being all flagged >> for "social engineering content." I see that there's a case-by-case >> security review request process, but is there any way to handle it for many >> at once? This seems to have been due to many different domains all being >> CNAMEd to one, then one client sending a campaign with a blacklisted domain >> in it, getting all the domains with the same CNAME value flagged. >> >> Tim Starr >> Senior Director, Deliverability >> Maropost.com >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
