Um, why don't you just edit /home/sogo/GNUstep/Defaults file as the sogo user after your initial setup?
Regards, Mark On 18 Feb 2011, at 10:59, Michael Crilly <[email protected]> wrote: > Greetings, > > When I first installed SOGo and realized it used GNUStep (urgh!) I wasn't too > impressed. It's a horrid way of configuring a UNIX application and it simply > doesn't fit in with the UNIX way of thinking. All that being said, I've > written a Perl script that I've found, so far, makes my life a lot easier... > > The script basically reads in a SOGo.conf file, which is in Apache format (a > very common UNIX configuration file format), and parses it, converting each > variable declaration into a 'defaults write <domain> <key> <value>' command. > It works perfectly so far, and even supports a variable amount of > SOGoUserSources entries/dictionaries. I've found this makes configuring SOGo > A LOT easier and if you need to change anything, it's incredibly easy too and > simpler than remembering the SOGoVariable, su'ing as the sogo user and typing > out the defaults command for each and every individual option - ugh. > > One thing it doesn't do at present is checking the variable names for > potential mistakes or any kind of error checking, for that matter. See below > why. > > If people would find this script useful, then I will refine the script and > add a lot of other support (logging, rollback, etc) and try and get it into > the official Debian linux package repository, amongst other things. If people > don't feel as though this would be helpful, then I will leave it as it is and > be done with it. > > Let me know. > > Kind regards, > > -- > Michael Crilly > Comtek IT Systems Administrator > E: [email protected] > > Comtek Network Systems UK Ltd > http://www.comtek.co.uk/ > > -- > [email protected] > https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
