Is that a good or a bad idea:
I just replaced
RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
by
RewriteCond %{REMOTE_ADDR} (.*)
RewriteRule .* - [E=SENDER_IP_ADDRESS:%1]
RequestHeader set "x-webobjects-remote-host" "%{SENDER_IP_ADDRESS}e"
giving the remote user's IP address as "X-Forward:" header in mails sent by
SOGo - so by looking at a mail message we can look where it originated.
The side effect is that sogo.log now also takes this remote ip addresses as
remote host - but all is still working properly.
What's the exact meaning of "x-webobjects-remote-host"?
Why was it set to 127.0.0.1? Our reverse-proxy-Apache is not on 127.0.0.1 and
still this setup worked without any problem.
Pascal
--
Pascal Gienger Jabber/XMPP/Mail: pascal.gien...@uni-konstanz.de
University of Konstanz, IT Services Department ("Rechenzentrum")
Electronic Communications and Web Services
Building V, Room V404, Phone +49 7531 88 5048, Fax +49 7531 88 3739
--
users@sogo.nu
https://inverse.ca/sogo/lists
