zygntwin -> Email ISP migration causes Anti-Spam failure (2.Dec.2016 1:08:50 PM)
Ok, the particulars...
I have a single Exchange 2010 box running Server 2008 Standard R2
We have a POP program go get our email from our Email Hosting provider
I have Anti-Spam enabled on the box and have set up IPBlockList to eliminate baddies.
Recently the Email Hosting provider needed to migrate to an upgraded platform...this changed our IP among other things. This apparently broke the Anti-Spam ability to detect the correct IP. if at all.
In the Anti-Spam report, I can't see the IP address of the origin for the email, now the report generated shows no IP address. This used to work fine.
An example of a spam header...
Received: from Exchange (10.10.0.200) by Exchange.Server.local
(10.10.0.200) with Microsoft SMTP Server id 14.3.319.2; Fri, 2 Dec 2016
Received: from 184.108.40.206 by OURDOMAIN with POP3; Fri, 2 Dec
2016 12:54:01 -0500
Received: from Email.Hosting.com by Email.Hosting.com (Dovecot) with LMTP id
Uc0OLte0QVgWEQAAblMv4A for <firstname.lastname@example.org>; Fri, 02 Dec
2016 12:52:23 -0500
Delivery-date: Fri, 02 Dec 2016 12:52:23 -0500
Received: from [220.127.116.11] (port=42770 helo=emailaddress.com) by
Email.Hosting.com with esmtp (Exim 4.87) (envelope-from
<email@example.com>) id 1cCs0V-0001HI-1s for
firstname.lastname@example.org; Fri, 02 Dec 2016 12:52:23 -0500
Date: Fri, 2 Dec 2016 12:50:52 -0500
Names and IP's have been changed to protect the innocent.
The -InternalSMTPServers have been set to our Exchange box IP and our Email Hosting IP (The first two Recieved: headers).
But, the Anti-Spam isn't picking up on the true IP address in the last Received: line (18.104.22.168).