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 :
You can also visit and contribute to the official SOGo Wiki maintained by SOGo users.Go to the Wiki
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:
|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|
|Included Consulting Hours||-||-||4||8|
|Cost||750 €||1,500 €||5,000 €||10,000 €|
If your frontend Web server is nginx and is reporting errors similar to upstream sent too big header, you may need to adjust some proxy parameters to your nginx configuration:
proxy_buffer_size 64k; proxy_buffers 8 64k; proxy_busy_buffers_size 64k;
If you encounter a possible bug with SOGo, you can access our bug tracking system
Please make sure to respect the following guidelines when reporting a bug: