Hello fellow SquirrelMail users,
I've been trying to get reverse proxying with SquirrelMail working for a
few weeks now and I think I found a quick cheat on how to deal with the
cookie paths that SquirrelMail sets..
On the reverse proxy, go ahead and set up the two rules to proxy to the back
end SquirrelMail server, in my case:
ProxyPass /serverA/ http://serverA/serverA/
ProxyPassReverse /serverA/ http://serverA/serverA/
On the backend servers, where I have SquirrelMail under http://serverA/webmail/
I added "Alias /serverA/ /WWW/webmail/" and now you can get to
http://serverA/serverA/ both internally and through the reverse proxy.
The issue I was having is since I have 10 Post Office servers with SquirrelMail
and they're all under http://post-office/webmail/ I needed a single instance of
Apache to put in the DMZ for reverse proxying, but I couldn't get away with
http://dmz-server/webmail/ since I have to reverse proxy 10 instances of
SquirrelMail. This workaround appears to work just fine for me..
Anyway, I wanted to ask if anyone else is reverse proxying SquirrelMail out
there and had any other recommendations or better ways to do this? Perhaps
there are some security issues that I may be overlooking that mod_rewrite could
help lock down for me?
Any suggestions or advice would be greatly appreciated!
--
Chris Winterrowd
Unix E-mail Administrator
Texas Instruments Inc.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
