Added Translation Strings.

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index d19be71e8cf69aca79d254cb1d125f2a7ffacfe2..697f75363bff36f53953ed77e49bfb74fd3a4650 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -312,31 +312,36 @@ 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: What is the correct connection string for a Kolab server in GOsa?
 
+A: Try {localhost:143/novalidate-cert}.
 
-Q: How can i store object snapshots on another server?
 
-A: Just add these lines in the main section of your gosa conf
+Q: Sieve is not working from GOsa - there are authentication problems
+   with this service, IMAP/POP is working. What's wrong?
 
-   snapshot_ldap_base  ="dc=server,dc=de"
-   snapshot_user       ="cn=ldapadmin,dc=server,dc=de"
-   snapshot_password   ="password"
-   snapshot_server     ="ldap://server:389"
+A: Verify that the paramater sasl_auto_transition: no is not
+   present in your imap.conf
 
-Q: What is the correct connection string for a Kolab Server in Gosa
 
-A: {localhost:143/novalidate-cert}
+Q: Slapd does not start with kolab2.schema included. It claims that the
+   definition of calFBURL is missing. What can I do?
 
-Q: Sieve is not working from GOsa
+A: For Kolab to work correctly you have to include the rfc2739.schema
+   in your slapd.conf. Insert it before the kolab2.schema
 
-A: verify that the paramater sasl_auto_transition: no is not
-   present in your imap.conf
 
-A: For Kolab to work correctly you have to include the rfc2739.schema
-   in your slapd.conf 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 "auto_network_conf" 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.
+
+
+Q: New implementations of OpenLDAP seem to require {sasl} instead of {kerberos}
+   in password hashes. GOsa writes the wrong string. What can I do?
+
+A: You can set "krbsasl" to "true" in your gosa.conf's main section.