> I am working on a setup and situation dictates that every server here > is behind a NAT firewall. The problem now of course is, that > connections to SMTP daemon are translated to the internal IP of the > firewall, therefor SPF, and a whole lot other checks fail because > ASSP sees them coming from the NAT firewalls internal IP.
which is a total nonsense :) see, "NAT != proxy" - this means that publishing whatever service sitting behind a NAT just means setting up a "port forwarding" rule and this, in turn, means that whatever incoming connection to such a port (on the WAN interface) will be forwarded to the internal box/port and seen by the latter as coming from the EXTERNAL IP address not from the NAT one; what you described, instead, is the situation of a box sitting behind a "proxy" of some kind which accepts incoming connections and proxies them to ASSP; this makes me think that you're using some kind of "appliance" or "UTM" which is also implementing incoming mail filtering (and maybe some kind of spam filtering); in such a case, given that such a filtering is carried on by ASSP (and far BETTER than using whatever appliance), my suggestion is to disable the "SMTP proxy" in your appliance and let ASSP do its job (even if sitting behind the NAT/Firewall) ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
