
POWERED BY MDAEMON!- These forums are provided by MDaemon Technologies for user-to-user support and discussion.

To unsubscribe from this mailing list send an email to. View/reply at WorldClient on Apache Proxy -MD-WC-ISSUES- This list is for questions and discussions about MDAEMON and WorldClient. Visit us on Facebook | LinkedIn | YouTubeįrom: On Behalf Of Ashley Griffin Wednesday, Aug3:28 PM MDaemon Technologies | Simple Secure Email If you run into any problems with setting this up, perhaps some of our forum members with Apache experience will be able to offer assistance. However, if you do decide to try setting this up or run MD Webmail under Apache, please let us know if you are successful. I am not aware of any issues where IP Screening functionality is lost when running Apache as a proxy server for MDaemon Webmail.
#MDAEMON WORLDCLIENT WINDOWS#
NOTE: The instructions provided in that article are for running Apache within a Windows environment. However, if you are looking to gain an increase in performance, then IIS or Apache might be a better solution. Regarding you question about whether you are better off running MDaemon Webmail under Apache: I would think that you would be better off running it under the built-in web server, if security is your concern. I do not have any helpful input for you regarding setting up MDaemon Webmail (WorldClient) to run under Apache, but if you would like to try setting it up, we do have that article in our Knowledge Base listed under a new article number: If we use Apache as the server itself (running the DLL) i assume we do not loose the IP filtering in World Client, if thats the case then i would be interested to check this out.

#MDAEMON WORLDCLIENT HOW TO#
I have also read how to use Apache as a pure proxy (KBA-01715) which appears to be a nice solution, i know this will loose some of the IP screening in World client, but appears to tamper way less with World Client engine.

I understand the DLL runs in the CGI part of apache, some input here would be good. This is the "best" solution however kinda stuck with it for now.Īt the moment World Client has an SSL internally, ive read quiet a bit of documentation on this so raised a few questions.Īm i better running the WorldClient end IN Apache which should have been under KBA-01525, however that seems to have gone from your website. We have a need to use the Apache server being the front end of World Client.
