|
|
||||
|
|||||
|
|||||
|
|
|||||
|
|
|
|
||||||||||||||||
|
||||||||||||||||||
 | ||
 |  Specialized System Administration Tasks 4.5 Back to Main Menu What is Server Passthru? Setting Up Passthru for Replication Configuring a Cluster Adding a Server to a Cluster Removing a Server from a Cluster Setting up Failover Setting up Load Balancing Replicating Databases within a Cluster Managing Databases within a Cluster Planning for Partitioned Servers Installing a New Partitioned Server Managing Partitioned Servers Using the Billing System Setting up Billing Integrating User Management in Notes and Windows NT -- When you register or delete a Notes user, you can also update the Windows NT User Manager. Additionally, you can use User Manager menu options to specify that additions, deletions, and name changes be made to the Notes Public Address Book. Administrators can perform the following tasks using either the Notes or Windows NT interface: Making User Management Easier Adding and Deleting Users Logging Notes Events to the Windows NT Event Viewer Implementing the Domino POP3 Server Setting up the POP3 Mail Files How Does Shared Mail Work? This lesson introduces Shared Mail, which gives administrators a choice in messaging technology and the opportunity to save storage space. Router Delivers Shared Mail The content is stored in the Shared Mail database; it is not sent to all intended recipients. In contrast, the header is sent to each recipient.
The Router delivering a Shared Mail message intended for three recipients User Viewing Shared MailWhen a user opens a Shared Mail message, the text and attachments are seamlessly available, just as they are in message-based mail. When the user views the Shared Mail message, the pointer in the user's mail file points to the content in the Shared Mail database: Users viewing Shared Mail Note: The Shared Mail database and the user's mail files must be on the same server.
About the database link file About the Shared Mail database Security features Back to Table of Contents
Maximizing Storage Space For example, locations with high mail traffic among users with mail files on a single mail server and few mobile users will maximize the amount of disk space they have for mail storage. Even with Shared Mail enabled, complete copies of mail messages will be placed in the user's mail file (not the Shared Mail database) if the user: Editing and Saving Shared Mail messages When a user edits and saves a Shared Mail message, the entire message is saved in the user's mail file. The following figure illustrates what happens: User1 edits and saves a message Saving sent messagesSaved mail messages are always stored in the sender's mail file even when Shared Mail is enabled. The reason is that it is the Router's job to split the message into header and content information; in this case, the Router never sees a Saved Mail message. To prevent a copy of the saved message from using additional space, instruct users to send copies to themselves (cc:). Alternatively, you can force saved messages in specific mail files to use the Shared Mail database. See Managing Users' Mail Files later in this module. Encrypting mail Encryption is primarily designed to provide additional security for the mobile user. Encrypted mail can only be read by the person whose user ID stores the correct public or private key capable of decrypting the message. If a user encrypts: Creating a local mail file replica When a user creates a local replica of a server-based mail file on a laptop, desktop, or another server, the replica contains complete copies of each mail message. The Shared Mail database is not used. Alternatively, you can force server replicas of mail files to use the Shared Mail database. See Managing Users' Mail Files later in this module. Back to Table of Contents
Shared_Mail=0 is the default setting. It is the messaged-based mail option available in all releases of Notes and does not enable Shared Mail. The two functional types of Shared Mail are: When Shared_Mail=1 Shared_Mail=1 and User 1 is the only recipient on that server 1. The complete message is written to the first recipient's mail file. 2. The Router identifies a second recipient. 3. The message content is written to the Shared Mail database. 4. The entire message is removed from the first recipient's mail file and replaced with a header. 5. The header is written to the other recipients' mail files. When Shared_Mail=2 Shared_Mail=2, and User 1 is the only recipient on that server Shared_Mail=2, and the Router transfers a message from Server 1 to Server 2Back to Table of Contents
Note: When Shared Mail is enabled, actual use of the Shared Mail database is not immediate; momentary background processing takes place. Procedure: Enabling Shared Mail using the server configuration form The server configuration form enables administrators to change the NOTES.INI settings using the Public Address Book interface. The server periodically reads the server configuration documents and updates the NOTES.INI variables. To enable Shared Mail, follow these steps: 1. Choose File - Tools - Server Administration. 2. Select the server from the list of servers to administer. 3. Choose Configure Server from the Server's pop-up menu. 4. Click Add Configuration. 5. Type the server name in the Server Name field. 6. Click Set/Modify Parameters. 7. Click the Item down-arrow, then select SHARED_MAIL from the list and click OK. 8. Type 1 or 2 in the Value text box and click OK. See Choosing a Shared Mail Option to help you decide which value to use. 9. Save and close the form. Note: If both the NOTES.INI file and a Public Address Book Server Configuration document are configured for a variable but contain conflicting values, the setting in the Public Address Book takes precedence. Disabling Shared Mail To keep new mail from being stored in the active Shared Mail database, change the NOTES.INI Shared_Mail setting to 0. Pointers to existing mail are not deleted or disabled, so users will still have access to messages in the Shared Mail database. Back to Table of Contents
Linking Mail Files to the Shared Mail Database The linking process LINK sets up existing mail files to use the Shared Mail database. To link a user's mail file, use the following command: LOAD OBJECT LINK USERX.NSF Shared_mail_database If you use a directory name for the first argument of this command, the Object Store Manager will link all of the mail files contained in that directory. For more information on LINK and its options, see "Ways to manage mail files that use shared mail" in the Administration Help database. The following figure shows the contents of three mail files in the MKTG directory before and after the linking process: Command entered: LOAD OBJECT LINK MKTG MAILOBJ1.NSF Relinking RELINK is a LINK command option. The LINK command links only those messages in a mail file which were never previously linked to a Shared Mail database. In contrast, RELINK links all messages, including those previously linked, to the specified Shared Mail database. To relink a user's mail file, use the following command: LOAD OBJECT LINK -RELINK USERX.NSF Shared_mail_database Unlinking UNLINK pulls messages out of the Shared Mail database and places them into users' mail files. This command should be used when you want to stop a mail file from using the Shared Mail database. For example, you could use it before you moved a user's mail file from one server to another. To unlink a user's mail file, use the following command: LOAD OBJECT UNLINK USERX.NSF Procedure: Moving mail files between servers To move a user's mail file from one server to another, follow these steps: 1. Unlink the user's mail file on the current mail server. 2. Use File - Replication - New Replica to make a replica of the mail file on the new server. 3. Change the person document to reflect the new mail server. 4. Relink the user's mail file to a Shared Mail database on the new mail server. Note: Unlinking the user's mail file is not necessary if you frequently run COLLECT on the server's Shared Mail databases. For more information on COLLECT, see Managing Shared Mail later in this module. Caution: Using File - Database - Copy is not recommended, since the database would then have a new replica ID. However, you can use the operating system to copy the mail file to the new server if you first unlink the user's mail file on the current mail server. Back to Table of Contents
Stage 1: User1 deletes the pointer to the mail message Stage 2: All users delete the pointer to the mail message, but the message content remains in the Shared Mail database Maintaining the Shared Mail databaseOver time the Shared Mail database may fill up with content documents for which there are no pointers and content documents to which users still require access. To maintain database efficiency, administrators must periodically: Deleting disconnected messages To remove "deleted" or disconnected messages from the Shared Mail database, use the following COLLECT command: LOAD OBJECT COLLECT shared_mail_database
Stage 3: All users delete the pointer to the shared message and COLLECT has been run on the Shared Mail database By default COLLECT runs at 2:00 AM. To change the daily server task schedule, change the ServerTasksAt2 parameter in the NOTES.INI file, or create a Server Program document to schedule COLLECT.To purge messages from a shared mail database after deleting a user's mail file, enter the following command: LOAD OBJECT COLLECT -FORCE shared_mail_database When you use the -FORCE option, if a mail file cannot be located or successfully opened for any reason, the Object Collect task behaves as if all messages in the mail file have been deleted. This will delete a content document that is referenced only by the inaccessible mail file and no other mail files because its header part has been deleted from all other mail files. COLLECT can also be used to remove remnant message headers from a user's mail file; for example: LOAD OBJECT COLLECT USERX.NSF Procedure: Backing up and restoring the Shared Mail database Back up the Shared Mail database at least once a day. It is best to use a utility that can back up open files, so the server doesn't need to be shut down when the backup takes place. To restore a backup, follow these steps: 1. Move the latest backup to a separate directory on the server that is not part of the server's directory structure. 2. Use the PUSH command to push changes from the backup to the damaged Shared Mail database. For example: PUSH SERVER1/DChem H:\BACKUP\SHARED1.NSF where SHARED1.NSF is the backup Shared Mail database. 3. Run COLLECT on the Shared Mail database and on users’ mail files to remove any disconnected or damaged messages. Creating a new active Shared Mail database The active Shared Mail database should be replaced periodically to maintain efficiency or when the active Shared Mail database requires maintenance. The old Shared Mail database continues to be used by existing Shared Mail messages. To create a new Shared Mail database, use one of the following server console commands: The TELL ROUTER USE command performs several functions. It will: 1. Enable Shared Mail if it is currently disabled. 2. Create a Shared Mail database with the specified name. 3. Make the newly created database the active Shared Mail database by placing the new database name and path in the database link file MAILOBJ.NSF. The LOAD OBJECT CREATE command performs only one function. It will: 1. Create a Shared Mail database with the specified name. Note: This command does not make the newly created database the active Shared Mail database, nor will this command enable Shared Mail if it is currently disabled. Back to Table of Contents
Managing User's Mail Files
Using a Passthru Server to Access Multiple Servers Introduction Advantages of Passthru Limits Dialup connections The next few lessons describe how to set up a remote user in each scenario. Back to Table of Contents
Controlling Passthru Access to Servers Passthru access control
Specifying a Default Passthru Server
John Jay attempting to access his mail file remotely Notes will require three Address Book documents to complete this connection:Location document John Jay needs a Location document in his Personal Address Book, specifying BLUE/PT/DChem as his default Passthru server and RED/Mail/DChem as his mail server. The following figure shows this Location document. Personal Address Book; Create - Location Dialup modem Connection documentHe also needs a Dialup Modem Connection document in his Personal Address Book, specifying how to call BLUE/PT/DChem, his default Passthru server. The following figure shows this Connection document. Personal Address Book; Create - Server - Connection Public Address Book; Create - Server - Connection Editing the server documentFinally, the administrator must edit the Passthru Use fields in the Restrictions section of the server documents to allow Passthru access. See Controlling Passthru Access to Servers in this module for a description of the Passthru Use fields. The table describes how the fields would be set up for the scenario described in this document. Note: John Jay does not need to authenticate with BLUE/PT/DChem or GREEN/PT/DChem since he is just being routed through these servers. Additionally, he does not need to be listed in the Access server field in the Restrictions - Server Access section of the server document, as shown in the figure below: Public Address Book; Server - Servers; BLUE/PT/DChem; Restrictions section
Scenario 2: Remote access using a different Passthru server Dialup modem Connection document He will need to create a Dialup Modem Connection document in his Personal Address Book, specifying how to call YELLOW/PT/DChem, the new default Passthru server. This document is similar to the Dialup Modem Connection document shown in Specifying a Default Passthru Server. Passthru Connection document in Personal Address Book He will need to create a Passthru Connection document in his Personal Address Book specifying the path from his laptop to RED/Mail/DChem (his mail server) using YELLOW/PT/DChem (the Passthru server). The following figure shows this Passthru Connection document. Personal Address Book; Create - Server - Connection Note: As an alternative to creating a Passthru Connection document in his Personal Address Book, John Jay could create a Location document similar to the document shown in Specifying a Default Passthru Server and specify YELLOW/PT/DChem as the Passthru Server. He would need to switch to this location before attempting to access his mail file. Passthru Connection document in Public Address Book Next, the administrator will have to create a Passthru Connection document in the Public Address Book, specifying the path from YELLOW/PT/DChem to RED/Mail/DChem using GREEN/PT/DChem as the Passthru server. This Passthru Connection document is similar to the document shown in Specifying a Default Passthru Server. Editing the server document Finally, the administrator must edit the Passthru Use fields in the Restrictions section of the server documents to allow Passthru access. See Controlling Passthru Access to Servers in this module for a description of the Passthru Use fields. The table describes how the fields would be set up for the scenario described in this document. Back to Table of Contents
Procedure: Creating the user's Passthru Connection document To create a Passthru Connection document in the user's Personal Address Book, follow these steps:
Procedure: Creating the user's Location document To create a Location document in the user's Personal Address Book, follow these steps:
Procedure: Creating the user's Dialup Modem Connection document To create a Dialup Modem Connection document in the user's Personal Address Book, follow these steps:
Back to Table of Contents Dialing into a Group of Passthru Servers You can allow users to dial in to a hunt group of Passthru servers and pass through to any member of the hunt group. Your telecommunications infrastructure must support hunt groups. Each Passthru server in a hunt group should be able to access the same destination servers. This connection allows Notes workstations to dial in to a hunt group of Passthru servers. This allows incoming calls to be routed to one of a group of available Passthru servers, thus spreading the load among the Passthru servers. Procedure: Setting up a workstation to connect using a hunt group To set up a workstation to connect to a group of Passthru servers using a hunt group, follow these steps: 1. Create a Connection document of the type Hunt Group in the user's Personal Address Book to provide the name and phone number of the hunt group. This figure is shown below: Personal Address Book; Server - Connections; Add Connection 2. Create a Passthru Connection document for each destination server to which you connect through the hunt group. Specify the name of the hunt group in the "Passthru server name or hunt group name" field and the name of the destination server. To specify multiple destination servers for one connection document, use wildcards, such as */DChem. Note: As an alternative to creating a Passthru Connection document in the Personal Address Book, the user could create a Location document similar to the document shown in Specifying a Default Passthru Server and specify the hunt group name as the Passthru Server. The user would need to switch to this location before attempting to access the group of Passthru servers. For more information on using Hunt Groups with Passthru servers, see "Hunt groups" in the Administration Help database. Back to Table of Contents Setting up a User for Remote LAN Server Remote LAN service allows Notes to take advantage of third-party products, such as Microsoft's Remote Access Service (RAS), so that remote users can dial directly into the LAN. In Release 4.5, Notes supports Microsoft's Remote Access Service (RAS) and AppleTalk Remote Access (ARA). Future Notes releases may support other remote access products. In order to use Remote LAN Service, the client's machine must have RAS or ARA installed and another machine on the LAN must be running as a RAS or ARA server. Most Remote LAN Service functions are performed by calling the RAS or ARA modules. The Notes contribution is to: 1. Control RAS or ARA operation. 2. Store the connection information in an Address Book connection document. This ensures that the connection can be made automatically rather than requiring the user to manually dial in and hang up. Procedure: Setting up a workstation to use a Remote LAN Service Once the RAS or ARA software is in place and tested, the administrator needs to create a Connection document of the type Remote LAN Service. To create this document, follow these steps:
Personal Address Book; Server - Connections; Add ConnectionFor more information on Remote LAN Service, see "About connecting to a remote LAN service" in the Administration Help database. Back to Table of Contents What is Server Passthru? Server Passthru is the process of using an intermediary server as a stepping stone from one server to a destination server to which the original server does not have direct access. You will remember that in order to replicate databases on servers that run different protocols, you must first replicate the database to an intermediary server that shares both protocols. We can't replicate databases stored on servers running different protocols by a direct connection. We could use Server Passthru to accomplish this replication. Server Passthru allows a server to use an intermediary server in order to replicate with servers elsewhere on the LAN, if they do not share a common protocol. Back to Table of Contents
Creating a Passthru Server Connection document When Notes attempts to make the connection from Server A to Server D based on the replication schedule specified in a connection document, it will use this same connection document to determine the route. First you must set up the connection from Server A to Server D using Server C as the Passthru server. This connection document also includes the enabled scheduled replication information. The following figure shows this document: Public Address Book; Server - Connections; Add Connection; Connection Type: Passthru ServerNotes will look for another Passthru Connection document to determine the route to Server C, therefore you need a second Passthru Server Connection document from Server A to Server C using Server B as the Passthru server. This connection document does not need to include scheduled replication information. The following figure shows this Passthru Connection document. Note that the Schedule is disabled. Public Address Book; Server - Connections; Add Connection; Connection Type: Passthru ServerEditing the Server documents Finally, in order to use a server as a Passthru Server, you must specify this use in the Server documents for each server. The four relevant fields are in the Passthru Use section. These fields are described in the Controlling Passthru Access to Servers lesson in this Learning Byte. The table describes how the fields would be set up for the scenario described in this document. Back to Table of Contents
Cluster Administration
Note: You must have at least Author access with the ServerModifier role in the Public Address Book and at least Author access in the Administration Requests database to perform this procedure. 1. Open the Public Address Book and navigate to Server - Servers. What happens next 1. The Administration Process modifies the server document on the designated Administration Server for the Public Address Book and fills in the server name and the Replica ID of the Cluster Database Directory used in this cluster.
Setting Up Failover Procedure: Setting up failover Procedure: Enable failover for mail files User failover is automatically enabled with CLUSTER.NCF on the client. Note: This NOTES.INI file setting must be configured on every server in the domain through which mail routes, not just cluster servers.
Setting Up Load Balancing After the cluster is configured and has been used for a period of time, you may want to analyze cluster performance. For more information on Cluster Analysis, see "Setting up a Cluster Analysis" and its related topics in the Administration Help database. Back to Table of Contents Replicating Databases with a Cluster The Cluster Replicator server task (CLREPL) keeps the databases that are stored on cluster servers synchronized. You do not need to schedule replication between servers in a cluster. When a change occurs in a database, the Cluster Replicator pushes the change to replicas on other servers in the cluster. It uses the Cluster Database Directory (CLDBDIR.NSF) to determine which other servers in the cluster store replicas of the changed database. To replicate a cluster server with a server that is not a member of the cluster, schedule replication using a connection document in the usual way for the Replicator (REPLICA) to exchange data. Forcing replication of databases within a cluster To force replication from the server console, type one of the following commands: REPLICATE <clustername> REPLICATE <clustername> <local filename> REPLICATE <clustername> <local directory> Procedure: Disabling cluster replication for a database To disable cluster replication for a particular database, follow these steps: 1. Open the Cluster Database Directory (CLDBDIR.NSF) and navigate to Databases by Server. 2. Open the database document for which you want disable replication. 3. Choose Actions - Edit Document. 4. Select Disabled in the Cluster Replication field. 5. Save and close the document. Procedure: Enabling multiple cluster replicators To enable multiple cluster replicators (CLREPL), use one of the following methods: Back to Table of Contents Managing Databases with a Cluster Cluster Database Directory The Cluster Database Directory (CLDBDIR.NSF) is a database that resides on each server in a cluster and contains information about all the databases within a cluster. Each server in the cluster stores a replica of the Cluster Database Directory. The Cluster Replicator keeps replicas of this database in tight synchronization. The following figure is an example of a document in the Cluster Database Directory. Cluster Database Directory documentMoving a database from a cluster server Use the Database Tools dialog box to move a database from one cluster server to another. The destination server does not have to be a member of a cluster. The Administration process creates a replica on the destination server, then marks the database for deletion on the source server. The following figure shows the Move a database tool: File - Tools - Server Administration; Database Tools; Move a databaseTo use this feature, you must ensure the following access: For more information on the details of how the Administration Process moves a database, see "Details: Moving databases from a cluster server" in the Administration Help database. Cluster management Use the Database Tools dialog box to perform additional cluster management. The following figure shows the Cluster Management Tool: File - Tools - Server Administration; Database Tools; Cluster Management The table describes the options available with this tool. When you select one of these options, the availability of the database in the Cluster Database Directory gets updated. For more information about clusters see "About Notes server clusters" and its related topics in the Administration Help database. Back to Table of Contents Each partitioned server can also be a member of a cluster if you require high availability of Notes databases. Carefully plan your naming scheme. Any administrator should be able to immediately distinguish one partitioned server from another. Avoid changing a server name after you install. Procedure: Planning for partitioned servers Consider the following questions when planning to use partitioned servers. 1. How do partitioned servers fit into your current Domino environment? 2. How many partitioned servers should you install? 3. What network protocols should you use for the servers? 4. If you choose the TCP/IP network protocol, should you use unique IP addresses for each server or should they share the same network interface card and IP address? 5. What should you name each partitioned server? 6. How do you determine the data directory name for each partitioned server's data files? For more information on these considerations, see "Planning a partitioned server configuration" and its related topics in the Administration Help database. Back to Table of Contents Installing a New Partitioned Server This document provides an overview of the process of installing an additional partitioned server, including the tasks necessary to install and the order in which they should be performed. Complete details are available in the Administration Help database and the Lotus Domino Install Guide for Servers. Partitioned servers use different Notes data directories and NOTES.INI files. When you install partitioned servers, install a separate data directory for each server. The first time you install a partitioned server, name both the program directory, which by default is NOTES, and the data directory. During subsequent installs, name the data directory only. Procedure: Installing an additional partitioned server To install a second and subsequent Domino partitioned servers on a Windows NT computer, follow these steps: 1. Install and set up the first partitioned server. Be sure to select the Advanced Services tab to install Advanced Services and Advanced Services data. 2. Run the Lotus Domino 4.5 Powered by Notes Installation Program. 3. At the Install Options screen, select "Customize features - Manual install" to install the additional Domino partitioned server and click OK. 4. Enter the drive and directory where you want this server's Domino data files to reside and click Next. We recommend that you use the name of the new partitioned server to name its data directory. Note: When installing additional Domino partitioned servers, the program directory field does not appear because all Domino partitioned servers share the same program files. 5. By default, both the Domino and Advanced Services tabs have the appropriate features selected for an additional Domino partitioned server install. Do not select or deselect any of the features. You must install the default features selected. Note: You do not need to select the "Advanced Services" option for an additional partitioned server install. 6. Continue with the installation as usual. 7. Click Done when installation is complete. 8. Repeat this procedure for each additional Domino partitioned server you want to install. After you install your Domino partitioned servers, set up the servers in the usual way. If you are installing the first server in an organization or domain, see "Setting up Domino on the first server" in the Domino Install Guide for Servers. For information on setting up additional servers, see "Setting up Notes on an additional server" in the Administration Help database. For more information about setting up the a partitioned server using the TCP/IP protocol, see "Ways to configure partitioned servers for TCP/IP" in the Administration Help database. Back to Table of Contents Managing Partitioned Servers Failures and shutdowns Setting Up Billing For more information on the Billing database, see "Viewing the Billing database" and its related topics in the Administration Help database. Making User Management Easier To use these features, you must have a properly certified Notes ID, appropriate access to make any changes to the Public Address Book, and be a member of the local Administrator Group or Account Operator Group in Windows NT. Back to Table of Contents Adding and Deleting Users Adding Users During user registration, administrators can add an NT user account and specify the NT Group Name as shown in the following figure: File - Tools - Server Administration; People; Register PersonAdditionally, administrators can specify an NT user name as shown in the following figure: File - Tools - Server Administration; People; Register Person; Continue For more information on registering Notes users from within Windows NT, see "Ways to register Notes users with Windows NT User Manager" in the Administration Help database. Enable Single Password Logon The NT account password will be set to the first 14 characters of the Notes password supplied during user registration. Note that changing a Notes password does not affect the Windows NT password. This option is only available on clients running a minimum of Notes Release 4.5 for Windows NT. Deleting Users In the Public Address Book, administrators can use the Delete Person action button to delete the selected person's NT user account. When the Administrator deletes a person on a server that is running Windows NT, the administrator will be asked whether to delete the person's Windows NT network account. This prompt appears regardless of whether or not a Windows NT account for the user exists in User Manager. The Administration Process must be set up in order to use this action button. Note that deleting the person document does not delete the NT user account; you must use the Delete Person action button. For more information on deleting Notes users, see "About how the Administration Process deletes a user name" in the Administration Help database. Back to Table of Contents Logging Notes Events to Windows NT Event Viewer Procedure: Log Notes Events to the NT Event Viewer To log Notes Events to the Windows NT Event viewer, follow these steps: 1. Open the Statistics and Events database (EVENTS4.NSF). 2. Choose Create - Monitors - Event Monitor. 3. Select Event Notification Enabled in the Enabled/Disabled field. 4. Select Server in the Event type field. 5. Select Log to NT Event Viewer in the Notification method field. 6. Enter the server name(s) to monitor or * for all servers. 7. Select an Event severity. 8. Save and close the document. Events are logged to the Application View of the NT Event Viewer by level of severity according to the table. Back to Table of Contents Implementing the Domino POP3 Server Domino POP3 Server Requirements The Domino POP3 server task allows Domino servers to be host servers for POP3 clients. Some popular POP3 clients are: The Domino POP3 server task only enables retrieval of mail files from the Domino server. To allow the POP3 client to send mail, a SMTP server or the Domino SMTP MTA must be installed and enabled. Hardware and Software Requirements for the POP3 server To properly run the Domino POP3 server task, the following is required: Back to Table of Contents
Configuring the Domino POP3 Server Task Step 1: Creating a Domino Mail File for each POP3 Client 1. Choose File > Database > New. 2. In the server field, select a Domino server which is running the POP3 server task. 3. In the title field, enter the title of the client's mail file. Example - Daffy Duck's Mail 4. In the file name field, enter a path name and the file name for the mail file. If the user has a separate Domino mail file, make sure they are separate. 5. Select the template Mail (R4.5) 6. Click OK Step 2: Creating a Person Document for a POP3 Client 1. Open the Public Address Book 2. Choose Create > Person 3. Complete the Name section 4. Complete the Mail section 5. In the Encrypt incoming mail field in the Misc. section, select NO. Step 3: Starting the POP3 Server
| |
 |
|||||
|
