Hello I assume you didn't purge your old SOGo 1.3.16 installation? Then the things in .GNUstepDefaults are old configuration of it. Remove it, then I think it will work as expected.
When there is a syntax error in the configuration of SOGo, then sogod will ignore this configuration and use defaults (which isn't functional at all). Kind regards, Christian Mack Am 2015-02-26 um 16:28 schrieb Louis-Philippe: > Hi, > I forget to mention, it's a fresh install, but, at the begining, I > discovered that SOGo 1.3.16 is in the official Debian (wheezy) repository. > I installed this version, but I didn't configure it. I remove it and > install 2.2.16. This error can broke something ? > > In the documentation ( > http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf) on page 10, > I can read "If SOGo refuses to start due to syntax errors in its > configuration file, plparse is helpful for finding these, as it indicates > the line containing the problem." > > So, I removed a semicolon in the file. I ran "plparse" an I get an error. I > restart SOGo (with the erronous conf file) and it restart ! > > Why ? > > > > > 2015-02-20 9:56 GMT-05:00 Louis-Philippe <[email protected]>: > >> Hello, >> >> >> 2015-02-20 7:46 GMT-05:00 Christian Mack <[email protected]>: >> >>> Hello >>> >>> Did you upgrade from a pre SOGo 2.0.5 installation? >>> If yes, did you do the steps described in the "SOGo Installation Guide" >>> chapter "Upgrading"? >>> >>> >> >> No, it's a fresh new install on Debian Wheezy (64 bits) . My production >> server is an old Debian Squeeze (32 bits). >> >> I made the folder /home/sogo because Sogo floods my log if it doesn't >> exist. >> >> The file .GNUstepDefaults is empty (some lines created by SOGo). The empty >> .GNUstepDefaults overwrites ALL sogo.conf ? not some parameters (in the >> case it's not an empty file) ? >> >> I read the "chapter 10 - Upgrading" and nothing to do ... >> >> Kind regards, >> >> >> -- >> Louis-Philippe Gauthier >> >> >> >>> I too had problems of this kind, before doing so. >>> That was, because the old GNUstep defaults were still in effect. >>> You can check this with sogo-tool. >>> /usr/sbin/sogo-tool dump-defaults >>> >>> This should deliver an empty configuration. >>> If not, that is your problem. >>> >>> >>> Kind regards, >>> Christian Mack >>> >>> Am 2015-02-18 um 19:26 schrieb Louis-Philippe: >>>> Hi, >>>> >>>> Before, I had a lot of "sogod[2726] Defaults path >>>> '/home/sogo/GNUstep/Defaults' does not exist - failed to create it." >>>> >>>> So, I created /home/sogo and the error message change to " [ERROR] >>> |SOGo| >>>> No value specified for 'SOGoProfileURL'". >>>> >>>> But it is in the file /etc/sogo/sogo.conf. >>>> >>>> It seems that it doesn't read the file in /etc/sogo/ . >>>> >>>> I have something to do for forcing the use of /etc/sogo/sogo.conf >>> instead >>>> of /home/sogo/GNUstep/Defaults/.... ? >>>> >>>> Thanks >>>> >>>> >>>> 2015-02-18 11:12 GMT-05:00 Carl Byington <[email protected]>: >>>> >>>> >>>>>>> In sogo.log, all time are UTC instead of local time. We are UTC -0500 >>>>>>> and I >>>>>>> have in /etc/sogo/sogo.conf: "SOGoTimeZone = America/Montreal;" >>>>>>> Why ? I made a dpkg-reconfigure tzdata and timezone is well >>>>>>> configured. >>>>>>> Did I miss something ? >>>> >>>> At least on Centos, sogo seems to ignore the zone in >>>> /etc/sogo/sogo.conf, and instead uses the $ZONE setting from >>>> /etc/sysconfig/clock. On Centos, that $ZONE value may contain embedded >>>> blanks, which then causes sogo to use UTC. >>>> >>>> http://www.five-ten-sg.com/mapper/blog/openchange >>>> -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
