Am 14.12.2014 um 23:48 schrieb Christian Rößner:
If I do understand this report right, DKIM passes, but SPF failed. If I look to my last mail, I sent this day, I see this in the headers:DMARC-Filter: OpenDMARC Filter v1.3.0 mx.roessner-net.de 3k0hcj6S5RzGpN5 Authentication-Results: mx.roessner-net.de; dmarc=pass header.from=roessner-network-solutions.com Authentication-Results: mx.roessner-net.de; spf=pass smtp.mailfrom=owner-postfix-us...@postfix.org DKIM-Filter: OpenDKIM Filter v2.9.2 mx.roessner-net.de 3k0hcj6S5RzGpN5 Authentication-Results: mx.roessner-net.de; dkim=pass (2048-bit key; secure) header.d=roessner-network-solutions.com header.i=@roessner-network-solutions.com header.b=G+zYCJvI; dkim-adsp=pass; dkim-atps=neutral So why does my own MX say, everything is fine, with incoming mails from the list, but I get reports from other people that SPF failed? Is this a misconfiguration somewhere remote or am I missing something?
i guess that fools apply the SPF test to the From-Header instead to the envelope, frankly Barracuda Networks does the same for Spoofing-Protection because "customers complained"
without knowing details i would suggest the problem is on the receivers side, but however: try to make your SPF as tiny as possible and avoid names and references
after switch to plain "ipv4:ip/network-range" i never faced any SPF problem while before it happened again and again by listing servers with names and things like a/mx/include
