Chris Arnold wrote:
>OK, if I understand you correctly...
>I see you having two options.
>You can configure your router/fire wall to route the traffic to the
>individual servers behind the fire wall, (if this is possible, it is
>the BEST way to do it IMO). This means that port 80 traffic for
>webmail.example.com should go to the web mail server and all other
>port 80 traffic to the web server. Most routers intended for
>business/professional use allow you to do just this sort of thing. If
>you are using one intended for the consumer market, all bets are off
>as to whether it supports such a configuration.
Our router/firewall does allow for this but as was stated in the
other posts (look in the vhost.conf that i posted) webserver answers
for port 80 and the webmail server answers for port 8080. So when
users type in webmail.some-domain.tld, this goes to the webserver
and not the webmail server (these users have trouble remembering to
type :8080 at the end of the address which results in help desk
calls). Just so you know, we use a Juniper/Netscreen router/firewall.
---------------- End original message. ---------------------
So why not have the web mail server responding to port 80 (as it should)?
Then you configure your router as I suggested. Problem solved and no
funky business with redirects or proxies.
Dragon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
