Search results

We just had the same issue as a false positive , and found the only Spamhaus-listed IP in the x-originating-ip, which was the versatel IP the client was using to connect to the office via VPN. So one solution in this case was to stop sending out this header added by the local Exchange-Server...