index 3702b1cab80a3f4ceee1f85dfe80bc4c55abcc86..16dc268c908cf9142fbc3d0be3644b2cc3a82b26 100644 (file)
--- a/FAQ
+++ b/FAQ
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
+
+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.
+
+
+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.