some minor fixes for base selects.

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index 0246791066e23e3967576479f5597569e46b1758..b797424d3bcd2cf7114dc5763a50047c21181fc6 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -312,7 +312,6 @@ 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
@@ -329,11 +328,29 @@ A: Just add these lines in the main section of your gosa conf
    snapshot_password   ="password"
    snapshot_server     ="ldap://server:389"
 
-Q: What is the correct connection string for a Kolab Server in Gosa
 
-A: {localhost:143/novalidate-cert}
+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
+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
+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.