PMDF Installation Guide
Tru64 UNIX Edition
PMDF-INST-DUX-60

The following is a list of tasks which must be completed following an upgrade installation of PMDF.

• If you are using a compiled PMDF configuration, you must recompile it with the command

  # pmdf cnbuild
  

  
  
• As of PMDF V6.0, there is a new PMDF periodic job that you need to schedule cron to run periodically. If you have not customized your pmdf crontab entries, then you may simply issue the commands:

  # su pmdf
  # crontab /pmdf/table/cronjobs
  # exit
  

  Otherwise, if you prefer to add the new crontab entry manually so as not to overwrite your existing, possibly customized, pmdf crontab entries, then issue the commands

  # su pmdf
  # crontab -e
  

  and use the editor thus invoked to add an entry such as the following:

  0  0,10,20,30,40,50 * * * * /pmdf/bin/pmdf_lg_purge >/dev/null 2>&1 
  

  Make sure to exit from the pmdf user shell when you have finished adding this entry; i.e.,

  $ exit
  

  
  
• The underlying storage of all PMDF databases has changed as of PMDF V6.0 from the format used in PMDF V5.2 and earlier. In particular, all PMDF crdb databases must be rebuilt or converted using the pmdf convertdd utility. The /pmdf/bin/finddb.sh shell script may be used to attempt to detect the major PMDF databases; running this utility will create a script file that may then be run in order to actually convert the databases.

  # /pmdf/bin/finddb.sh
  

  Note, however, that if you have additional PMDF databases on your system (for instance, users' own personal alias databases), then you will also need to convert those databases. Please also note that the base name (name sans file extension) of the PMDF password database has been changed from pauth to passworddb, so if your sites uses the PMDF password database (not all sites do) be sure to use the new name when you are converting the password database, e.g.,

  # pmdf convertdb /pmdf/table/pauth /pmdf/table/passworddb
  

  
  
• The format of the PMDF queue cache database has changed as of PMDF V6.0 from the format used in PMDF V5.2 and earlier. Therefore the PMDF queue cache database must be rebuilt, via the commands

  # rm /pmdf/table/queue_cache/*
  # pmdf cache -synchronize
  

  Note that it is a good idea to rebuild the PMDF queue cache database with the above commands or with the command

  # pmdf cache -rebuild
  

  after any upgrade of PMDF, including after minor interim releases.
  
• UNIX sites which were using the popstore under PMDF V5.2 or earlier and which are upgrading to PMDF V6.0 must rebuild (or should build for the first time) the PMDF popstore user database since its format has changed. (As of PMDF V5.2, in order to accelerate certain management functions such as generating listings of user accounts, using wild cards in conjunction with account management commands, etc., a database of user accounts is used by the popstore. This database, referred to as the popstore user database, is located in the /pmdf/user/ directory on UNIX systems. This database is only used for management functions and does not in any way impact the performance of the popstore.) The PMDF popstore user database is located via the PMDF_POPSTORE_USER_DATABASE PMDF tailor file option, and so is usually /pmdf/user/userdb. Sites upgrading from PMDF V5.2 must rebuild their existing popstore user database using the commands

  # rm /pmdf/user/userdb.*
  # pmdf popstore x_build_user_db
  

  Sites which were using the PMDF popstore under PMDF V5.1 and which are upgrading to PMDF V6.0 should create a popstore user database using the command

  # pmdf popstore x_build_user_db
  

  after upgrading to PMDF V6.0. This command will scan the profile directory tree and build a user database.
  
• If you are using the pmdfcyrus program to deliver to the Cyrus message store, you should check the permission settings for the /pmdf/bin/pmdfcyrus image to make sure that they are still correct. The PMDF installation attempts to set the permissions properly when it updates the image. But if the permissions are not correct, you will need to reset them manually with the commands:

  # chown cyrus-user /pmdf/bin/pmdfcyrus
  # chmod 4755 /pmdf/bin/pmdfcyrus
  

  where cyrus-user is whatever userid was selected when installing Cyrus, typically cyrus.
  
• If you are using the PMDF-LAN Lotus Notes channel or PMDF-XGS, be sure to upgrade the PMDF images used on the Lotus Notes server or XGS transport bridge system. These are OS/2 or NT PMDF images, available under the /pmdf/other/ directory on the PMDF system, or available directly off the PMDF distribution CD-ROM under the other directory. Note that this is an ISO 9660 with Rockridge extensions CD-ROM, readable from many different platforms including OS/2 and NT.
  • a. For PMDF-XGS, shutdown all the PMDF-XGS processes on the transport bridge and then copy the respective files to the transport bridge system. Then restart the PMDF-XGS processes on the transport bridge system.
  • b. For a PMDF-LAN Lotus Notes channel, shut down the PMDF Lotus Notes Server Add-ins, using Lotus Notes server console commands such as TELL PNGATECIN QUIT, and TELL PNGATECOUT QUIT (or just TELL PNGATEC QUIT if you were using just the one Server Add-in). Then copy the new server Add-ins to the Lotus Notes server, and startup them back up (e.g., LOAD PNGATECIN and LOAD PNGATECOUT). If you have not already done so, note that this is a good time to switch to using the two independent Server Add-ins PNGATECIN and PNGATECOUT in place of the single PNGATEC Add-in originally released in PMDF V5.1: change the line in the Lotus Notes initialization file, notes.ini, defining server tasks from

    ServerTasks=...,PNGATEC 
    

    to

    ServerTasks=...,PNGATECIN,PNGATECOUT 
    

    
    
  • Start up the PMDF Job Controller and PMDF Service Dispatcher using the command

    # pmdf startup    
    

    
    
  • If you also installed PMDF-DIRSYNC, PMDF-LAN, PMDF-MB400, PMDF-X400, or PMDF-XGS for the first time, then you should configure them now. Configuration instructions for PMDF-LAN may be found in Chapters 9 and 10 ; configuration instructions for PMDF-MB400 may be found in Chapters 11 and 12 ; configuration instructions for PMDF-X400 may be found in Chapters 13 and 14 ; configuration instructions for PMDF-XGS may be found in Chapters 15 through 18 .

    1.5.1 Additional post-installation tasks for sites upgrading from PMDF V5.1 or V5.0

    The following is a list of additional post-installation tasks that must be completed following an upgrade from V5.1 or V5.0 of PMDF-MTA, PMDF-ACCESS, PMDF-DIRSYNC, PMDF-LAN, PMDF-MB400, or PMDF-X400. Sites upgrading from PMDF V5.2 or later should skip this section.
    • Update configuration:
      • a. V5.1 PMDF-X400 or PMDF-MB400 sites that were using the former MIME-CONTENT-TYPES-TO-X400 mapping table to control the mapping of MIME attachments to X.400 attachments should note that that mapping table became obsolete as of PMDF V5.2, having been superseded by the new, more general, MIME-TO-X400-CONTENT-TYPES mapping table. You must convert the name of the mapping table to the new name, and also include the new channel name argument on the left hand (pattern) side; for a useful sample starting point, see the file /pmdf/table/x400_mappings.sample.
      • b. If you are using PMDF POP or IMAP servers, be aware that some password handling changed as of PMDF V5.2. The new, configurable authentication source control used as of PMDF V5.2 by, for instance, the POP and IMAP servers has default behavior that is intended to operate "naturally" and usually means no visible change to users. But a few users with less natural setups (for instance, non-popstore users who have PMDF password database entries different from their system password) can see a change in behavior.
        To achieve the prior PMDF V5.0 or PMDF 5.1 behavior in PMDF 6.0, a PORT_ACCESS mapping would need to segregate POP and IMAP connections into different rulesets, e.g.,

        PORT_ACCESS 
         
         TCP|*|110|*|*        $YPOP-RULES 
         TCP|*|143|*|*        $YIMAP-RULES 
         
        

        and the security configuration file security.cnf would need corresponding ruleset definitions of:

        [RULESET=DEFAULT] 
        ENABLE=MSGSTORE/*,PASSDB/*,SYSTEM/* 
        ! 
        [RULESET=POP-RULES] 
        ENABLE=MSGSTORE/*,PASSDB/CRAM-MD5,PASSDB/APOP,SYSTEM/* 
        ! 
        [RULESET=IMAP-RULES] 
        ENABLE=SYSTEM/* 
        

      • c. The LOG_CONNECTION PMDF option for controlling logging of connection information is now not simply an on/off setting as in PMDF V5.0 and PMDF V5.1, but rather is bit-encoded for more specific controls.
        
      • If you are upgrading from PMDF V5.0 (which used the image /pmdf/bin/pmdfsend rather than the new image /pmdf/bin/sendmail to replace sendmail) then you must replace sendmail with PMDF's /pmdf/bin/sendmail. Change the symbolic link for sendmail to /pmdf/bin/sendmail as follows:

        # ln -s /pmdf/bin/sendmail /usr/sbin/sendmail
        

      • If you are upgrading from PMDF V5.0, note that the PMDF periodic post shell script and PMDF return shell script which used to be named /pmdf/bin/post and /pmdf/bin/return in PMDF V5.0, as of PMDF V5.1 are instead named /pmdf/bin/post.sh and /pmdf/bin/return.sh, respectively. So if you are upgrading from PMDF V5.0, you must change the crontab entries for these jobs to use the new names. This can be performed by issuing the commands: ²

        # su pmdf
        $ crontab /pmdf/table/cronjobs
        $ exit
        

        
        
      • If you are upgrading from PMDF V5.0 and use the SMTP server, note that this service is now handled by the PMDF Service Dispatcher. You must configure the PMDF Service Dispatcher to handle the SMTP server or any other servers under its control. Dispatcher configuration is normally performed as part of the initial web-based PMDF-MTA configuration or as part of the command line PMDF-ACCESS configuration; see Chapters 5 , 6 , and Chapter 7 for instructions and sample configurations. The multithreaded POP3 and IMAP servers are handled by the PMDF Service Dispatcher. If you were previously using non-PMDF servers, or older PMDF singlethreaded servers running under the inetd daemon, then you must shut down your old servers before you can use the PMDF multithreaded servers. Before you can use the multithreaded POP3 or IMAP servers, you must also configure the Dispatcher to run the desired service. Dispatcher configuration is normally performed as part of the initial web-based PMDF-MTA configuration or as part of the command line PMDF-ACCESS configuration; see Chapters 5 , 6 , and Chapter 7 for instructions and sample configurations of the Dispatcher. See Chapter 8 for instructions and Chapter 5 for an example of configuring the POP and IMAP servers.

        ---

        Note

        ² If you prefer to manually change the cron entries, as for instance if you have previously customized those entries for site-specific reasons, then you may perform the following steps. To submit commands to the cron daemon, first become the user pmdf:

        # su pmdf

        Then to edit the crontab entries, issue the commands

        # su 
        pmdf$ crontab -e

        and use the editor thus invoked to edit the entries to use the new names, i.e., so that they appear similar to:

        30 0 * * * 
        /pmdf/bin/return.sh >/pmdf/log/return.log-`/pmdf/bin/unique_id` 
        2>&1 0 0,4,8,12,16,20 * * * /pmdf/bin/post.sh 
        >/pmdf/log/post.log-`/pmdf/bin/unique_id` 2>&1 0 
        0,10,20,30,40,50 * * * * /pmdf/bin/pmdf_lg_purge >/dev/null 
        2>&1 

        The first value in the second line, shown as 0 in the example above, is the minutes-after-the-hour offset; particularly if you have multiple PMDF nodes, then this is a value which you might wish to stagger between different nodes, e.g., 0 on one node, 10 on a second node, 20 on a third node, etc. Also note the use of log files in the above; such log files can be useful in tracking down problems with the operation of return.sh and post.sh. Make sure to exit from the pmdf user shell when you have finished adding these entries; i.e.,

        $ exit

        ---

        ---

        Previous | Next | Contents