General discussion on installation and configuration of SOGo

Text archives Help

Re: [SOGo] Re: Upgrading from sogo 1.3.4 to 1.3.11

Chronological Thread 
  • From: André Schild < >
  • To:
  • Subject: Re: [SOGo] Re: Upgrading from sogo 1.3.4 to 1.3.11
  • Date: Fri, 27 Jan 2012 16:58:18 +0100

Hello Kyle,

I remember that there is a SQL script you must run manually to
make some schema upgrades.

Make sure that you use the correct Sogo.conf file for apache
Might be saved under somthing like sogo.rpmnew in a upgrade

If you had enabled out of office messages, then make sure you
configure the "Turnoff" thing correctly. (Needs a cron job)
Otherwise users will enter a expire date, but the ooo messages will not be turned off.

Otherwise I think things should go smooth.


Am 27.01.2012 06:44, schrieb kyle:
Looking over the install guide, it does seem there have been database
changes(just judging by the addition of OCSSessionsFolderURL in the
guide). I am using the RHEL rpms found on the sogo site. I don't run
mysql locally on my lab sogo servers, so if any of the rpms perform
database updates, then they wouldnt(and didnt) run on my lab mysql
server. So, can someone provide me with some guidance on what required
params need to be added to .GNUstepDefaults, and how to perform any
updates to the database(mysql)? Recall, I am updating from 1.3.4 to


On Thu, Jan 26, 2012 at 10:27 PM,
kyle< >
Hi, I am looking to upgrade from my 1.3.4 install to 1.3.11. I have
been researching it, and noting some issues others have had when
upgrading a 1.3.4 installation(i.e. md5crypt issues, bug 0000703).
But, wondering if there are other issues I should be looking out for?

My install is centos(5.6), i386, mysql(percona 5.5), openldap auth.

Archive powered by MHonArc 2.6.18.

Top of page