Community Support

Community support is offered through the mailing list. You can subscribe to it and ask questions related to SOGo.

  1. Register (free)
  2. Search if question has been answered
    Online archives of the mailing list are available from :
    https://www.mail-archive.com/users@sogo.nu/
  3. Ask question
    Once subscribed, write to users@sogo.nu to post to the mailing list.

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 :

  • post constructive emails - rants will be automatically discarded
  • consult the FAQ for previously answered questions
  • send plain text message (no HTML or Rich Text) to avoid getting rejected by our spam filters
  • avoid replying to a message on top of the quoted text of the previous correspondence

Wiki

You can also visit and contribute to the official SOGo Wiki maintained by SOGo users.

Go to the Wiki

Documentation

SOGo - Installation and Configuration Guide
For SOGo version 5.10.0
Mozilla Thunderbird - Installation and Configuration Guide
For SOGo version 5.10.0
Outlook Connector Configuration Guide
For SOGo version 5.10.0
SOGo - Installation and Configuration Guide
For SOGo version 4.3.2
Mozilla Thunderbird - Installation and Configuration Guide
For SOGo version 4.3.2
Outlook Connector Configuration Guide
For SOGo version 4.3.2
SOGo - Installation and Configuration Guide
For SOGo version 3.2.10
Mozilla Thunderbird - Installation and Configuration Guide
For SOGo version 3.2.10
Native Microsoft Outlook Configuration Guide
For SOGo version 3.2.10
SOGo - Installation and Configuration Guide
For SOGo version 2.4.3
Mozilla Thunderbird - Installation and Configuration Guide
For SOGo version 2.4.3
Native Microsoft Outlook Configuration Guide
For SOGo version 2.4.3

Bug Tracking System

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:

  • verify that the bug you found is not already known or even fixed in the trunk version
  • make the actual facts very clear; be precise, we need to be able to reproduce the problem
  • explain your speculations, if any
  • add a screenshot to the ticket if appropriate