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 |
This article describes how to install a production version of SOGo; you need to follow theses steps if you prefer to use the unsupported nightly builds.
In order to access the production builds, you need a proper support contract from Alinto. Continue with the configuration once you received your username and password.
Alinto signs its RPM packages with its GPG key. Integrity verification happens all by itself on package installation, all you need to do is first import the key into your rpm keychain:
rpm --import "https://keys.openpgp.org/vks/v1/by-fingerprint/74FFC6D72B925A34B5D356BDF8A27B36A6E2EAE9"
Some of the dependencies are provided by external repositories.
You will need to add the EPEL to your yum repositories.
On RedHat Enterprise Linux 6 (and compatibles), gnustep packages have to be excluded from the EPEL repository in order to use the packages available on Alinto SOGo Repository.
Simply add the following line to the EPEL repo definition:
[epel]
# ...
exclude=gnustep-*
On RedHat Enterprise Linux 5 (and compatibles), you also need to add RPMForge to your yum repositories.
Once the package is installed, you’ll also need to activate the RPMForge extras repository by modifying /etc/yum.repos.d/rpmforge.repo:
[rpmforge-extras]
# ...
enabled=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel6]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/5/rhel/6/$basearch
gpgcheck=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel7]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/5/rhel/7/$basearch
gpgcheck=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel8]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/5/rhel/8/$basearch
gpgcheck=1
Some of the dependencies are provided by external repositories.
You will need to add the EPEL to your yum repositories.
On RedHat Enterprise Linux 6 (and compatibles), gnustep packages have to be excluded from the EPEL repository in order to use the packages available on Alinto SOGo Repository.
Simply add the following line to the EPEL repo definition:
[epel]
# ...
exclude=gnustep-*
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel6]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/2/rhel/6/$basearch
gpgcheck=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel7]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/2/rhel/7/$basearch
gpgcheck=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel8]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/2/rhel/8/$basearch
gpgcheck=1
Create a new yum configuration file (such as /etc/yum.repos.d/SOGo.repo
) with the following content:
[sogo-rhel9]
name=Alinto SOGo Repository
baseurl=https://<username>:<password>@packages.sogo.nu/release/2/rhel/9/$basearch
gpgcheck=1
Once the repositories above are configured, simply install SOGo:
yum install sogo
Replace the SOGo 2.x.x yum configuration file’s “baseurl” with the one for 5.x.x, clear your cache with “yum clean all” then proceed to upgrade using “yum update”.
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: