Michael-
Michael Crilly wrote:
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.
I'm not sure if it's a fluke or not with my system, but if you type in
the config file once (of course making a backup to avoid the surprise of
having your configuration wiped away when you make a mistake) and only
edit the file instead of using the "defaults write" commands, it will
maintain it's appearance as in the SOGo manual which I think is easy to
edit. I only experience the conversion to the not so legible XML-style
format if I use the "defaults write" to add something.
Steve
--
[email protected]
https://inverse.ca/sogo/lists
