Mailing list

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

Consulting Services

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:

  • Install, configure, customize and optimize the solution to meet your needs
  • Perform a pre or post-implementation audit to make sure your SOGo deployment performs optimally
  • Correct a specific issue with your installation or with components related to it
  • Migrate calendars, address books and emails from a previous solution to SOGo
  • Efficiently integrate SOGo with in-house systems (CRM, ERP, portal, etc.)
  • Develop specific features mentioned in the roadmap, vertical to your environment or others

Contact Us

Support Packages

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
Office Hours : Support Hours are Monday to Friday from 9 am to 6 pm French working days

Supported operating systems:

  • CentOS 7 / 8
  • Red Hat Enterprise Linux (RHEL) 7 / 8 / 9
  • Debian 8 to 12
  • Ubuntu 14 to 24

The support packages do not include:

  • components installation
  • custom development
  • preventive system monitoring
  • training and documentation

The included consulting hours can be consumed for:

  • architecture design and review
  • migration from another system
  • performance tuning
  • best practices

Documentation

SOGo - Installation and Configuration Guide
For SOGo version 5.11.2
Mozilla Thunderbird - Installation and Configuration Guide
For SOGo version 5.11.2
Outlook Connector Configuration Guide
For SOGo version 5.11.2
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

FAQ

How to dedicate a separate SOGo instance for ActiveSync

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.

RedHat 7

  1. 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
  2. Create the home GNUstep directory for the sogoeas user:

    mkdir -p /var/lib/sogoeas/GNUstep/Defaults
  3. Create a /var/lib/sogoeas/GNUstep/Defaults/sogod.plist file, containing this:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    
    <?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>
  4. Ensure a correct ownership of /var/lib/sogoeas/GNUstep/Defaults/sogod.plist:

    chown -R sogoeas:sogo /var/lib/sogoeas
  5. Create a systemd service file - /usr/lib/systemd/system/sogod-eas.service - for the second SOGo instance, containing this:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    
    [Unit]
    Description=SOGo is a groupware server (EAS)
    After=network.target
    After=mariadb.service
    
    [Service]
    EnvironmentFile=-/etc/sysconfig/sogo
    Type=forking
    ExecStart=/usr/sbin/sogod -WOWorkersCount 120 -WOPidFile /var/run/sogo/sogo-eas.pid -WOLogFile /var/log/sogo/sogo-eas.log
    PIDFile=/var/run/sogo/sogo-eas.pid
    User=sogoeas
    
    [Install]
    WantedBy=multi-user.target
  6. 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/
  7. 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
  8. 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.

  9. Start the secondary SOGo instance and restart Apache:

    service sogod-eas start
    service httpd restart

Debian 8 and Debian 9

  1. 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
  2. Create the home GNUstep directory for the sogoeas user:

    mkdir -p /var/lib/sogoeas/GNUstep/Defaults
  3. 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>
  4. 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>
  5. 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
  6. Create a service file /etc/init.d/sogo-eas for the second SOGo instance, containing this:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    
    #!/bin/bash
    ### BEGIN INIT INFO
    # Provides: sogo-eas
    # Required-Start: $remote_fs $network
    # Required-Stop: $remote_fs $network
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # Short-Description: SOGo-EAS server
    ### END INIT INFO
    
    # SOGo init script for Debian GNU/Linux
    #
    # Copyright (C) 2007-2019 Inverse inc.
    #
    # This file is free software; you can redistribute it and/or modify
    # it under the terms of the GNU General Public License as published by
    # the Free Software Foundation; either version 2, or (at your option)
    # any later version.
    #
    # This file is distributed in the hope that it will be useful,
    # but WITHOUT ANY WARRANTY; without even the implied warranty of
    # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    # GNU General Public License for more details.
    #
    # You should have received a copy of the GNU General Public License
    # along with this program; see the file COPYING. If not, write to
    # the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
    # Boston, MA 02111-1307, USA.
    PATH=/sbin:/bin:/usr/sbin:/usr/bin
    
    NAME=sogo
    EASNAME=sogo-eas
    DAEMON=/usr/sbin/sogod
    DESC="SOGo-EAS"
    
    USER=sogo
    EASUSER=sogoeas
    PREFORK=120
    
    PIDFILE=/var/run/$NAME/$EASNAME.pid
    LOGFILE=/var/log/$NAME/$EASNAME.log
    
    if [ -f /etc/default/$NAME ]; then
    . /etc/default/$NAME
    fi
    
    . /lib/lsb/init-functions
    
    if [ ! -x $DAEMON ]; then
    log_failure_msg "$DAEMON is not executable."
    exit 1
    fi
    
    set -e
    
    . /usr/share/GNUstep/Makefiles/GNUstep.sh
    
    DAEMON_OPTS="-WOWorkersCount $PREFORK -WOPidFile $PIDFILE -WOLogFile $LOGFILE"
    
    case "$1" in
    start)
    log_daemon_msg "Starting $DESC" "$EASNAME"
    
    # Enforce directory existence and permissions
    install -o $USER -g $USER -m 775 -d /var/run/$NAME
    install -o $USER -g $USER -m 770 -d /var/spool/$NAME
    install -o $USER -g $USER -m 770 -d /var/log/$NAME
    
    if ! start-stop-daemon -c $EASUSER --quiet --start --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_OPTS
    then
    log_progress_msg "already running"
    fi
    log_end_msg 0
    ;;
    stop)
    log_daemon_msg "Stopping $DESC" "$EASNAME"
    start-stop-daemon --stop --pidfile $PIDFILE --retry=TERM/20/KILL/5 --oknodo
    log_end_msg 0
    ;;
    restart|force-reload)
    log_daemon_msg "Restarting $DESC" "$EASNAME"
    start-stop-daemon --stop --pidfile $PIDFILE --retry=TERM/20/KILL/5 --oknodo
    # Ensure directory's existence and permissions
    install -o $USER -g $USER -m 775 -d /var/run/$NAME
    install -o $USER -g $USER -m 770 -d /var/spool/$NAME
    install -o $USER -g $USER -m 770 -d /var/log/$NAME
    start-stop-daemon -c $EASUSER --quiet --start --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_OPTS
    log_end_msg 0
    ;;
    status)
    status_of_proc -p $PIDFILE "$DAEMON" $EASNAME &amp;&amp; exit 0 || exit $?
    ;;
    *)
    echo "Usage: $EASNAME {start|stop|restart|status}" >&amp;2
    exit 1
    ;;
    esac
    
    exit 0
  7. 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
  8. 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/
  9. 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.

  10. Start the secondary SOGo instance and restart Apache:

    service sogod-eas start
    service httpd restart
January 4, 2019

Bug Tracking System

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:

  • 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