Installing and Configuring OpenMail on an HP OmniBook 5700 Laptop with Red Hat Linux 6.1 --------------------------------------------------------------- Origin: http://www.openmail.com/cyc/om/00/showfile.cgi?100-1546 ¡ http://www.openmail.com/cyc/om/00/showfile.cgi?100-1546 --------------------------------------------------------------- This document provides an overview on how to install and configure OpenMail on a HP OmniBook 5700 CTX Laptop running Red Hat Linux 6.1. The HP Laptop provides a nice demonstration system for customers, resellers and other third party OpenMail providers. Not only can the OpenMail server software be demonstrated, but also popular messaging clients (e.g., the Netscape IMAP or POP client, the OpenMail Web client, the OpenMail Linux GUI) can all be demonstrated from within the same system. This document can also be used as a guide for installing and configuring a production OpenMail system using Red Hat 6.1 on another Intel based system other than a laptop. While it should be considered work in progress, it does provide the necessary steps for getting an OpenMail system operational. It will also provide some tips on configuring the system that may not have been considered during initial install or configuration process.Building an OpenMail Linux Demo System on an HP OmniBook 5700 Laptop Profile: Demo OpenMail Linux System Collect the necessary SOFTWARE & DOCUMENTATION for system installation. This will include: Required software: 1. Red Hat Boot Diskette Release 6.1 2. Red Hat Linux 6.1 Operating System for Intel Computers CD 3. Red Hat Third Party Server Applications CD from the Red Hat Linux Applications Library (Server Edition) 4. OpenMail Media Subscription Service Quarterly Patch CD, February 2000 (EP1) Patch CD Suggested Documentation: 1. Performance and Sizing Information for OpenMail Version 6.0 (B.06.00) for Linux [ID: 200-0307] 2. OpenMail HOWTO - a quickstart configuration guide [ID: 100-1454] 3. OpenMail and Linux [ID: 100-1333] 4. Release Notes - OpenMail B.06.00 on Linux (OMNOTES) [ID: 100-1423] 5. OpenMail Installation Instructions for Linux Systems 6. OpenMail Technical Reference Guide 7. OpenMail Motif Client for Linux Technical Guide For help on Configuring Linux on a laptop go to the "Linux on Laptops" Web Page at: http://www.cs.utexas.edu/users/kharker/linux-laptop Review the notes for the HP OmniBook 5700CTX at: http://www.best.com/~mcrosbie/Linux/Linux.html Review the notes for "Linux on HP OmniBook 5700 CT" at: http://www.physik.tu-berlin.de/~matzed/5700CT.htm Collect the necessary Networking Information for this system. Before you install the Red Hat and OpenMail, fill in the following table. It lists information you will need to input during the installation process. Item: Value:  Physical Memory Installed   Internet System Name (hostname)   Domain Name   IP Address   Subnetwork Mask   Default Gateway hostname   Default Gateway host IP Address   DNS Server Name   DNS Server IP Address   Current LOCAL Date & Time   Root Password   Note: NIS is not required and not recommended for OpenMail systems. Set up the Hardware 1. PCMCIA Ethernet Card to be installed in one of the PCMCIA slots in the HP 5700 2. Hook the Ethernet Card up to the network 3. CDROM Drive & Floppy Diskette Drive both connected and operational on the 5700 Cold Install Red Hat Linux 6.1 WARNING: this cold install procedure will wipe all information on the hard disk drive of the HP 5700 LapTop 1. Insert the "RedHat Boot Diskette Release 6.1" in the diskette drive 2. Turn on the HP 5700 Laptop and boot from the RedHat Boot Diskette 3. Insert the "RedHat Official Linux 6.1 Operating System for Intel Computers CD disk 1" in the CDROM drive 4. Hit "Enter" when the "Welcome to Red Hat Linux 6.1" screen appears 5. Select "English" when "Choose a Language" appears (or other preferred language) 6. Select "Generic 101-key PC" Model, "U.S. English w/ISO9995-3" Layout and "None" for Variant when the Keyboard Configuration screen appears (or other preferred keyboard type), select "Next>" 7. Select the Generic "2 Button Mouse (PS/2)" when the "Mouse Configuration" screen appears, select "Next>" 8. Select "Next>" when the "RedHat Linux System Installer" screen appears 9. Select "Custom" when the "Install Path" screen appears 10. When the "Disk Druid" screen appears, configure the partitions as follows: Mount Point Device Requested Actual Type /boot hda1 24M 27M Linux native <swap> hda5 128M 128M Linux swap / hda6 1M 2779M Linux native Note: the "root" file system (/) was configured to "grow to fill disk". 11. Select "Next>" 12. Select "Next>" when the "Choose Partitions to Format" screen appears 13. Select "Next>" when the "LILO Configuration" screen appears 14. Select a Time Zone and select "Next>" 15. Enter a root password, confirm and select "Next>" 16. Select "Next>" when the "Authentication Configuration" screen appears 17. Select the following packages when the "Package Group Selection" appears: Printer Support X Window System Gnome KDE DOS/Windows Connectivity Graphics Manipulation Games Multimedia Support NetworkedWorkstation Dialup Workstation News Server Anonymous FTP Server Web Server DNS Name Server Network Management Workstation Development Kernel Development Extra Documentation Utilities Note: finally select "Select individual packages" Select "Next>" to continue 18. Select "Next>" when the "Individual Package Selection" appears 19. Select BOTH "Customize X Configuration" & "Use Graphical Login" when the X Configuration screen appears, select "Next>" 20. Select "16 Bits per Pixel, 640X480" when the Customize X Screen appears, select "Next>" 21. Select "Next>" to begin the installation Note: this will take some time to install all the software on the hard disk 22. Remove the "RedHat Boot Diskette" from the diskette drive 23. Place a BLANK floppy diskette in the diskette drive 24. Select "Next>" when the "Bootdisk Creation" screen appears 25. Select "Next>" when the "Congratulations ..." screen appears 26. Remove the diskette from the floppy diskette drive 27. Select "Exit" 28. The system will reboot 29. Remove the Linux OS CD from the CDROM Note: the X-Windows screen will be a little off at this point. The next step will help fix that. Reconfigure Xfree86 1. Login as "root" into Gnome 2. Start a terminal window 3. Edit the /etc/X11/XF86Config File (or copy it from another location) See the attached XF86Config File for the changes involved. 4. Save the XF86Config file and reboot the system. Configure the Hostname & Networking Information 1. Login as "root" 2. Start a terminal window 3. Run "linuxconf" 4. Under "Config", "Networking", "Client Tasks", enter "Basic Host Information" Under "host name" enter the Host Name without the domain name (e.g., hp1) Under Adaptor 1, make sure "Enabled" is selected Select "Manual" for Config Mode Primary Name + domain (e.g. hp1.domain.hp.com) Aliases (opt) (e.g., hp1alias) IP Address Netmask (opt) Net device (e.g., eth0) 5. Accept the changes, select "Act/Changes" 6. Select "Quit" & reboot the system manually Change the Kernel Parameters The kernel parameters to modify are outlined and can be calculated from the Linux "OMNOTES" documentation that is supplied on the OpenMail web site (http://www.hp.com/go/openmail). For the HP 5700 Laptop, this step is optional. It is provided here for completeness and in the event these notes are being used for another type of production OpenMail system, this step will be required. Modify the following kernel parameters: V6.0 Kernel Parameter Default Modification  NR_TASKS 2048 NA  File_max NA NA  Inode_max NA NA  Save the kernel modifications, recompile the kernel and reboot the system Installing & Configuring OpenMail v6.0 & SendMail 8.9.3 on a HP OmniBook 5700 CTX Laptop Profile: Demo OpenMail Linux System Configuring SendMail SendMail configuration will be very specific to a customer's implementation. OpenMail installs the necessary OpenMail rulesets and mailers into the "sendmail.cf" configuration file. However, it does not set up specific routing, aliases and hostname information that may be required for proper operation. The following files are configuration files that can be modified for SendMail: · /etc/sendmail.cf · /etc/sendmail.cw · /etc/aliases Customize these files for your OpenMail Linux Demo environment. With the version of SendMail that is installed with Red Hat 6.1 (v8.9.3), a mailertable can be created such that all mail from a specific domain can be routed into OpenMail automatically. The initial file "/etc/mailertable" is a zero (0) length file when installed. To restart SendMail: /etc/rc.d/init.d/sendmail stop /etc/rc.d/init.d/sendmail start Install the OpenMail v6.0 server & the OpenMail GUI Client software 1. Login as "root" 2. Start a terminal window 3. Insert the "Red Hat Third Party Server Applications" CD Note: the CD should mount automatically on /mnt/cdrom 4. The OpenMail Software is located under "/mnt/cdrom/HP" 5. Install the OpenMail server software by running: rpm -i /mnt/cdrom/HP/openmail-core-eval-6.0-1.i386.rpm 6. Proceed with the OpenMail Server Software "Core" installation 7. Install the desired OpenMail Languages (American English in this case): rpm -i /mnt/cdrom/HP/openmail-lang-American-6.0-1.i386.rpm 8. Proceed with the OpenMail language installation 9. Install the OpenMail GUI client software rpm -i /mnt/cdrom/HP/openmail-gui-6.0-1.i386.rpm 10. Proceed with the OpenMail GUI installation 11. Run "ominstall": /opt/openmail/B.06.00.00/bin/ominstall Note: you should check the /tmp/ominstall.log for errors when complete 12. unmount and remove the CD, type "umount /mnt/cdrom" Install the Latest OpenMail Patch (EP1, February 2000 Patch) 1. Login as "root" 2. Insert the " OpenMail Media Subscription Service Quarterly Patch CD, February 2000 (EP1)" CD Note: the CD should mount automatically on /mnt/cdrom 3. The OpenMail server software is located under "/mnt/cdrom/SERVER/6.0/LINUX" 4. Remove the current OpenMail language installation (American English in this case): rpm -e openmail-lang-American-6.0-1 5. Remove the current OpenMail core software rpm -e openmail-core-6.0-1 6. Install the OpenMail February 2000 EP1 Patch software by running: rpm -i /mnt/cdrom/SERVER/6.0/LINUX/openmail-core-6.0.5-7.i386.rpm 7. Install the desired OpenMail Languages (American English in this case): rpm -i /mnt/cdrom/SERVER/6.0/LINUX/openmail-lang-American-6.0.5-7.i386.rpm Note: there is a bug in the OpenMail EP1 (February 2000) patch for the PAW Web Client profile. The workaround is to: · cd /var/opt/openmail/omhtml/PAW-AMERICAN: mv diratt.search.std diratt.search mv profile.std profile · cd /var/opt/openmail/omhtml/PAW-AMERICAN/pers: mv PINSTRIPE.std PINSTRIPE mv default.std default · cd /var/opt/openmail/omhtml/PAW-C: mv diratt.search.std diratt.search mv profile.std profile · cd /var/opt/openmail/omhtml/PAW-C/pers: mv PINSTRIPE.std PINSTRIPE mv default.std default Note: if you have other languages installed, this will need to be done for those as well. This will be fixed in the next (EP2, May 2000) OpenMail patch release. OpenMail Configuration Note: make sure that the OpenMail binaries are accessible via your "PATH" environment variable (export PATH=$PATH:/opt/openmail/bin) Start OpenMail for the 1st Time: omrc omon -s all execute "omstat -a & omstat -s" to verify OpenMail is operational. Note: you may see the "Application Link Server" as "Aborted" when finished with this process. That's ok, ignore this message for now. Add the 1st (primary) MailNode: omaddmn -m <primary mailnode name> Note: in lieu of a creative name to use for a mailnode name, you can use the system name for the primary mailnode. Create a "Pool" of OpenMail Unix ID's for use by OpenMail: omadmidp -a -s 1001 -n 11000 Check the creation of the pool "omadmidp -u -q" Create the "FREEBUSY" directory: omaddfb Check the creation of the directory by running "omlistdirs -L" Add the Error Notification User (ENU) Account: omaddu -n "Error Manager/<primary mailnode name>" -c admin -l C -p error -F Configure the Error Notification User (ENU) Account: omconfenu -n "Error Manager/<primary mailnode name>" Add an OpenMail administration user account: omaddu -n "Admin Manager/<primary mailnode name>" -c admin -l C -p error -F Configure the OpenMail CDA server: omaddcda -d system -r 60 Force the first build of the Directory Access Tables for the SYSTEM directory: omexeccda Check the logging levels for Event Logging: omshowlvl Service Level  Local Delivery 7  Internet Mail Gateway 7  Sendmail Interface 7  Test Server 7  Administration  7  Converters 7  Browser 7  Request Server 7  Print Server 7  Directory Synchronization 7  Bulletin Board Server 7  Directory Relay Server 7  Background Search Service 7  Archive Server 7  CDA Server 7  Modify the logging levels for Audit Logging: omconfaud router 11 local 11 unix 11 lci 11 rci 11 admin 11 dirsync 11 bbs 11 Check the logging levels for Event Logging: omshowaud Service Level  Service Router 11  Local Delivery 11  Internet Mail Gateway 11  Local Client Interface 11  Remote Client Interface 11  Administration 11  Request Server 0  Directory Synchronization 11  Bulletin Board Server 11  Background Search Service 0  Configure the Unix gateway: omconfux -m internet -s <primary mailnode>,sh -u <primary mailnode>,uu Check the OpenMail Routes: omshowrt -q all LOCAL <primary mailnode> UNIX internet MIME UNIX <primary mailnode>,sh SHAR UNIX <primary mailnode>,uu UUENCODE Setup & Configure POP3: Edit /etc/inetd.conf and add the following lines: # OpenMail POP3 Service pop-3 stream tcp nowait root /opt/openmail/bin/in.pop3d in.pop3d Note: the following line should already be in /etc/services pop-3 110/tcp # POP Version 3 Restart inetd: /etc/rc.d/init.d/inet stop /etc/rc.d/init.d/inet start Setup & Configure IMAP4: The OpenMail IMAP4 daemon is automatically started as one of the OpenMail "services". Therefore, it is already configured. To view the status, type: omstat -a Note: the following line should already be in /etc/services imap2 143/tcp imap # Interim Mail Access Proto V2 Setup & Configure LDAP: Edit /var/opt/openmail/sys/dit.cfg and make the following entry "blank": DIT_DIRECTORY= Edit /var/opt/openmail/sys/slapd.conf and make sure these are the only lines in the file: database om suffix "" flatSuffix "ou=<primary mailnode>" directory SYSTEM sizelimit 100 timelimit 15 useDit false Restart the OpenMail LDAP daemon (slapd): omoff -d 0 -a slapd omon -a slapd Edit the general.cfg file: BRW_NAME_MAPPING=TRUEUAL_POP3_HOSTNAME=<primary mailnode> UAL_SIGNON_ALIAS=YESUAL_SIGNON_ALIAS_CONFIG=SYSUAL_USE_SIGNON_ALIAS=FALSEUXI_NAME_MAPPING=TRUEUXO_NAME_MAPPING=TRUECDA_CHECKTIME=60CDA_USE_CHANGE_LOG=TRUEUAL_SIZE_ERR_TO_USER UAL_SIZE_MSG_TO_ENU UAL_SIZE_MSG_TO_USER SE_DEFAULT_DELAY=86400 IMAP_CONNECTION_LIMIT=500 IMAP_CONNRATE_LIMIT=3 IMAP_IDLE_TIMEOUT=31 IM_MAKE_MSG_ID_GLOBAL_UNIQUE=FALSE UAL_SINGLE_TEMP_DIR=/var/opt/openmail/temp Set up the Licenses for the Server: Obtain the "Password Certificate" from the appropriate source (check http://www.hp.com/go/openmail for more detail). Edit the "/var/opt/ifor/nodelock" file Enter the "passwords" for: 1. B2016BZ (OpenMail Mailbox License) 2. B2020BZ (OpenMail HP Client License) 3. B2269BZ (OpenMail Japanese GUI Driver License) 4. B2274BZ (OpenMail cc:Mail R6 Driver License) 5. B2275BZ (OpenMail Outlook Driver License) 6. B2264BZ (OpenMail HP Mobile Client License) Note: this sets up the "nodelock" file for licensing. Once complete, verify license installation by running "omshowlic -v". Note: for Linux the directory "/var/opt/ifor" may not exist and may need to be created. Run "omdisksprd" (optional): omshut omdisksprd 0 /var/opt/openmail/data1 1 /var/opt/openmail/data2 1 /var/opt/openmail/data3 1 /var/opt/openmail/data4 1 /var/opt/openmail/data5 1 /var/opt/openmail/data6 1 Note: for this demo system, this step can be skipped. Set up Password Controls (optional): Password controls are flexible and as such can be set up in any manner that fits the business need. For each OpenMail toaster, this is what is recommended: Expiration 180 days  Minimum Length 5 characters  Options must contain at least one alphanumeric and one numeric character  Illegal Tries 5  omconfpwd -e 180 -l 5 -c an -k 5 Check the controls by running: omshowpwd Note: for this demo system, this step can be skipped. Message Store Limits (optional): Set the Message Store Limits for the Demo System. This system has about 1.5gb of usable message store space. With 10 users, this equates to 150mb per user. So, for each user it is recommended that you allow for 50mb of In-Tray space and 100mb of File Cabinet space. Run the following command: omlimit -g -i 50 -f 100 Note: for this demo system, this step can be skipped. Configure v6.0 PQA "auxiliary" processes (optional): First, shutdown the processes that will need to be updated: "omoff -d 0 -s rtr local sendmail unix" Now run: omsetsvc -x router 20 omsetsvc -x local 20 omsetsvc -x sendmail 20 omsetsvc -x unix 20 Now, turn the processes back on: "omon -s rtr local sendmail unix" Note: for this demo system, this step can be skipped. Remove the "ISS" process from automatic startup: The Item Structure Server Process is installed and running by default. Change the startup flag on the ISS service by running: omsetsvc -a iss n This will insure the Item Structure Server process is not started by default, but is still available if needed. It will also be viewable by omstat and remain in the "stopped" state while OpenMail is in operation. Remove the "Application Link Server" process from automatic startup: The Application Link Server Process is installed and running by default. Although, at first start, it may be in an "aborted" state. Check the status by running: omstat -s. Change the startup flag on the Application Link Server service by running: omsetsvc -a "Application Link Server" n This will insure the Application Link Server process is not started by default, but is still available if needed. It will also be viewable by omstat and remain in the "stopped" state while OpenMail is in operation. Restart OpenMail At this point in the configuration process, it's time to restart all processes. Type: "omshut" to shutdown all of OpenMail. Once complete, type: "omrc" to start it all back up again. Setup an Apache Web Server on the Demo box Red Hat Linux 6.1 has an Apache Web server installed as part of the initial install process. It will need to be configured so that the OpenMail Web Clients can access OpenMail. The main directories & files for the Apache Server are: /var/log/httpd /home/httpd /usr/sbin/httpd /var/cache/httpd /var/lock/subsys/httpd /var/run/httpd.pid /etc/rc.d/init.d/httpd /etc/httpd Change directory to "/home/httpd/cgi-bin" (cd /home/httpd/cgi-bin) and add the following links: · ln -s /opt/openmail/bin/ice.cgi ice.cgi · ln -s /opt/openmail/bin/omhtml.cgi omhtml.cgi · ln -s /opt/openmail/bin/select.cgi select.cgi · ln -s /opt/openmail/bin/webselect.cgi webselect.cgi Change directory to "/home/httpd/html" (cd /home/httpd/html) and add the following link: · ln -s /var/opt/openmail/omhtml omhtml Change directory to "/etc/httpd/conf" (cd /etc/httpd/conf) and edit "access.conf" Change this section of the config file to look like this: <Directory /home/httpd/cgi-bin> AllowOverride None Options ExecCGI Indexes Includes FollowSymLinks </Directory> Restart the Web Server: To stop the Apache Web server: /etc/rc.d/init.d/httpd stop To start the Apache Web server: /etc/rc.d/init.d/httpd start To access the different OpenMail Web Client Profiles, point your browser to the following urls: http://<yourdemoservername>/cgi-bin/ice.cgi -> OpenMail v6.0 Web Client http://<yourdemoservername>/cgi-bin/omhtml.cgi -> OpenMail v5.x Web Client http://<yourdemoservername>/cgi-bin/ice.cgi/prof=PAW-C -> OpenMail v6.0 Personal Administration Wizard (PAW) or http://<yourdemoservername>/cgi-bin/webselect.cgi -> to access the web profile selector. Add OpenMail Users & their respective Internet-Addr (attribute 167) information Demo users and accounts must be installed on the system prior to the demo box use. Use the "omaddu" utility to add users to the system. In addition, the internet address associated with this OpenMail account must be added separately. This is the internet address that this person will send/receive mail as. To do this, use the "ommodent" utility to modify a users directory entry. OpenMail Client Configuration and Access The OpenMail Linux Demo box is ready for use. Review any of the client installation documentation from the main OpenMail web site to determine how and which clients you would like to connect to OpenMail. Operations Note: these steps can be skipped for the OpenMail Linux demo box. They are documented here to use as a guideline for other "non-demo" systems. This next section is to be used as a guide to help with "day-to-day" operations. No one organization has a "standard" way of operating their messaging environment. This is to be used as a guide to help determine the processes and functions to execute the tasks necessary to keep OpenMail in good working order. It is a guide only and may not be all-inclusive. Day-to-Day Operations: Some of the tasks necessary to monitor the health of the OpenMail system include: 1. Check all services are running 2. Check Error Manager 3. Check Message Movement 4. Check Error Queues (e.g., SMERR) 5. Check for System Messages 6. Disk Usage 7. omscan 8. Directory (omexeccda) Cron Scripts: Some standard scripts that would help would be to: 1. A script to run omtidyallu to clean up the waste can area 2. A script to age the OpenMail & Sendmail logs 3. A script to run omscan 4. A script to do backups automatically (see the "Backups" section) 5. A script to check OpenMail process health 6. A script to check queues 7. A script to check disk space utilization 8. A script to check the error queues 9. A script to modify the SendMail alias file if necessary Backups: This system is designed with disk mirroring. The system can be backed up in one of three ways: 1. online, without shutting down OpenMail 2. offline, shutdown OpenMail 3. online, by splitting mirrors Number three (#3) above is recommended for this system. SendMail Configuration: OpenMail modifies the SendMail configuration file by default to add in the OpenMail mailers. However, it does not make the necessary modifications for SendMail to run in your specific environment. In fact, it is assumed that the network infrastructure and any SendMail configuration necessary is completed before OpenMail is installed. OpenMail uses SendMail as a transport mechanism only and does not check to make sure it is in working order. At a minimum, you will need to add any network routes (using the "route add" command) to add network routes to other mail systems, gateways, DNS servers, NIS servers, Web servers, etc. Also, you can make changes to the "/etc/nsswitch.conf" as needed. Virus Scanning (Optional): Trend Micro's "ScanMail" product for OpenMail can be integrated with the OpenMail system to perform virus scanning. http://www.antivirus.com Message Delivery Rulesets: Create and edit the message delivery ruleset file: "vi /var/opt/openmail/rules/off-peak" and enter the following rule filters into the file: # low priority messages will not be delivered between 9am-11am # and 1pm-3pm Monday thru Friday PRIORITY=LOW ACTION=DEFER DAY=1-5 TIME=09:00-11:00 PRIORITY=LOW ACTION=DEFER DAY=1-5 TIME=13:00-15:00 # messages with more than 1000 BCC recipients will not be # delivered between 9am and 5pm Monday thru Friday BCC-COUNT=1000 ACTION=DEFER DAY=1-5 TIME=09:00-17:00 # messages with more than 2000 recipients will not be # delivered between 9am and 5pm Monday thru Friday DL-COUNT=2000 ACTION=DEFER DAY=1-5 TIME=09:00-17:00 # messages that are larger than 50mb will not # delivered between 9am and 5pm Monday thru Friday SIZE=50000 ACTION=DEFER DAY=1-5 TIME=09:00-17:00 Change the ownership of the file: "chown openmail:hpoffice /var/opt/openmail/rules/off-peak" Modify the route(s) to add the message delivery ruleset: "ommodrt -m <primary mailnode> -d off-peak" Note: the other routes should modified as well. Check that the rulesets are in place: "omshowrt -q all -d" Restart the service router: "omoff -d 0 -s rtr" "omon -s rtr" User Configuration: There are a couple of tools in the contributed library that can help set up or delete users in batches. Also, the Admin Manager tool can help with adding/modifying/deleting users. PDL Configuration: One of the tools in the contributed library will set up a Public Distribution List (PDL) for all local users on the box. At a minimum, this script (or one similar) should be installed. Configure Directory Synchronization: If there are other OpenMail or Microsoft Exchange systems in the network, then directory synchronization can be set up using OpenMail's dirsync commands. Request Server Scripts: Request Server scripts can be added for anything. Examples include: 1. A script to add/modify/delete a PDL 2. A script to report on output from an omscan run 3. A script to change a password for a user These are several examples, but anything that would help the user or administration can be developed. Bulletin Board Configuration: Any public or private BB's need to be set up. Third Party Products: There are a number of third party products that can help with Operating your OpenMail system. They include: OpenTime Calendaring: http://www.cst.ca OpenScope InfoDirect: http://www.openscope.com Openview: http://www.hp.com/go/openview Trend Micro ScanMail: http://www.antivirus.com Entrust PKI: http://www.entrust.com Virtual Vault (OpenMail AnyWhere): http://www.hp.com/go/security Spark 2000 OMVI: http://www.spark2000.com Automated Profile Management's Profile Maker: http://www.autoprof.com Check out others on document 100-1156 at http://www.hp.com/go/openmail /etc/X11/XF86Config File # File generated by XConfigurator. # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. FontPath "unix/:-1" EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #NoTrapSignals # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence # This allows clients to receive this key event. #DontZap # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching # sequences. This allows clients to receive these key events. #DontZoom EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Keyboard section # ********************************************************************** Section "Keyboard" Protocol "Standard" # when using XQUEUE, comment out the above line, and uncomment the # following line #Protocol "Xqueue" AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be # required when using pre-R6 clients #ServerNumLock # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) #Xleds 1 2 3 #To set the LeftAlt to Meta, RightAlt key to ModeShift, #RightCtl key to Compose, and ScrollLock key to ModeLock: # LeftAlt Meta # RightAlt Meta # ScrollLock Compose # RightCtl Control # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel "pc102" # If you have a US Microsoft Natural keyboard, you can use: # XkbModel "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout "de" # or: # XkbLayout "de" # XkbVariant "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions "ctrl:swapcaps" # These are the default XKB settings for XFree86 # XkbRules "xfree86" # XkbModel "pc101" # XkbLayout "us" # XkbVariant "" # XkbOptions "" XkbKeycodes "xfree86" XkbTypes "default" XkbCompat "default" XkbSymbols "us(pc101)" XkbGeometry "pc" XkbRules "xfree86" XkbModel "pc101" XkbLayout "us" EndSection # ********************************************************************** # Pointer section # ********************************************************************** Section "Pointer" Protocol "PS/2" Device "/dev/mouse" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Protocol "Xqueue" # Baudrate and SampleRate are only for some Logitech mice # BaudRate 9600 # SampleRate 150 # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Emulate3Buttons Emulate3Timeout 50 # ChordMiddle is an option for some 3-button Logitech mice # ChordMiddle EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "My Monitor" VendorName "Unknown" ModelName "Unknown" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 24 - 80 # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 39-90 # Modes can be specified in two formats. A compact one-line format, or # a multi-line format. # These two are equivalent # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace # Mode "1024x768i" # DotClock 45 # HTimings 1024 1048 1208 1264 # VTimings 768 776 784 817 # Flags "Interlace" # EndMode # This is a set of standard mode timings. Modes that are out of monitor spec # are automatically deleted by the server (provided the HorizSync and # VertRefresh lines are correct), so there's no immediate need to # delete mode timings (unless particular mode timings don't work on your # monitor). With these modes, the best standard mode that your monitor # and video card can support for a given resolution is automatically # used. ModeLine "800x600@8bpp" 36 800 824 896 1024 600 601 603 625 Modeline "800x600@16bpp" 40 800 824 896 1024 600 601 603 625 Modeline "800x600@24bpp" 40 800 824 896 1024 600 601 603 625 EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present Section "Device" Identifier "Generic VGA" VendorName "Unknown" BoardName "Unknown" Chipset "generic" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Device configured by Xconfigurator: Section "Device" Identifier "Chips & Technologies CT65545" VendorName "Unknown" BoardName "Unknown" VideoRam 2048 # Option "noaccel" # Option "no_bitblt" # Option "xaa_no_color_exp" # Option "xaa_benchmark" # Option "hw_cursor" # Option "sync_on_green" # Option "fast_dram" # Option "use_vclk1" # Textclockfreq 25.175 # Option "nolinear" # MemBase 0x03b00000 # Device section for C&T cards. # Option "suspend_hack" # Option "STN" # Option "no_stretch" # Option "no_center" # Option "use_modeline" # Option "fix_panel_size" # videoram 512 # Insert Clocks lines here if appropriate EndSection # ********************************************************************** # Screen sections # ********************************************************************** # The Colour SVGA server Section "Screen" Driver "svga" # Use Device "Generic VGA" for Standard VGA 320x200x256 #Device "Generic VGA" Device "Chips & Technologies CT65545" Monitor "My Monitor" DefaultColorDepth 16 Subsection "Display" Depth 8 # Omit the Modes line for the "Generic VGA" device Modes "800x600@8bpp" ViewPort 0 0 Virtual 0 0 EndSubsection Subsection "Display" Depth 16 # Omit the Modes line for the "Generic VGA" device Modes "800x600@16bpp" ViewPort 0 0 Virtual 0 0 EndSubsection Subsection "Display" Depth 24 # Omit the Modes line for the "Generic VGA" device Modes "800x600@24bpp" ViewPort 0 0 Virtual 0 0 EndSubsection EndSection # The 16-Color VGA Server Section "Screen" Driver "vga16" Device "Generic VGA" Monitor "My Monitor" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 0 0 EndSubsection EndSection # The Mono server Section "Screen" Driver "vga2" Device "Generic VGA" Monitor "My Monitor" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 0 0 EndSubsection EndSection # The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64 # I128, and S3V) Section "Screen" Driver "accel" Device "Chips & Technologies CT65545" Monitor "My Monitor" Subsection "Display" Depth 8 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "800x600" "640x480" "640x400" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 32 Modes "640x480" "800x600" ViewPort 0 0 EndSubsection EndSection