We have made no changes that I am aware of but suddenly all email that is either forwarded out of our SmarterMail system (or forwarded because SmarterMail is the gateway mail server before Exchange) is failing SPF checks. The SPF checks appear that they are reading the header as the original sender domain, but with our IP address (the IP of the SmarterMail server). This might not be a new problem, but with increased weight on filters for SPF, it is becoming an large issue now.
Example: [email protected]<mailto:[email protected]> (Gmail IP Address)sends an email to our client at [email protected]<mailto:[email protected]> (Our SmarterMail IP Address) The [email protected]<mailto:[email protected]> client has set his account to auto forward to his Yahoo account. Yahoo is rejecting the message as it says that [email protected]<mailto:[email protected]> does not have permission to send from the SmarterMail IP address (SPF Fail) This especially hurts our clients that use our SmarterMail system for SPAM checks before it sends down to their Exchange server. Even their local Exchange server is seeing the message and comparing the original sender domain with our SM IP address and failing SPF. Is there some setting we are missing in SmarterMail or the Declude headers to help correct this? Any thoughts are appreciated. Thanks! ----------------------------------------------------------- Tina Cline 270net Technologies - IT Support Specialist Phone: 301.663.6000 x200 Fax: 301.663.4410 www.270net.com "Internet Technology for Business and Government" -----------------------------------------------------------
