Am 04.02.2016 um 17:38 schrieb David Jones:
* you did not provide a hint to the list-problem * to "solve" the OP's problem DMARC is not neededMail admins need to get familiar with DMARC because major ISPs have begun to take this seriously in the past year and are starting to reject or put into spam folders when this is setup incorrectly or missing. Many mail servers trust inbound email better (not whitelist) when SPF and DKIM checks pass. Google is telling all of their mail customers to add DMARC DNS records to block spoofing of their own domains
before Google ist telling somebody something they should better learn the difference between "~" and "-" in a SPF record to make gmail.com at least on envelope-level spoofing protected
i high percentage of spam here would not only have been flagged but outright rejected if they would do their own homework
;; ANSWER SECTION:gmail.com. 300 IN TXT "v=spf1 redirect=_spf.google.com"
;; ANSWER SECTION:_spf.google.com. 300 IN TXT "v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all"
signature.asc
Description: OpenPGP digital signature
