Re: [SOGo] debian nightly
On 19/05/15 21:37, Ludovic Marcotte wrote: It should all be good for Wheezy, Precise and Trusty, all on x86_64. I can confirm it's working for Wheezy, very many thanks. It might be worth mentioning that both the nightly and the stable repositories need to be enabled. Perhaps this is just normal, but I wasn't aware of it. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] debian nightly
On 15/05/15 17:16, Ludovic Marcotte wrote: On 15/05/2015 12:08, Fabio Onorini wrote: So in next nightly builds I'll can re found openchange-ocsmanager ? (maybe from zentyal packages) Yes sir! I encourage folks to test them. Um ... maybe I'm doing something obviously wrong, but I am encountering some dependency problems when trying to install Openchange (prior to installing SOGo: I'm trying to follow the tutorial here: http://iabsis.com/en/community/tuto/openchange-samba4-debian). When I do this: Konsole output apt-get install openchangeserver sogo-openchange openchangeproxy openchange-ocsmanager openchange-rpcproxy python-mysqldb I get this: Konsole output Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: openchange-ocsmanager : Depends: python-ocsmanager (= 3:2.3-zentyal11) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Trying to install python-ocsmanager on its own produces this: Konsole output python-ocsmanager : Depends: python-rpclib (= 2.7.0) but it is not installable Depends: python-sievelib but it is not installable This is using debian-nightly, wheezy, amd64. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Strange problem on installing Openchange server
Hi. I've got SOGo working well on a Debian Wheezy virtual server with Postfix, Dovecot, MySQL and nginx. I was trying to add Outlook interoperability, so I installed the Openchange packages a couple of days ago and started working through the various configuration procedures in the manual. It now seems that Postfix developed an issue more or less at the same time as I installed Openchange. From that point on, incoming emails were regularly being turned away with a message saying Service unavailable - try again later. I reversed all the configuration I'd done, but it was only after uninstalling the Openchange packages that the problem seemed to go away. Has anyone seen this issue, or does anyone have a theory about how it might arise? And how to avoid it?? I do realise that the connection I've made between installing those packages and having Postfix problems could be spurious. Thanks in advance Rob -- Rob Kemp r...@copwick.net -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Strange problem on installing Openchange server
I had installed and configured Samba 4, yes, and it was working (I think). But the trouble started only when I installed Openchange. On 03/07/14 15:48, Steve Ankeny wrote: Do you have an LDAP Server, Microsoft AD or Samba 4 installation? My understanding is that Outlook connectivity via OpenChange does not work without Samba 4 See http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf On 07/03/2014 07:45 AM, Rob Kemp wrote: Hi. I've got SOGo working well on a Debian Wheezy virtual server with Postfix, Dovecot, MySQL and nginx. I was trying to add Outlook interoperability, so I installed the Openchange packages a couple of days ago and started working through the various configuration procedures in the manual. It now seems that Postfix developed an issue more or less at the same time as I installed Openchange. From that point on, incoming emails were regularly being turned away with a message saying Service unavailable - try again later. I reversed all the configuration I'd done, but it was only after uninstalling the Openchange packages that the problem seemed to go away. Has anyone seen this issue, or does anyone have a theory about how it might arise? And how to avoid it?? I do realise that the connection I've made between installing those packages and having Postfix problems could be spurious. Thanks in advance Rob -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Strange problem on installing Openchange server
On 03/07/14 15:22, Sven Schwedas wrote:
On 2014-07-03 13:45, Rob Kemp wrote:
From that point on, incoming emails were regularly being turned away
with a message saying Service unavailable - try again later.
Are there any further details in /var/log/mail.{err,info} ?
This is all I've got:
Jul 1 14:17:50 [servername] postfix/cleanup[4968]: EF5232BE1A9:
milter-reject: END-OF-MESSAGE from server.example.com[###.###.###.###]:
4.7.1 Service unavailable - try again later;
from=fred.blo...@example.com to=j...@example.com proto=ESMTP
helo=server.example.com
I've combed through the log files but been unable to find anything that
explains the problem.
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] nginx
On 02/14/2014 09:02 PM, mayak wrote: On 02/14/2014 07:30 PM, Rob Kemp wrote: I wonder if someone can help me sort out the configuration problem I'm having. I had phpMyAdmin and postfix.admin running on my server, under nginx. Then I installed SOGo, and had the problem I described before where trying to open the SOGo web interface resulted in a 404 error. This turns out to have been because the setup I was using was sending all requests for SSL sites to a directory under /home, whereas of course SOGo lives elsewhere. Disabling the non-SOGo config file solved that problem. However, now I'm not able to work out how to get SOGo AND the other two services to work at the same time. With the SOGo/nginx config file I've been using, anything landing on sogo.server.com is redirected to sogo.server.com/SOGo, and I haven't a clue how to enable sogo.server.com/phpmyadmin. Several hours poring over nginx documentation hasn't helped much either, as I'm a bit thick about that sort of thing. So I was hoping someone who might have a similar setup could give me a pointer (or post a config file) that shows how SOGo can coexist with phpMyAdmin or something similar. Thanks Rob Hi Rob, If I have understood you correctly, you probably want use to use virtual hosts: a.domain.com b.domain.com c.domain.com Each of these would have a `container` describing SSL certs, home directory, etc ... Cheers M That's right, and with a, b, and c being the same domain. I've tried to set it up that way, but on restarting nginx the non-SOGo virtual hosts throw up a warning that they are duplicates and are being ignored. I'll go back to the nginx documentation. Thanks Rob -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] nginx
I wonder if someone can help me sort out the configuration problem I'm having. I had phpMyAdmin and postfix.admin running on my server, under nginx. Then I installed SOGo, and had the problem I described before where trying to open the SOGo web interface resulted in a 404 error. This turns out to have been because the setup I was using was sending all requests for SSL sites to a directory under /home, whereas of course SOGo lives elsewhere. Disabling the non-SOGo config file solved that problem. However, now I'm not able to work out how to get SOGo AND the other two services to work at the same time. With the SOGo/nginx config file I've been using, anything landing on sogo.server.com is redirected to sogo.server.com/SOGo, and I haven't a clue how to enable sogo.server.com/phpmyadmin. Several hours poring over nginx documentation hasn't helped much either, as I'm a bit thick about that sort of thing. So I was hoping someone who might have a similar setup could give me a pointer (or post a config file) that shows how SOGo can coexist with phpMyAdmin or something similar. Thanks Rob -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] nginx
Thanks Andy. All I did, I think, was to change the hostname and the
location of the SSL certificates. (I've replaced the server name with
X's below, but that was accurately entered without typos in the file I
was trying to use).
-
server {
listen 80 default;
server_name XXX.XXX.com;
## redirect http to https ##
rewrite ^ https://$server_name$request_uri? permanent;
}
server {
listen 443;
server_name XXX.XXX.com;
root /usr/lib/GNUstep/SOGo/WebServerResources/;
ssl on;
ssl_certificate /etc/nginx/certs/XXX.XXX.com.crt;
ssl_certificate_key /etc/nginx/certs/XXX.XXX.com.key;
location = /
{
rewrite ^ https://$server_name/SOGo;
allow all;
}
# For IOS 7
location = /principals/
{
rewrite ^ https://$server_name/SOGo/dav;
allow all;
}
location ^~/SOGo {
proxy_pass http://127.0.0.1:2;
proxy_redirect http://127.0.0.1:2 default;
# forward user's IP address
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $server_name;
proxy_set_header x-webobjects-server-url $scheme://$host;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
client_max_body_size 50m;
client_body_buffer_size 128k;
break;
}
location /SOGo.woa/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location /SOGo/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
location
^/SOGo/so/ControlPanel/Products/[^/]*UI/Resources/.*\.(jpg|png|gif|css|js)$
{
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
}
-
On 02/13/2014 07:09 PM, Andy Tuinman wrote:
Can you post your config file instead of the default? You have to make
a few adjustments in the file. So if you post your file i can look at it.
Op 13 feb. 2014 19:45 schreef rpk...@copwick.net
mailto:rpk...@copwick.net:
Hi. I'm trying to get SOGo working with my nginx installation, but
I'm a bit
of a novice with both nginx and SOGo.
I'm using the nginx config file that's posted here:
http://wiki.sogo.nu/nginxSettings
However, I'm getting a 404 Not Found error from nginx when I try
to access /
SOGo.
If anyone knows of an obvious explanation, I'd be grateful to hear it.
(The server is running Debian 7 with MySQL.)
Rob
--
users@sogo.nu mailto:users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] nginx
Thanks, it turned out that while following some instructions of the
internet (silly, I know!) I had put in place some configuration file
that was redirecting all SSL connections somewhere different. So I have
sorted it out now. I'll have a look at your configurations though - many
thanks.
Rob
On 02/13/2014 08:36 PM, mayak wrote:
On 02/13/2014 08:09 PM, Andy Tuinman wrote:
Can you post your config file instead of the default? You have to make
a few adjustments in the file. So if you post your file i can look at it.
snip
here's mine:
url is: ghttps://sogo.domain.com
server {
listen 443;
server_name sogo.domain.com;
rewrite ^/$ https://sogo.domain.com/SOGo;
access_log /var/log/nginx/sogo-access.log;
error_log /var/log/nginx/sogo-error.log;
location ^~ /SOGo {
proxy_passhttp://127.0.0.1:2/SOGo;
proxy_redirecthttp://127.0.0.1:2/SOGo/;
proxy_set_headerX-Real-IP$remote_addr;
proxy_set_headerX-Forwarded-For
$proxy_add_x_forwarded_for;
proxy_set_headerHostsogo.domain.com;
proxy_set_headerx-webobjects-server-protocolHTTP/1.0;
proxy_set_headerx-webobjects-remote-hostsogo.domain.com;
proxy_set_headerx-webobjects-server-namesogo.domain.com;
proxy_set_headerx-webobjects-server-url
https://sogo.domain.com;
proxy_connect_timeout90;
proxy_send_timeout90;
proxy_read_timeout90;
proxy_buffer_size4k;
proxy_buffers16 64k;
proxy_busy_buffers_size64k;
proxy_temp_file_write_size64k;
client_max_body_size50m;
client_body_buffer_size128k;
break;
}
location ^~ /Microsoft-Server-ActiveSync {
proxy_pass http://127.0.0.1:2/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect
http://127.0.0.1:2/Microsoft-Server-ActiveSync /;
}
location ^~ /SOGo/Microsoft-Server-ActiveSync {
proxy_pass http://127.0.0.1:2/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect
http://127.0.0.1:2/SOGo/Microsoft-Server-ActiveSync /;
}
location /.woa/WebServerResources/ {
alias /usr/lib64/GNUstep/SOGo/WebServerResources/;
}
location /SOGo.woa/WebServerResources/ {
alias/usr/lib64/GNUstep/SOGo/WebServerResources/;
}
location /SOGo/WebServerResources/ {
alias/usr/lib64/GNUstep/SOGo/WebServerResources/;
}
location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias/usr/lib64/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
}
--
users@sogo.nu
https://inverse.ca/sogo/lists
