PMDF Installation Guide
OpenVMS Edition
Previous Next Contents Index

1.7.3 Additional Post-Installation Tasks for Sites Upgrading from PMDF V5.1 or Earlier
  1. If you were using the PMDF popstore in PMDF V5.1, note that to accelerate certain management functions (e.g., generating listings of user accounts, using wild cards in conjunction with account management commands), a database of user accounts was added as of PMDF V5.2. This database, referred to as the popstore user database, is located in the PMDF_POPSTORE_PROFILES:[000000] directory. This database is only used for management functions and does not in any way impact the performance of the popstore.
    Sites using the popstore under PMDF V5.1 should issue this command: 


    $ PMDF POPSTORE X-BUILD-USER-DB

    after upgrading. This command scans the profile directory tree and builds a user database.
    Sites upgrading from V5.1 of the popstore should note that the popstore will continue to function without this command being issued. At issue is that some management operations will not function until this command is executed.

  2. If you are upgrading from PMDF V5.1 and using the POP or IMAP server, be aware that some password handling changed as of PMDF V5.2:
    1. As of PMDF V5.2, the POP and IMAP servers now check whether a user's password has expired, and will not allow authentication with an expired password. Check that your users do not have expired passwords.
    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. The current (PMDF V5.2 and later) behavior is preferable for most sites. But if you need to achieve the PMDF V5.1 behavior, you would need to configure the following. Use a PORT_ACCESS to segregate POP and IMAP connections into different rulesets, e.g., 


      PORT_ACCESS 
 
 TCP|*|110|*|*        $YPOP-RULES 
 TCP|*|143|*|*        $YIMAP-RULES
      Then you would need corresponding security configuration 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/*

  3. As of PMDF V5.2, the IMAP server supports hierarchical folders. As part of that support, IMAP users can no longer use the slash character, /, in normal folder names. If you are upgrading from PMDF V5.1 or earlier, IMAP users with existing folder names containing the slash character will need to rename those folders using something other than IMAP, e.g., using VMS MAIL or PMDF MAIL, in order to see the folders from IMAP. You might find the FIND_SLASHES program helpful for spotting (and optionally renaming) such folders, as discussed in Section 1.5.
  4. If you are upgrading from PMDF V5.1, note that as of PMDF V5.2 the LOG_CONNECTION PMDF option for controlling logging of connection information takes a bit-encoded value for specific controls rather than simply an an on/off setting as in PMDF V5.1, so you might want to change your setting of this option; see the PMDF System Manager's Guide for a discussion of the current meanings of values for this option.
  5. For sites upgrading from PMDF V5.1 using the PMDF Lotus Notes channel, if you have not already done so you must now 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

  6. The old (obsolete as of PMDF V5.2) single threaded, package-specific PMDF TCP/IP channels, e.g., MTCP, PTCP, UTCP, and WTCP channels, are no longer provided having been superseded by the newer, higher performance, multithreaded TCP/IP channel. If you were using those old channels, you will need to update your configuration to use the multithreaded TCP/IP channel instead; see Section 1.7.5 for a discussion of converting to use of the multithreaded TCP/IP channel.

Previous Next Contents Index