Last Update: 28-Mar-2000
Operating System: OpenVMS
Component: PMDF Shared Library
Base Level Required: PMDF V5.2-31
Other Requirements: none
Platform Subdirectory File(s) to download
-------- ------------ --------------------
OpenVMS VAX [.VMS.VAX_EXE] PMDFSHR.EXE
OpenVMS Alpha [.VMS.ALPHA_EXE] PMDFSHR.EXE
Tru64 UNIX osf/lib/ n/a
Solaris SPARC solaris-sparc/lib/ n/a
Solaris x86 solaris-x86/lib/ n/a
NT Alpha [.NT-ALPHA] n/a
NT Intel [.NT-INTEL] n/a
OS2 os2/ n/a
General info
------------
You will need to have a License PAK with a release date after the date of
this PMDFSHR.EXE to run PMDF. Note that this may apply to other images as
well.
When FTPing these images, be sure to FTP them as binary images. Before
retrieving such an image with the GET command, be sure to put your FTP into
binary mode with a command such as TYPE IMAGE or TYPE BINARY.
If you are using the DIRSYNC product, you will need to fetch the newer
images listed on the AA_DIRSYNC_PATCHES.HTML page.
Change history
---------------
28-Mar-2000
Fixed a problem with no intrusion records on VMS 6.x with pop/imap login
failures. This was broken on VMS around March 1999.
22-Mar-2000
Added a new option for PMDF-MR called FROM_TO_REPLYTO which will copy From
information to the ReplyTo field when no ReplyTo information is available.
29-Nov-1999
Fixed a problem that could cause an ACCVIO in DELIVER when certain header
fields weren't present.
19-Nov-1999
Fixed a problem with TURN and local address cache; also fixed a problem with
4xx response to DATA.
20-Oct-1999
Fixed a bug which caused a successful password match to trigger both
MATCH and NOMATCH activity logging calls. This only applies if user-supplied
popstore activity logging is used.
13-Oct-1999
Fixed a problem that could cause channels to abort when processing a long,
illegally formatted Received: header.
2-Sep-1999
Fixed a bug whereby the intrusion count was off by one.
7-Jul-1999
Fixed broken "nodns" behavior that would cause an ACCVIO in the TCP client.
2-Jul-1999
Be sure to erase SMTP response buffer when encountering an SMTP error;
previously, garbage text might propagate into the error text recorded in
the log file and message delivery history, and extraneous SMTP responses
could appear in, for instance, TCP/IP client debug log files.
10-Jun-1999
Fixed a problem with address groups in the middle of a list of addresses
losing preceeding comma.
Fixed a problem with USE_REVERSE_DATABASE=128 affecting the mappings pattern.
7-Jun-1999
Fixed a problem in PMDFGetAddressProperty handling empty RFC822 groups.
27-May-1999
Further generalizedtime fixes for PMDF-X400.
23-May-1999
Made a change to allow UTC times in generalized time fields in X.400.
22-May-1999
Messages submitted from VMS MAIL now do not unconditionally assume that the
message was submitted using NOTARY; whether or not NOTARY submission is
considered to have occurred is now assumed based on the L channel's report*
channel keyword setting. In particular, this means that the PMDF-FAX
ACKNOWLEDGEMENT channel option can be relevant for messages submitted from
VMS MAIL.
12-May-1999
Fixed a problem handling recipients with two or more active sieve scripts.
5-May-1999
Limit the portion of HELO/EHLO parameter stored for logging purposes to 128
characters.
Fixed a problem with decoding X.400 BP14s carried inside of BP15s for messages
received from X.400 or Mailbus 400.
28-Apr-1999
The web-based management interface needed some changes so as to allow
group managers to make changes to existing accounts. These changes are
only relevant to sites using group management.
21-Apr-1999
Made a change to use 1022 byte buffers so that undefined file formats will be
handled properly in VMS MAIL.
16-Apr-1999
When PMDF-X400 or PMDF-MB400 is processing DSNs, DSNs that cannot be legally
converted to X.400 reports such as DSNs regarding Message Router or other
"foreign" addresses will now be converted to X.400 messages, rather than
causing the mime_to_x400 or xapi_local channel to abort.
7-Apr-1999
Fixed another problem with X.400 notifications.
21-Mar-1999
More X.400 notifications support work
11-Mar-1999
Added support to workaround the change Compaq introduced in UCX V5.0's
nameserver logicals (i.e., added support for the new TCPIP$BIND_SERVER*
logicals). Prior to this change, the SMTP client would encounter
"resolver errno = 2" errors on UCX V5.0 systems.
8-Mar-1999
More X.400 notifications support work
The mailing list named parameters [AUTH_MAPPING], [MODERATOR_MAPPING] and
[CANT_MAPPING] -- which formerly unconditionally and automatically rejected
empty envelope From: addresses (i.e., notification messages) -- will now probe
the respective mapping table for an empty envelope From: match (* match).
This may be useful for those rare cases where one actually wants to pass
notification messages through to an entire list.
4-Mar-1999
The mailing list parameter [HEADER_ADDITION] is now applied only upon actual
postings, not upon redirections to the moderator when [MODERATOR_*]
parameters are in effect.
25-Feb-1999
Corrected the interpretation of the TCP/IP channel option
ATTEMPT_TRANSACTIONS_PER_SESSION; previously the interpretation was off by
one.
16-Feb-1999
If a user's password is expired, the POP and IMAP servers will now say so
in the reply to the login attempt. If the account is expired, the servers
will now say that as well.
11-Feb-1999
Fixed subaddressrelaxed keyword support so that the proper final probe (sans
any subaddress information) is performed.
Added access to an additional popstore routine.
8-Feb-1999
Fixed a problem with truncated queue entries.
Installation
------------
OpenVMS
Before installing a new PMDFSHR.EXE, issue the following command:
$ PMDF SHUTDOWN DISPATCHER
Failure to issue the above command could result in the current processes
not recognizing commands (i.e., RESTART and SHUTDOWN) with the new
PMDFSHR.EXE in place.
PMDFSHR.EXE needs to be copied to the PMDF_EXE: directory and then
installed with the command:
$ INSTALL REPLACE PMDF_SHARE_LIBRARY
on all members of the OpenVMS cluster running out of the affected PMDF
directory tree.
In some cases new versions of PMDFSHR.EXE may alter the format of compiled
configurations. When this happens recompilation and reinstallation are also
necessary:
$ PMDF CNBUILD/OPTION
$ INSTALL REPLACE PMDF_CONFIG_DATA
The first command need only be done once on VAX and once on AXP; the latter
must be done on every cluster member that runs PMDF. Failure to recompile and
install the configuration after installing new versions of PMDFSHR.EXE may
lead to "compiled configuration version mismatch" errors.
Next, be sure to start the dispatcher by issuing the following command:
$ PMDF STARTUP DISPATCHER
Note: If you are ftping PMDFSHR_Z.EXE image, which is a self-extracting
compressed version of the PMDFSHR.EXE image, simply issue the following
command:
$ RUN PMDFSHR_Z.EXE
to extract the file. Then follow the instructions above for installing it.
Solaris, Tru64 UNIX
Not applicable
NT
Not applicable