Community support is offered through the mailing list. You can subscribe to it and ask questions related to SOGo.
The SOGo community is very large and active so do not hesitate to subscribe to the mailing list and ask questions. However, please make sure to respect the following guidelines when posting a new message :
Groupware deployment projects are complex in nature because they usually involve many different technologies. We have done hundreds of large-scale deployment projects for prestigious organizations, all around the world. Let us help you make this deployment project a success by using our unmatched expertise!
If you are looking for a SOGo expert to help you:
Bronze |
Silver |
Gold |
Platinum |
|
---|---|---|---|---|
Duration | 1 year prepaid contract. Unused tickets are not prolonged. | |||
Support Method | Support Portal | Support Portal / Phone | Support Portal / Phone | Support Portal / Phone |
Response Time | 1 business day | 4 business hours | 2 business hours | 1 business hour |
Support Hours | Office Hours | Office Hours | Office Hours | Office Hours |
Notifications | None | Security | Security / Bug Fixes | Security / Bug Fixes |
Bug Fixes | No | No | No | Yes |
Included Incidents | 5 | 10 | 30 | 75 |
Included Consulting Hours | - | - | 4 | 8 |
Cost | 500 € | 1,500 € | 5,000 € | 7,500 € |
Order | Order | Order | Order |
A second SOGo instance (sharing almost everything with the primary SOGo instance) can be deployed and dedicated for ActiveSync clients. As you many know, ActiveSync clients tend to aggressively hold on to their connections; that behavior may starve web interface clients. Setting up a second instance ensures web interface clients get their fair share of connections.
Below are the steps to create a second SOGo instance, which has exactly the same configuration as the primary one, except it listens on a different TCP port (30000 instead of 20000); Apache will forward ActiveSync requests to port 30000 while regular web interface clients will continue to be forwarded to port 20000.
Add a new system user (sogoeas) dedicated for the second instance:
useradd -d /var/lib/sogoeas -g sogo -c "SOGo EAS daemon" \
-s /usr/sbin/nologin -r sogoeas
Create the home GNUstep directory for the sogoeas user:
mkdir -p /var/lib/sogoeas/GNUstep/Defaults
Create a /var/lib/sogoeas/GNUstep/Defaults/sogod.plist
file, containing this:
|
|
Ensure a correct ownership of /var/lib/sogoeas/GNUstep/Defaults/sogod.plist
:
chown -R sogoeas:sogo /var/lib/sogoeas
Create a systemd service file - /usr/lib/systemd/system/sogod-eas.service
- for the second SOGo instance, containing this:
|
|
Make the sogoeas user able to read/write SOGo data:
chmod 0640 /etc/sogo/sogo.conf
chmod 0775 /var/run/sogo/ /var/lib/sogo/
chmod 0770 /var/log/sogo/
Ensure that /var/run/sogo
keeps its permissions at reboot; change this line in /etc/tmpfiles.d/sogo.conf
:
d /var/run/sogo 0755 sogo sogo
to:
d /var/run/sogo 0775 sogo sogo
Modify your apache proxy configuration so that /Microsoft-Server-ActiveSync
points to the secondary SOGo instance; change this line in /etc/httpd/conf.d/SOGo.conf
:
ProxyPass /Microsoft-Server-ActiveSync \
http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=700
to:
ProxyPass /Microsoft-Server-ActiveSync \
http://127.0.0.1:30000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=700
You may also want to adjust the MaxRequestWorkers directive in Apache to accomodate the extra connections.
Start the secondary SOGo instance and restart Apache:
service sogod-eas start
service httpd restart
Add a new system user (sogoeas) dedicated for the second instance:
useradd -d /var/lib/sogoeas -g sogo -c "SOGo EAS daemon" \
-s /usr/sbin/nologin -r sogoeas
Create the home GNUstep directory for the sogoeas user:
mkdir -p /var/lib/sogoeas/GNUstep/Defaults
On Debian 8, create a /var/lib/sogoeas/GNUstep/Defaults/.GNUstepDefaults
file, containing this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml">
<plist version="0.9">
<dict>
<key>NSGlobalDomain</key>
<dict>
</dict>
<key>sogod</key>
<dict>
<key>WOPort</key>
<string>30000</string>
</dict>
</dict>
</plist>
On Debian 9, create a /var/lib/sogoeas/GNUstep/Defaults/sogod.plist
file, containing this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml">
<plist version="0.9">
<dict>
<key>WOPort</key>
<string>30000</string>
</dict>
</plist>
Ensure a correct ownership of /var/lib/sogoeas/GNUstep/Defaults/.GNUstepDefaults
or /var/lib/sogoeas/GNUstep/Defaults/sogod.plist
:
chown -R sogoeas:sogo /var/lib/sogoeas
Create a service file /etc/init.d/sogo-eas
for the second SOGo instance, containing this:
|
|
Make the service active and started at boot:
chown root:root /etc/init.d/sogo-eas
chmod 0755 /etc/init.d/sogo-eas
systemctl enable sogo-eas
Make the sogoeas user able to read/write SOGo data:
chmod 0640 /etc/sogo/sogo.conf
chmod 0775 /var/run/sogo/ /var/lib/sogo/
chmod 0770 /var/log/sogo/
Modify your apache proxy configuration so that /Microsoft-Server-ActiveSync
points to the secondary SOGo instance; change this line in /etc/httpd/conf.d/SOGo.conf
:
ProxyPass /Microsoft-Server-ActiveSync \
http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=700
to:
ProxyPass /Microsoft-Server-ActiveSync \
http://127.0.0.1:30000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=700
You may also want to adjust the MaxRequestWorkers directive in Apache to accomodate the extra connections.
Start the secondary SOGo instance and restart Apache:
service sogod-eas start
service httpd restart
If you encounter a possible bug with SOGo, you can access our bug tracking system.
By default you will have the viewer rights, but you need to contact us to upgrade your account to report issues (the procedure is detailed on the bug tracker).
Please make sure to respect the following guidelines when reporting a bug: