bernhard: doc/raw-howtos freebusy-troubleshooting.txt,1.3,1.4

[cvs at intevation.de]

Author: bernhard

Update of /kolabrepository/doc/raw-howtos
In directory doto:/tmp/cvs-serv32502

Modified Files:
	freebusy-troubleshooting.txt 
Log Message:
More improvements: 
	Explain the macros.
	Explain what URL to use for the Browser test.


Index: freebusy-troubleshooting.txt
===================================================================
RCS file: /kolabrepository/doc/raw-howtos/freebusy-troubleshooting.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- freebusy-troubleshooting.txt	12 Aug 2005 09:37:31 -0000	1.3
+++ freebusy-troubleshooting.txt	12 Aug 2005 15:50:21 -0000	1.4
@@ -20,16 +20,18 @@
 Settings|Configure Contact... in the part Organizer|Free/busy on the tab
 Retrieve.
 
-Server URL: https://kolabserver.domain/freebusy/%EMAIL%.ifb
-(Note that "%25" will also work instead of "%".)
+Retrieval Server URL: https://kolabserver.domain/freebusy/%EMAIL%.ifb
+	The macro will be expanded by the client with the email address
+	for the person we want to see the fb information for.
+	(Note that "%25" will also work instead of "%".)
+
 Check "Use full email address for retrieval"
 Check "Retrieve other people's free/busy information automatically"
 
 Make sure the right username/password is being used to retrieve the
 free/busy list.  Use the same as for imap.
 
-If you configure kontact with the kolabwizard, the settings should be
-OK.
+If you configure kontact with the kolabwizard, the settings should be OK.
 
 
 Check the server
@@ -43,11 +45,12 @@
 
 Retrieval does not work?
 ------------------------
-Try the retrieval with a regular browser of the operating system:
+Try the retrieval URL from above (macros expaned) 
+with a regular browser of the operating system:
 	KDE -> Konqueror
 	Windows -> IE
 Those browsers will use the same proxy and certificate settings as the clients.
-For Outlook to work, this test must not bring up a https certificate question.
+For Outlook to work, this test must not bring up a certificate trust question.
 
 
 Triggering