I'm ok with all of the open discussion. However, I'm far from inexperienced and I'd like to think I'm fairly intelligent.
I've seen good documentation and I can see the difference of what's being discussed here. Once you go outside the cookie cutter world of the existing documentation, well, it seems you're quite screwed. Well, good for the existing documentation with the existing cookie cutters. However, never let it be said that I didn't try to give insight and try to help the product as I can see some serious superiority here. I've now realized that the prevalent attitude is "We think it's great documentation, why improve it?" That's ok, too. However, don't expect people to help when they offer some very simple methods of how to improve it and it becomes "Heck no! We think it's good enough." :-( Let's face it, I have enough work in my own life. I've offered some very simple things that could be done, and it seems that people want me to do the documentation or just be quiet. That's fine. Good luck with this project. I'll try to help round out the FreeBSD port with Jim, at least there'll be turnkey solution for the "Server OS". Oh and, yes, if anyone has been reading any of the other threads that I've been posting, I have been improving the installation with information on how to create a more well-rounded FreeBSD port so that it's like everything on FreeBSD.... "it just works". It will become, go to /usr/ports/sysutils/sogo and type "make install" Change a couple of configuration files and turn it on. Done. However, knowing it doesn't work like that elsewhere, will make me sad. Also, if Zimbra gets their engineering to look at not hard coding paths, there will be a Zimbra port and their documentation is, presently, superior and the system is pretty turnkey. I'll just migrate. *shrug* P. ________________________________ From: ABBAS Alain <[email protected]> To: [email protected] Sent: Sunday, July 7, 2013 5:06 PM Subject: Re: [SOGo] Dear progammers and architects hello I m following this discution with some interest and some of the words makes me .... Exchange in 4 hours ? you dream Exchange is a complicated system and you have to learn about a lot of things too . Try to make public activesync for example without reverse proxy and your windows will be hacked in a few time. Try to read the configuration of an apache of a nginx for exchange and you will cry too. Try to make exchange runing with an no uniform park (office 2003 , office 2007 , office ...) and you will cry too. I m new in Sogo and we have planned to migrate your customers from kolab (who is a goo email server but a weak groupware storage) and we configured and learned all in 2 days . All did run and we didnt have problems with configuration. We use Debian, Postgress and openLDAP (kolab) and all run like a charm. For now we don t use openchange and outlook connectivity but we planned to test it before september Really Sogo is THE RESPONSE against exchange and THANKS GUYS FOR YOUR WORK.I participated to Kolab development i m the creator of the backend Kolab for Zpush (who was integrated in standard in Kolab 2.3.4) and have some experiences on the mail servers and i know what mean opensource development and how peoples react. You try to set the system without really try to knowledge what really Sogo does and without plan . did you think why mysql versus postgress ? did you think why 386dir versus openldap ? did you make a map of your system and how all the bricks works between them ? i guess not otherside you shouldn t have this kind of problems. Exhange gives to you the illusion of the knowlege.In microsoft you spend 10% of your time to make the system runs at 90% and 90% of your time for the another 10% In Unix world (i mean UNIX in general and not Linux) this is the inverse you have 90% of the tim e to aquire the knowledge and after 10% to make the system runs ... Unix world is not for mouse clickers ... My experience since 1 month of SOGO is more than well and definitively we adopted the system (i migrated last week a customer with 1500 accounts in less than one day .......) Alain Abbas Regards Le Dimanche 7 Juillet 2013 22:34 CEST, Steve Ankeny <[email protected]> a écrit: I appreciate the discussion, and I appreciate having clear, concise >documentation. > >However, I find the SOGo documentation adequate for me, even though I am >a relatively inexperienced administrator (having come from the Microsoft >side of things to Linux and open source) > >IF the same amount of time we're spending to critique SOGo documentation >were spent in documenting how to change "example.com" in the ZEG to a >domain o f your choice, we'd have something! > >The ZEG is fully configured and "ready to go," and except for very-large >domains, the ZEG is fully adequate with the exception of changing the >domain. We hired Inverse to do that work, and we're happy! > >Download the ZEG; set it up as a virtual machine; change the domain; and >you're ready to go with no fuss. > >On 07/07/2013 03:43 PM, Schmitt, Christian wrote: >> I know that it is not a problem of sogo, but i'm a developer and not a >> system administrator. I mean if I really want to make use of sogo i >> wouldn't want to go through thousands of documentations, just to have >> a good and working installation. > >-- >[email protected] >https://inverse.ca/sogo/lists -- Alain Abbas Directeur 03 83 18 02 70 -- [email protected] https://inverse.ca/sogo/lists
