General discussion on installation and configuration of SOGo

Text archives Help


[SOGo] Is there a problem replacing "x-webobjects-remote-host" with a useful information?


Chronological Thread 
  • From: "Pascal Gienger" < >
  • To: < >
  • Subject: [SOGo] Is there a problem replacing "x-webobjects-remote-host" with a useful information?
  • Date: Thu, 02 Dec 2010 19:30:25 +0100

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:

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


  • [SOGo] Is there a problem replacing "x-webobjects-remote-host" with a useful information?, Pascal Gienger, 12/02/2010

Archive powered by MHonArc 2.6.16.

Top of page