We use mod_proxy_balancer in front of our SOGo servers, so by default
outgoing emails from sogo will have a X-Forward header with the address
of our loadbalancer.
| frontend server 1,2 (apache mod_proxy_balancer) | backend server 1,2,3,n
(standard sogo-configured apache and sogod) |
I suppose the fix for this should be to change on the backend
sogo-servers:
RewriteRule ^/SOGo/(.*)$ /SOGo/$1 [env=REMOTE_HOST:%{REMOTE_ADDR},PT]
to rather use the X-Forwarded-For that mod_proxy sets:
RewriteRule ^/SOGo/(.*)$ /SOGo/$1
[env=REMOTE_HOST:%{X-Forwarded-For},PT]
I've been sniffing the network traffic to verify that X-Forwarded-For is set on
the incoming requests to the backend servers, but the X-Forward header
isn't included in outgoing messages..
Any idea what I'm doing wrong here?
-jf
--
[email protected]
https://inverse.ca/sogo/lists
