X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=FAQ;h=30b4c8e340d10420ae00365c4f35c626d2c6844a;hb=6e46575fcf501cfa83418c94c1cb3646c8df4c56;hp=9b7de7611254a532521480fb03ebecc79da1d9c2;hpb=e0fce5eea2b993efffa1173aea8e89eab78723f4;p=gosa.git

diff --git a/FAQ b/FAQ
index 9b7de7611..30b4c8e34 100644
--- a/FAQ
+++ b/FAQ
@@ -269,12 +269,12 @@ Q: I'd like to have TLS based LDAP connections from within GOsa. Is this possibl
 
 A: Yes, add
 
-   <main ...>
+   <location ...>
    ...
          tls="true"
    ... \>
 
-   to the main section of GOsa. This switch affects all LDAP connections.
+   to the location section of GOsa. This switch affects LDAP connections for a single location only.
    
 
 Q: Cyrus folder get created in the style user.username. I prefer the unix hirachy
@@ -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,17 +328,38 @@ 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
 
-A: verify that the paramater sasl_auto_transition: no is not
+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: I got /etc/ldap/schema/kolab2.schema:
-   line 540: AttributeType not found: "calFBURL"
+
+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 before the kolab2.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.
+
+
+Q: Is there a way to add the personalTitle attribute the the users dn?
+
+A: Just add this line into the location section of your gosa.conf.
+   <location name=...
+	include_personal_title="true"
+   ...>
+