1 Notes on T_IMPS harness 07-Aug-1998

     2 -----------------------

     3 

     4 This harness drives the IMPS.DLL component through connecting to an IMAP

     5 server, performing various synchronising and fetching tasks, and then

     6 disconnection. After disconnection, the local folder structure is dumped

     7 to the file:

     8 

     9 c:\system\messages\zac.txt

    10 

    11 ...which can be used to check the server database has been formed correctly.

    12 

    13 When run, you get offered a selection of IMAP servers to connect to: if you

    14 have no existing server in your database, pick one of these to create a new

    15 service entry and run against this.

    16 

    17 If you have created a service entry in a previous session, and wish to run

    18 against this existing service entry (with its associated data - messages,

    19 folder structure, etc) then key '0', which searches the root of the database

    20 for the first IMAP service, then uses this for the connection. This allows

    21 synchronisation to be tested -

    22 

    23  - Blank database

    24  - Create new service entry, connect and synchronise trees and inbox

    25  - Disconnect

    26  - Using another client, alter the inbox/folder tree

    27  - Connect again, using option '0'

    28  - Client synchronises changes on the remote server back to the database

    29 

    30 The current operation sequence is this:

    31 

    32  1. Connect to server (checks hierarchy separator if necessary)

    33  2. Perform full sync operation, which conists of

    34     - Select inbox

    35     - Sync inbox

    36     - Sync folder tree

    37     - Check remote folder subscriptions

    38       For each subscribed folder:

    39       - Select folder

    40       - Sync folder

    41  3. Logout

    42  4. Disconnect

    43  5. Create text file showing database structure (zac.txt)