@Jean Davis: I got a fix from Sonicwalls forums on this already. The firewall was changing the IP on the email header to our public IP.
Jean Davis
(February 28, 2011)
in response to this post
in response to this post
@Jean Davis: Glad to hear the problem has been solved.
In case the firewall (or any relaying hosts between ORF and the internet) adds its on delivery information to the MIME email headers (as a Received: from line) instead of allowing emails thru "transparently", then it should be added to the Intermediate Host List of ORF, so ORF will skip them when analyzing the headers.
We often see such issues with secondary MXs: if ORF is unaware of them, it will consider the secondary MX IP (which relays to the primary where ORF runs) as the sender, and all emails will be blocked by the SPF test if the domain owner has an SPF policy ending with "-all" published:
http://blog.vamsoft.com/2010/05/26/spf-test-and-intermediate-hosts/
In case the firewall (or any relaying hosts between ORF and the internet) adds its on delivery information to the MIME email headers (as a Received: from line) instead of allowing emails thru "transparently", then it should be added to the Intermediate Host List of ORF, so ORF will skip them when analyzing the headers.
We often see such issues with secondary MXs: if ORF is unaware of them, it will consider the secondary MX IP (which relays to the primary where ORF runs) as the sender, and all emails will be blocked by the SPF test if the domain owner has an SPF policy ending with "-all" published:
http://blog.vamsoft.com/2010/05/26/spf-test-and-intermediate-hosts/
Krisztian Fekete
(March 1, 2011)
in response to this post
in response to this post
Does anyone know exactly whats happening?
Thanks,
Jean