ASSP development mailing list <[email protected]> schreibt: >XCLIENT is necessary in this case for >ASSP to have the real information on the client - the conection comes >from >127.0.0.1 and that would kill all RBLs and everything that is keyed >on >client's >IP address.
No, it does not. If you give ASSP the information about the frontend it will perform most of the ip based checks ISP/Secondary Hostnames* (ispHostnames) Hostnames to lookup the IP that connected to the ISP/Secondary server. If found, this address is used to perform IP-based checks on forwarded messages. For example: mx1.yourisp.com or mx1.yourisp.net|mx2.yoursecondary.com. This hostnames are found in the 'Received:' header, like 'Received: from ...123.123.123.123... by mx1.yourisp.com'. Leave this blank to disable the feature. In 1.3.6 in future-development we developed a Transparent SSL Proxy Table* (ProxyConf) Define transparent Port Proxy here. ASSP will forward incomming packets to a specific destination. For example: if you want incoming connections on port 465 (SMTP-SSL) to be forwarded to your mailserver. Example:0.0.0.0:465=>192.168.1.25:465<=12.1.1.3,34.5.6.7,67.23.2.1|10.1.1.1:1477=>192.168.1.23:25<=120.5.1.3,134.5.19.7,67.123.221.11 The syntax is: localIP:localPORT=>forwardIP:forwardPORT<=allowfromIP1,allowfromIP2,...|next Proxy configuration|.... You have to configure the IP-address and IP-port for both - local and forward to value. AllowfromIP are comma separated values of IP-addresses from where connections are allowed. If there is no allow value defined, all connections will be allowed! ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
