2013-09-05 17:32 keltezéssel, stev...@cinergymetro.net írta:
Pg. 12 [14] of 'SOGo Native Microsoft Outlook Configuration 2.0.7'
Apache Configuration for Web Services
The OpenChange web services consist of two components:
1. OCS Manager which is used for autodiscovery and freebusy lookups on Outlook
2007
and 2010. This service runs in its own application server which listens on
127.0.0.1:5000 by default. Apache needs to be configured to forward certain
requests
to it to make it accessible from the outside.
Note that this service MUST be accessible over HTTPS, otherwise Outlook won't
use it.
2. RPC Proxy which is used for RPC over HTTP (“Outlook Anywhere”)
This service runs as a WSGI application under apache (mod_wsgi).
While HTTPS is not required to access this service, it is strongly recommended.
Is it absolutely necessary to use HTTPS and SSL for Outlook connectivity?
I am experiencing the usual error: Cannot find the Exchange server ...
My thinking is that I need to enable HTTPS for OCSManager, and that means going
back and enabling SSL in LDAP, IMAP, SOGo, Apache, etc. (which is doable) I'm
on a private network.
If you use only over lan some of your services, then they should not be
over SSL.
But, if you use some services from the internet side, then strongly
recommended use them over SSL.
Most of services can communicate over SSL and plain simultaneously, so
you don't need to set up everything over SSL.
If you use just the Outlook Anywhere and SOGo WebUI from internet side,
the Apache SSL settings are enough - but, you need to deny the access to
TCP/80 from the internet side on your firewall.
I think, if you setup everything to over SSL working posibilities, you
cannot make mistake.
IMAP/POP3/SMTP/HTTP/LDAP/etc. can work in plain and over SSL mode
simultaneously, and you need to enabled from the internet only the
following ports: 443, 465, 636, 993, 995 - and sieve 4190/2000 (only in
TLS mode).
--
users@sogo.nu
https://inverse.ca/sogo/lists
