Re: [SOGo] Alternative port with SSL
It looks like I have it.
I had to copy over the SSL configs to the virtualhost section to make the
SSL work.
Listen *:6443
NameVirtualHost *:6443
VirtualHost *:6443
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/ssl/usr-2-cert.pem
SSLCertificateKeyFile /etc/ssl/private/usr-2-key.pem
Files ~ \.(cgi|shtml|phtml|php3?)$
SSLOptions +StdEnvVars
/Files
Servername FQDN
DocumentRoot /usr/lib/GNUstep/SOGo/WebServerResources/
ErrorLog /var/log/httpd/sogoerror.log
Customlog /var/log/httpd/sogoaccess.log combined
ServerSignature Off
Alias /SOGo.woa/WebServerResources/
/usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*)
/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2
Directory /usr/lib/GNUstep/SOGo/
SSLOptions +StdEnvVars
AllowOverride None
Order deny,allow
Allow from all
IfModule expires_module
ExpiresActive On
ExpiresDefault access plus 1 year
/IfModule
/Directory
LocationMatch
^/SOGo/so/ControlPanel/Products/.*UI/Resources/.*\.(jpg|png|gif|css|js)
SetHandler default-handler
/LocationMatch
ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On
ProxyPass /SOGo http://127.0.0.1:2/SOGo retry=0
Proxy http://127.0.0.1:2/SOGo
RequestHeader set x-webobjects-server-port 6443
RequestHeader set x-webobjects-server-name FQDN:6443
RequestHeader set x-webobjects-server-url https://FQDN:6443
RequestHeader set x-webobjects-server-protocol HTTP/1.0
RequestHeader set x-webobjects-remote-host %{REMOTE_HOST}e
env=REMOTE_HOST
AddDefaultCharset UTF-8
Order allow,deny
Allow from all
/Proxy
## We use mod_rewrite to pass remote address to the SOGo proxy.
# The remote address will appear in SOGo's log files and in the X-Forward
# header of emails.
# RewriteEngine On
# RewriteRule ^/SOGo/(.*)$ /SOGo/$1 [env=REMOTE_HOST:%{REMOTE_ADDR},PT]
# Redirect permanent /index.html http://sogo.example.com/SOGo
/virtualhost
Then I changed the extensions.rdf file to use the new port:
?xml version=1.0?
!DOCTYPE RDF
RDF xmlns=http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:isi=http://inverse.ca/sogo-integrator/;
xmlns:em=http://www.mozilla.org/2004/em-rdf#;
xmlns:NC=http://home.netscape.com/NC-rdf#;
Seq about=http://inverse.ca/sogo-integrator/extensions;
isi:updateURL=https://FQDN:6443/SOGo-configs/updates.php?plugin=%ITEM_ID%amp;version=%ITEM_VERSION%amp;platform=%PLATFORM%
li
/li
/Seq
/RDF
And Thunderbird and SOGo worked!
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] Alternative port with SSL
Hello everyone, I am trying to configure SOGo to run on an alternate SSL port but I am having to success. Does anyone have any experience with doing this? Will it break any functionality with the Thunderbird plugin. I am only interested in changing ports for the SOGo connection and webmail. IMAPS and STMPS will stay the same. Thank you in advance for your help. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Alternative port with SSL
We were able to get sogo working over ssl on nginx with port 444 (meaning that to log into the sogo web client we could do that over part 444). The browser complains, but it did work. We were even able to get Thunderbird working, but had trouble getting integrator working because it wasn't connecting and wouldn't offer to add an exception (from what I can remember). We gave up, bought a ssl cert and just used 443 in the end and had help from Inverse setting it up. On Friday, February 21, 2014 5:02 PM, Kevin Brault kbra...@live.com wrote: Hello everyone, I am trying to configure SOGo to run on an alternate SSL port but I am having to success. Does anyone have any experience with doing this? Will it break any functionality with the Thunderbird plugin. I am only interested in changing ports for the SOGo connection and webmail. IMAPS and STMPS will stay the same. Thank you in advance for your help. -- users@sogo.nu https://inverse.ca/sogo/lists-- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Alternative port with SSL
Would you be able to share your SOGo.conf file that you used? Thanks J. wrote in message news:1393032178.21878.yahoomail...@web122103.mail.ne1.yahoo.com... We were able to get sogo working over ssl on nginx with port 444 (meaning that to log into the sogo web client we could do that over part 444). The browser complains, but it did work. We were even able to get Thunderbird working, but had trouble getting integrator working because it wasn't connecting and wouldn't offer to add an exception (from what I can remember). We gave up, bought a ssl cert and just used 443 in the end and had help from Inverse setting it up. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Alternative port with SSL
Unfortunately I don't have the sogo.conf file that was the one that worked over
port 444 (grep 444 * in my sogo dir brings up nothing). Here's a few lines from
the nginx conf file:
## this one is for the SOGo web client
server {
listen 192.168.1.4:444;
server_name mail.mydomain.com;
#root /usr/lib/GNUstep/SOGo/WebServerResources/;
root /var/www/mail.mydomain.com;
ssl on;
On Friday, February 21, 2014 6:21 PM, Kevin kbra...@live.com wrote:
Would you be able to share your SOGo.conf file that you used?
Thanks
J. wrote in message
news:1393032178.21878.yahoomail...@web122103.mail.ne1.yahoo.com...
We were able to get sogo working over ssl on nginx with port 444 (meaning
that to log into the sogo web
client we could do that over part 444). The
browser complains, but it did work. We were even able to get Thunderbird
working, but had trouble getting integrator working because it wasn't
connecting and wouldn't offer to add an exception (from what I can
remember). We gave up, bought a ssl cert and just used 443 in the end and
had help from Inverse setting it up.
--
users@sogo.nu
https://inverse.ca/sogo/lists--
users@sogo.nu
https://inverse.ca/sogo/lists
