joako wrote:I think here is one good example. HP OpenMail manual has 20 pages about the message store, it's structure, the item structure server, single user restore, etc. Many of these concepts are not explored in the Scalix manual. 832 pages vs 265 pages.
ALL THE SCALIX MANUAL SAYS ABOUT THE MESSAGE STORE IS "The message store is the mail database". In contrast, HP OpenMail docs have 20 pages about the message store. I think this qualifies for saying "Scalix documentation is piss-poor."
Lets see.....
Item Structure Server. Show me one person who uses that? I looked at that years ago. Its an ancient way of rolling forward/back mail transactions. Nobody uses it as it is too complex to understand. When i looked at it years ago there might have been 1 or 2 guys at Scalix who could understand it. it is always turned off by default. People use tar/rsync/sxmboxexp for backups these days.
Single user restore....that's how it used to be done via the Item Structure Server. Nobody uses that. sxmboxexp and sxmboximp are the tools now. Oh and they are in the Scalix Adminsitration manual starting on page 99 with the section about backups.
And lets see, your screenshot....ok, what commands are listed on the openmail side that don't appear under scalix....
omdisksprd - obsolete.
omrestore - obsolete.
omsnoop - obsolete.
omstore - obsolete.
Don't forget there are man pages as well for all commands and omsolve for scalix errors.
Oh, and i thought you were complaining about not having every error documented? Now you've changed tack and started complaining about ancient technology to do with the Item Structure Server which no one uses and its not the officially recommended action to take in terms of backups.
When you buy your $250000 ferrari, and it comes with its owners manual is everything documented in it? Including all errors? Would you expect to be able to fix something broken in the engine, for free, just by reading the manual?