Any receiver may decide to override the sender policy. There is a method to do that and report it in aggregate reports. A receiver would do it, when you have a particularly troublesome big forwarder and when too many of your users would complain of not receiving such emails anymore.
The solution: identify the forwarder and tell them to not break DKIM when forwarding. If they don’t get it, may be don’t email the forwarder… (better said than done). On Jul 31, 2014, at 3:31 PM, Norman, Jean Marie via dmarc-discuss <[email protected]> wrote: > Has anyone experienced unauthenticated emails being delivered to Google > recipients despite having a DMARC policy (quarantine or reject) in place? We > have seen evidence that unauthenticated emails (not passing both SPF and > DKIM) are being delivered to Google, despite a DMARC policy, when messages > pass through a ‘forwarder’, as noted by Google. We are trying to better > understand this behavior and whether or not anyone has found a solution? Any > insight or recommendations would be appreciated. > > Thanks, >
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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)
