some minor fixes for base selects.

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index 6a8a56db9491f708b0a43737ea829e9d78b6cb29..b797424d3bcd2cf7114dc5763a50047c21181fc6 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -89,7 +89,13 @@ A: Yes. Just go to the locale directory and copy the messages.po file somewhere
    You may need to restart apache, depending on your setup. On Debian, be sure
    to have your locale generated (dpkg-reconfigure locales) before.
 
+Q: The online help doesn't exist in my language, can i translate it to my language?
 
+A: Yes. Just go to the doc/guide/user/en directory and copy the lyx-source directory
+   to a new directory in doc/guide/user/<your language>. You have to use the lyx
+   program create the online help in your language. When you have finish just run
+   ./gen_online_help from the gosa root directory to generate the online docs.
+   
 Q: Can I specify some kind of password policies?
 
 A: You can place the keywords "pwminlen" and "pwdiffer" in the main section of your
@@ -306,3 +312,45 @@ Q: How can i active the account expiration code for the gosa interface?
 
 A: Yes. Just set "account_expiration" to "true" in your gosa.conf's main section.
 
+Q: How can i activate the object snapshot functionality?
+
+A: Add these lines in the main section of your gosa.conf
+   enable_snapshot     ="true"
+   snapshot_base       ="ou=snapshots,dc=server,dc=de"
+
+
+Q: How can i store object snapshots on another server?
+
+A: Just add these lines in the main section of your gosa conf
+
+   snapshot_ldap_base  ="dc=server,dc=de"
+   snapshot_user       ="cn=ldapadmin,dc=server,dc=de"
+   snapshot_password   ="password"
+   snapshot_server     ="ldap://server:389"
+
+
+Q: What is the correct connection string for a Kolab server in GOsa?
+
+A: Try {localhost:143/novalidate-cert}.
+
+
+Q: Sieve is not working from GOsa - there are authentication problems
+   with this service, IMAP/POP is working. What's wrong?
+
+A: Verify that the paramater sasl_auto_transition: no is not
+   present in your imap.conf
+
+
+Q: Slapd does not start with kolab2.schema included. It claims that the
+   definition of calFBURL is missing. What can I do?
+
+A: For Kolab to work correctly you have to include the rfc2739.schema
+   in your slapd.conf. Insert it before the kolab2.schema
+
+
+Q: Is there a way to let GOsa automatically fill missing fields in the network
+   configuration?
+
+A: Sure. You can specify the "autoconf" option and provide the contributed
+   script "net-resolver.sh" in your gosa.conf. If this is configured, you're
+   getting an additional button in each network dialog.