|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Sun Dec 09 2001 - 09:52:56 CST
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun Dec 9 3:05:41 PST 2001
Table of Contents:
Document ID Title
--------------- -----------
PHSS_24991 s700_800 11.X OV OB4.00 patch - LOTUS packet
PHSS_24983 s700_800 11.X OV OB4.00 patch - SAP packet
PHSS_25838 s700_800 11.04 VirtualVault 4.5 OWS update
PHSS_25689 s700_800 11.11 N4000 41.46 firmware patch
PHSS_25688 s700_800 11.00 N4000 41.46 firmware patch
PHSS_25687 s700_800 11.11 L3000 41.46 firmware patch
PHSS_25686 s700_800 11.00 L3000 41.46 firmware patch
PHSS_25685 s700_800 11.11 L1000/L2000 41.39 firmware patch
PHSS_25684 s700_800 11.00 L1000/L2000 41.39 firmware patch
PHSS_25646 s700_800 11.X OpenMail B.06.00 December 01 Periodic Patch
PHSS_25262 s700_800 11.X OpenGL 1.1 Dev (PA2.0 only)
PHSS_25261 s700_800 11.X OpenGL 1.1 Run (PA2.0 only)
PHSS_25260 s700_800 11.X PHIGS Dev (PA2.0 only)
PHSS_25259 s700_800 11.X PHIGS Run (PA2.0 only)
PHSS_25258 s700_800 11.X Starbase/Hardcopy Dev (PA2.0 only)
PHSS_25257 s700_800 11.X PEX 5.1 Dev (PA2.0 only)
PHSS_25256 s700_800 11.X PEX 5.1 Run (PA2.0 only)
PHSS_25255 s700_800 11.X DDA Run (PA2.0 only)
PHSS_25254 s700_800 11.X PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
PHSS_25253 s700_800 11.X 3D Common Run (PA2.0 only)
PHSS_24995 s700_800 11.X OV OB4.00 patch - CORE packet
PHSS_25795 s700_800 11.00 OV ITO5.3X SOLARIS Agent Patch A.05.39
PHKL_25729 s700_800 11.11 signals,threads enhancement,Psets Enablement
PHKL_25728 s700_800 11.11 Psets Enablement, thread cumulative
PHKL_25367 s700_800 11.11 Priority inversion and thread hang
PHCO_25814 s700_800 11.11 LVM commands cumulative patch
PHKL_25813 s700_800 11.00 Cumulative mmap fixes
PHKL_25773 s700_800 11.11 Psets & vPar Enablement, Reboot Hangs
PHKL_25690 s700_800 11.11 Dump support for EMC disk arrays
PHKL_25056 s700_800 11.04 (VVOS) PM cumulative patch
PHCO_25723 s700_800 11.11 q4 patch version B.11.20f
PHCO_24705 s700_800 11.00 cumulative patch for mkmf(1)
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_24991
Date Loaded: 20011207
Title: s700_800 11.X OV OB4.00 patch - LOTUS packet
Patch Name: PHSS_24991
Patch Description: s700_800 11.X OV OB4.00 patch - LOTUS packet
Creation Date: 01/11/28
Post Date: 01/12/07
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.04.00
Filesets:
OMNIBACK-II.OMNI-CORE-IS,fr=A.04.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_24991
Symptoms:
PHSS_24991:
Id = HSLco23175
OmniBack II does not support Lotus Domino.
Defect Description:
PHSS_24991:
Id = HSLco23175
OmniBack II does not support Lotus Domino.
Resolution:
OmniBack II supports Lotus Domino on HP-UX 11.x and
AIX systems.
OmniBack II Lotus Domino integration will work when in
addition these patches (or their successors) are
available and installed:
PHSS_24992/PHSS_24993 (Cell Console)
PHSS_24994/PHSS_24995 (Core).
Please see Special Installation Instructions.
SR:
H555003773
Patch Files:
OMNIBACK-II.OMNI-CORE-IS,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/lotus/hp/s800/hp-ux-11/A.04.00/
packet.Z
/opt/omni/databases/vendor/lotus/hp/s800/hp-ux-11/A.04.00/
require.dat
/opt/omni/databases/vendor/lotus/ibm/rs6000/aix-42/A.04.00/
packet.Z
/opt/omni/databases/vendor/lotus/ibm/rs6000/aix-42/A.04.00/
require.dat
what(1) Output:
OMNIBACK-II.OMNI-CORE-IS,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/lotus/hp/s800/hp-ux-11/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/lotus/hp/s800/hp-ux-11/A.04.00/
require.dat:
None
/opt/omni/databases/vendor/lotus/ibm/rs6000/aix-42/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/lotus/ibm/rs6000/aix-42/A.04.00/
require.dat:
None
cksum(1) Output:
OMNIBACK-II.OMNI-CORE-IS,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3065157145 1277057 /opt/omni/databases/vendor/lotus/hp/s800/
hp-ux-11/A.04.00/packet.Z
239274258 17 /opt/omni/databases/vendor/lotus/hp/s800/
hp-ux-11/A.04.00/require.dat
59694798 1169467 /opt/omni/databases/vendor/lotus/ibm/
rs6000/aix-42/A.04.00/packet.Z
2630127531 17 /opt/omni/databases/vendor/lotus/ibm/rs6000/
aix-42/A.04.00/require.dat
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_24990:
s700: 10.20
s800: 10.20
Patch Package Size: 2410 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_24991
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_24991.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_24991. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_24991.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_24991.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_24991.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_24991.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24991:
NOTE!
Patch has to be installed on the Installation Server host.
The Lotus Domino Agent packets must be redistributed to the
Cell Manager system and client systems afterwards to get the
fixes into effect.
NOTE!
After the installation of the PHSS_24990/PHSS_24991 is
completed and Core patch PHSS_24994/PHSS_24995 is
installed, please export and then import Installation
Server system from the GUI.
For more details reffer to Lotus Domino Integration Guide
located in $OmniHome/doc directory after the patch
has been installed and Lotus Domino integration packets
redistributed.
-----End of Document ID: PHSS_24991------------------------------------------
Document ID: PHSS_24983
Date Loaded: 20011207
Title: s700_800 11.X OV OB4.00 patch - SAP packet
Patch Name: PHSS_24983
Patch Description: s700_800 11.X OV OB4.00 patch - SAP packet
Creation Date: 01/11/29
Post Date: 01/12/07
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.04.00
Filesets:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_24983
Symptoms:
PHSS_24983:
Id = HSLco27809 SR: H555005775
SAP R/3 backup preview abnormally ends on Solaris
platform.
Id = HSLco27898 SR: H555005806
"Util_sap -OBJSO <SID>" is not excluding locally
managed temporary tablespaces from the list of all
tablespaces.
Id = HSLco28402 SR: H555006012
Omnisap crashes at the end of backup.
Id = HSLco28403 SR: H555006013
SAP can not be configured when running on Oracle 8.0.x.
Id = NSMex04633, NSMex04725 SR: H555006500
If omnisap.exe runs only brarchive, it does not change
-u user to -u user/password.
Id = NSMex04698 SR: H555006672
SAP restore to different system and directory fails.
Id = HSLco28624 SR: H555006085
Symbolic links can not be restored neither via
SAP/backint restore nor via filesystem restore.
Id = HSLco28862 SR: H555006173
When running split mirror backup backup SAP
integration reads configuration for application
host, not for the backup host.
Id = HSLco28960 SR: H555006205
SAP backup fails with an error:
"Unable to find library 'libclntsh.sl.8.0"
Id = HSLco29240 SR: H555006290
SAP backup fails with segmentation fault error.
Defect Description:
PHSS_24983:
Id = HSLco27809
Null pointer string in debugs is passed on as an
argument, which causes core dump.
Resolution:
Source code is made safe to null pointer strings.
Id = HSLco27898
Incorrect query for displaying Oracle tablespaces is
used. Locally managed tablespaces must be excluded
from the list of all tablespaces.
Resolution:
Query is fixed, locally managed tablespaces are not
displayed.
Id = HSLco28402
Depending on the environment incorrect FREE() command
can be executed in some cases.
Resolution:
All variables are properly allocated.
Id = HSLco28403
Wrong query (Oracle 8.1.x specific) is used to check
login and password.
Resolution:
Query for Oracle 8.1.x is run and if it fails with
error "Invalid column name", query for Oracle 8.0.x.
is run.
Id = NSMex04633, NSMex04725
When -u option is not specified in backup specification
the owner of the backup specification is used. If you
specify the -u user/password it should be used instead.
Part of SSPUX400_008.
Resolution:
The same -u option which is used for brbackup in the
CheckSAPfiles is now used in brarchive.
Id = NSMex04698
Attempted to write random memory content to the file.
Resolution:
Memory is cleared before random memory is written.
Id = HSLco28624
Format of symbolic links backed up with SAP is not
consistent with Disk agent format. When backing up
symbolic link as part of directory the contents
of file is backed up instead of link.
Resolution:
Format of backint is changed in accordance with
Disk agent format.
Id = HSLco28862
If OB2BARHOSTNAME is set in split mirror backup,
it is incorrectly used.
Resolution:
New variable OB2BAROBJNAME is introduced. In case
of split mirror backup it is used for forming object
names.
Id = HSLco28960
Library is not found in SHLIB_PATH and LD_LIBRARY_PATH.
Resolution:
ORACLE_HOME/lib64 is added to SHLIB_PATH and
LD_LIBRARY_PATH.
Id = HSLco29240
During conversion of string "NextSetNumber" to integer
there is no checking if the input parameter to 'atoi'
function is null. If this happened backup session
ended with segmentation error massage.
Resolution:
Input parameter of 'atoi' function is checked. If it
is null, the function is not called.
SR:
H555006290 H555006173 H555006012 H555006013 H555006085
H555006500 H555005806 H555006205 H555006672 H555005775
Patch Files:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.00/
packet.Z
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.00/
packet.Z
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.00/
packet.Z
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.00/
packet.Z
what(1) Output:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.00/
packet.Z:
None
cksum(1) Output:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1958285489 1296859 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-1020/A.04.00/packet.Z
1645162178 1297119 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-11/A.04.00/packet.Z
2782026806 1149453 /opt/omni/databases/vendor/sap/ibm/
rs6000/aix-42/A.04.00/packet.Z
350798194 1214419 /opt/omni/databases/vendor/sap/sun/sparc/
solaris-26/A.04.00/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_24982:
s700: 10.20
s800: 10.20
Patch Package Size: 4870 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_24983
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_24983.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_24983. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_24983.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_24983.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_24983.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_24983.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24983:
NOTE!
This Patch has to be installed on the Installation
Server host.
The OB2 SAP agent must be redistributed to the SAP
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SAP agent, refer to
the OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX400_008
-----End of Document ID: PHSS_24983------------------------------------------
Document ID: PHSS_25838
Date Loaded: 20011206
Title: s700_800 11.04 VirtualVault 4.5 OWS update
Patch Name: PHSS_25838
Patch Description: s700_800 11.04 VirtualVault 4.5 OWS update
Creation Date: 01/11/30
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
VirtualVault A.04.50
Filesets:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25838
Symptoms:
PHSS_25838:
1. Apache web server reprompts for certificate
during same SSL session.
2. Apache web server can not pass client
certificate information through proxy like
previous VirtualVault versions.
PHSS_24052:
1. Outside Apache web servers do not support SpeedCard
on N, R, L, A, K and D class servers.
2. The SSLSessionCache directive does not support
shared memory (shm).
Defect Description:
PHSS_25838:
1. Apache web server reprompts for certificate
during reused SSL session after a
client/server disconnect.
2. Apache web server can not pass client
certificate information through proxy like
previous VirtualVault versions.
Resolution:
1. If the Apache server has previously
verified a client certificate and the current
session context/cache has not recorded
a verification error, the client is allowed to
continue on the session without complete
SSL session renegotiation.
2. The outside server can pass client information
via HTTP headers in proxied requests.
PHSS_24052:
1. SpeedCard support is needed on N, R, L, A, K and D class
servers. To gain support for these servers, the outside
Apache web server needs to be migrated from version
1.3.14 to version 1.3.19.
2. Currently there is no shared Memory SSLSessionCache
support.
Resolution:
1. Migrate the Apache outside web server from version
1.3.14 to 1.3.19 and include SpeedCard support.
2. Include the open source Shared Memory Library
(mm.1.1.3) to provide shared memory SSL caching
for Apache.
This patch contains files specific to the VirtualVault 4.5
release.
SR:
8606227054 8606195978
Patch Files:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/25.patches/24052_PHSS.fcdb
/opt/vaultWS/bin/ows_create
/opt/vaultWS/install/bin/ab
/opt/vaultWS/install/bin/apxs
/opt/vaultWS/install/bin/dbmmanage
/opt/vaultWS/install/bin/htdigest
/opt/vaultWS/install/bin/htpasswd
/opt/vaultWS/install/bin/httpd
/opt/vaultWS/install/bin/logresolve
/opt/vaultWS/install/bin/rotatelogs
/opt/vaultWS/install/conf/httpd.conf
/opt/vaultWS/install/conf/httpd.conf.default
/opt/vaultWS/install/libexec/httpd.exp
/opt/vaultWS/install/libexec/libhttpd.ep
/opt/vaultWS/install/libexec/libhttpd.sl
/opt/vaultWS/install/libexec/libhttpd.sl.1
/opt/vaultWS/install/libexec/libhttpd.sl.1.3
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.19
/opt/vaultWS/install/libexec/libproxy.so
/opt/vaultWS/install/libexec/libssl.so
/opt/vaultWS/install/libexec/mod_access.so
/opt/vaultWS/install/libexec/mod_actions.so
/opt/vaultWS/install/libexec/mod_alias.so
/opt/vaultWS/install/libexec/mod_asis.so
/opt/vaultWS/install/libexec/mod_auth.so
/opt/vaultWS/install/libexec/mod_auth_anon.so
/opt/vaultWS/install/libexec/mod_auth_dbm.so
/opt/vaultWS/install/libexec/mod_autoindex.so
/opt/vaultWS/install/libexec/mod_cern_meta.so
/opt/vaultWS/install/libexec/mod_cgi.so
/opt/vaultWS/install/libexec/mod_define.so
/opt/vaultWS/install/libexec/mod_digest.so
/opt/vaultWS/install/libexec/mod_dir.so
/opt/vaultWS/install/libexec/mod_env.so
/opt/vaultWS/install/libexec/mod_expires.so
/opt/vaultWS/install/libexec/mod_headers.so
/opt/vaultWS/install/libexec/mod_imap.so
/opt/vaultWS/install/libexec/mod_include.so
/opt/vaultWS/install/libexec/mod_info.so
/opt/vaultWS/install/libexec/mod_jserv.so
/opt/vaultWS/install/libexec/mod_log_config.so
/opt/vaultWS/install/libexec/mod_mime.so
/opt/vaultWS/install/libexec/mod_mime_magic.so
/opt/vaultWS/install/libexec/mod_negotiation.so
/opt/vaultWS/install/libexec/mod_rewrite.so
/opt/vaultWS/install/libexec/mod_setenvif.so
/opt/vaultWS/install/libexec/mod_speling.so
/opt/vaultWS/install/libexec/mod_status.so
/opt/vaultWS/install/libexec/mod_tga.so
/opt/vaultWS/install/libexec/mod_unique_id.so
/opt/vaultWS/install/libexec/mod_userdir.so
/opt/vaultWS/install/libexec/mod_usertrack.so
/opt/vaultWS/install/libexec/mod_vhost_alias.so
/opt/vaultWS/install/libexec/speedcard/libssl.so
/opt/vaultTS/lib/libmm.a
/opt/vaultTS/lib/libmm.la
/opt/vaultTS/lib/libmm.sl
/opt/vaultTS/lib/libmm.sl.11
/opt/vaultTS/lib/libmm.sl.11.23
what(1) Output:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultWS/bin/ows_create:
(#)87 1.27 src/scripts/ows_create, vaultWS, vault
WS_4.5 05/10/01 12:38:43 PATCH_11.04 (PHSS_2
4052)
/opt/vaultWS/install/bin/ab:
None
/opt/vaultWS/install/bin/apxs:
None
/opt/vaultWS/install/bin/dbmmanage:
None
/opt/vaultWS/install/bin/htdigest:
None
/opt/vaultWS/install/bin/htpasswd:
None
/opt/vaultWS/install/bin/httpd:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
/opt/vaultWS/install/bin/logresolve:
None
/opt/vaultWS/install/bin/rotatelogs:
None
/opt/vaultWS/install/conf/httpd.conf:
None
/opt/vaultWS/install/conf/httpd.conf.default:
None
/opt/vaultWS/install/libexec/httpd.exp:
None
/opt/vaultWS/install/libexec/libhttpd.ep:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/05/03 08:15:12 $ $Rev
ision: 1.20 PATCH_11.04 (PHSS_24052) $
/opt/vaultWS/install/libexec/libhttpd.sl:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 01/05/03 08:16:27 $
$Revision: 1.5 PATCH_11.04 (PHSS_24052) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
/opt/vaultWS/install/libexec/libhttpd.sl.1:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 01/05/03 08:16:27 $
$Revision: 1.5 PATCH_11.04 (PHSS_24052) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
/opt/vaultWS/install/libexec/libhttpd.sl.1.3:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 01/05/03 08:16:27 $
$Revision: 1.5 PATCH_11.04 (PHSS_24052) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.19:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 01/05/03 08:16:27 $
$Revision: 1.5 PATCH_11.04 (PHSS_24052) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
/opt/vaultWS/install/libexec/libproxy.so:
$Source: src/apache/src/modules/proxy/mod_proxy.c, v
aultWS, vaultWS_4.5 $ $Date: 01/11/30 14:58:
09 $ $Revision: 1.6.1.1 PATCH_11.04 (PHSS_24
052) (PHSS_25838) $
$Source: src/apache/src/modules/proxy/proxy_http.c,
vaultWS, vaultWS_4.5 $ $Date: 01/11/30 14:59
:26 $ $Revision: 1.9.1.1 PATCH_11.04 (PHSS_2
4052) (PHSS_25838) $
src/apache/src/modules/proxy/proxy_http.c, vaultWS,
vaultWS_4.5 1.9.1.1 11/30/01
/opt/vaultWS/install/libexec/libssl.so:
mod_ssl/2.8.2
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.5 $ $Date: 01/11/30
14:56:02 $ $Revision: 1.4.1.1 PATCH_11.04 (P
HSS_25838) $
src/apache/src/modules/ssl/ssl_engine_config.c, vaul
tWS, vaultWS_4.5 1.4.1.1 11/30/01
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.5 $ $Date: 01/11/30
14:54:37 $ $Revision: 1.2.1.1 PATCH_11.04 (P
HSS_25838) $
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:31:00 $ $Revision: 1.5 PATCH_11.04 (PHSS_2
4052) $
$Source: src/apache/src/modules/ssl/ssl_engine_pphra
se.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03
08:26:52 $ $Revision: 1.9 PATCH_11.04 (PHSS
_24052) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.5 1.9 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache.c, va
ultWS, vaultWS_4.5 $ $Date: 01/05/03 08:32:5
8 $ $Revision: 1.4 PATCH_11.04 (PHSS_24052)
$
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 08:
34:22 $ $Revision: 1.5 PATCH_11.04 (PHSS_240
52) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:08:55 $ $Revision: 1.4 PATCH_11.04 (PHSS_2
4052) $
src/apache/src/modules/ssl/ssl_scache_shmht.c, vault
WS, vaultWS_4.5 1.4 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:08:38 $ $Revision: 1.4 PATCH_11.04 (PHSS_2
4052) $
src/apache/src/modules/ssl/ssl_scache_shmcb.c, vault
WS, vaultWS_4.5 1.4 05/03/01
/opt/vaultWS/install/libexec/mod_access.so:
None
/opt/vaultWS/install/libexec/mod_actions.so:
None
/opt/vaultWS/install/libexec/mod_alias.so:
None
/opt/vaultWS/install/libexec/mod_asis.so:
None
/opt/vaultWS/install/libexec/mod_auth.so:
None
/opt/vaultWS/install/libexec/mod_auth_anon.so:
None
/opt/vaultWS/install/libexec/mod_auth_dbm.so:
None
/opt/vaultWS/install/libexec/mod_autoindex.so:
None
/opt/vaultWS/install/libexec/mod_cern_meta.so:
None
/opt/vaultWS/install/libexec/mod_cgi.so:
None
/opt/vaultWS/install/libexec/mod_define.so:
None
/opt/vaultWS/install/libexec/mod_digest.so:
None
/opt/vaultWS/install/libexec/mod_dir.so:
None
/opt/vaultWS/install/libexec/mod_env.so:
None
/opt/vaultWS/install/libexec/mod_expires.so:
None
/opt/vaultWS/install/libexec/mod_headers.so:
None
/opt/vaultWS/install/libexec/mod_imap.so:
None
/opt/vaultWS/install/libexec/mod_include.so:
None
/opt/vaultWS/install/libexec/mod_info.so:
None
/opt/vaultWS/install/libexec/mod_jserv.so:
None
/opt/vaultWS/install/libexec/mod_log_config.so:
None
/opt/vaultWS/install/libexec/mod_mime.so:
None
/opt/vaultWS/install/libexec/mod_mime_magic.so:
None
/opt/vaultWS/install/libexec/mod_negotiation.so:
None
/opt/vaultWS/install/libexec/mod_rewrite.so:
$Source: src/apache/src/modules/standard/mod_rewrite
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:29:12 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
4052) $
/opt/vaultWS/install/libexec/mod_setenvif.so:
None
/opt/vaultWS/install/libexec/mod_speling.so:
None
/opt/vaultWS/install/libexec/mod_status.so:
None
/opt/vaultWS/install/libexec/mod_tga.so:
93 1.13.1.3 src/gateway/cgi2/iolib/io.c, vaultTS,
vaultTS_4.5 06/24/99 11:25:36
/opt/vaultWS/install/libexec/mod_unique_id.so:
None
/opt/vaultWS/install/libexec/mod_userdir.so:
None
/opt/vaultWS/install/libexec/mod_usertrack.so:
None
/opt/vaultWS/install/libexec/mod_vhost_alias.so:
None
/etc/auth/system/files.fcdb/25.patches/24052_PHSS.fcdb:
src/host/24038_PHSS.fcdb, vaultTS, vaultTS_4.5 1.1
05/01/01
/opt/vaultWS/install/libexec/speedcard/libssl.so:
mod_ssl/2.8.2
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:31:00 $ $Revision: 1.5 PATCH_11.04 (PHSS_2
4052) $
$Source: src/apache/src/modules/ssl/ssl_engine_pphra
se.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03
08:26:52 $ $Revision: 1.9 PATCH_11.04 (PHSS
_24052) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.5 1.9 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache.c, va
ultWS, vaultWS_4.5 $ $Date: 01/05/03 08:32:5
8 $ $Revision: 1.4 PATCH_11.04 (PHSS_24052)
$
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 08:
34:22 $ $Revision: 1.5 PATCH_11.04 (PHSS_240
52) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:08:55 $ $Revision: 1.4 PATCH_11.04 (PHSS_2
4052) $
src/apache/src/modules/ssl/ssl_scache_shmht.c, vault
WS, vaultWS_4.5 1.4 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:08:38 $ $Revision: 1.4 PATCH_11.04 (PHSS_2
4052) $
src/apache/src/modules/ssl/ssl_scache_shmcb.c, vault
WS, vaultWS_4.5 1.4 05/03/01
/opt/vaultTS/lib/libmm.a:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.la:
None
/opt/vaultTS/lib/libmm.sl:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.sl.11:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.sl.11.23:
MM 1.1.3 (01-Jul-2000)
cksum(1) Output:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
642930446 17793 /opt/vaultWS/bin/ows_create
1262687632 49259 /opt/vaultWS/install/bin/ab
4197983697 21154 /opt/vaultWS/install/bin/apxs
3811743186 10939 /opt/vaultWS/install/bin/dbmmanage
2658800727 36960 /opt/vaultWS/install/bin/htdigest
3650905660 73896 /opt/vaultWS/install/bin/htpasswd
3773140239 57446 /opt/vaultWS/install/bin/httpd
2174728145 24642 /opt/vaultWS/install/bin/logresolve
105961534 28733 /opt/vaultWS/install/bin/rotatelogs
1112552940 46521 /opt/vaultWS/install/conf/httpd.conf
1112552940 46521 /opt/vaultWS/install/conf/
httpd.conf.default
779068524 8304 /opt/vaultWS/install/libexec/httpd.exp
4242513649 24637 /opt/vaultWS/install/libexec/libhttpd.ep
3117099754 1059469 /opt/vaultWS/install/libexec/libhttpd.sl
3117099754 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1
3117099754 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3
3117099754 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3.19
2753623531 221478 /opt/vaultWS/install/libexec/libproxy.so
2152864597 2683660 /opt/vaultWS/install/libexec/libssl.so
2993986834 20509 /opt/vaultWS/install/libexec/mod_access.so
4152718123 16406 /opt/vaultWS/install/libexec/mod_actions.so
4275050123 20526 /opt/vaultWS/install/libexec/mod_alias.so
528682144 12299 /opt/vaultWS/install/libexec/mod_asis.so
3683990203 20506 /opt/vaultWS/install/libexec/mod_auth.so
3794250761 12321 /opt/vaultWS/install/libexec/
mod_auth_anon.so
1677672897 20504 /opt/vaultWS/install/libexec/
mod_auth_dbm.so
319691963 65627 /opt/vaultWS/install/libexec/
mod_autoindex.so
2798274003 20509 /opt/vaultWS/install/libexec/
mod_cern_meta.so
210476963 32807 /opt/vaultWS/install/libexec/mod_cgi.so
1024512365 20509 /opt/vaultWS/install/libexec/mod_define.so
3044190853 24605 /opt/vaultWS/install/libexec/mod_digest.so
1669345403 16404 /opt/vaultWS/install/libexec/mod_dir.so
2265636880 12312 /opt/vaultWS/install/libexec/mod_env.so
3842010989 24607 /opt/vaultWS/install/libexec/mod_expires.so
2069023418 12312 /opt/vaultWS/install/libexec/mod_headers.so
839220256 45112 /opt/vaultWS/install/libexec/mod_imap.so
3166651693 90215 /opt/vaultWS/install/libexec/mod_include.so
2843506832 40997 /opt/vaultWS/install/libexec/mod_info.so
29912906 188828 /opt/vaultWS/install/libexec/mod_jserv.so
515123627 45190 /opt/vaultWS/install/libexec/
mod_log_config.so
149726227 36921 /opt/vaultWS/install/libexec/mod_mime.so
1556557527 53334 /opt/vaultWS/install/libexec/
mod_mime_magic.so
585247284 69742 /opt/vaultWS/install/libexec/
mod_negotiation.so
1993355012 151761 /opt/vaultWS/install/libexec/
mod_rewrite.so
3452651814 20511 /opt/vaultWS/install/libexec/
mod_setenvif.so
2440657301 24605 /opt/vaultWS/install/libexec/mod_speling.so
1153359535 45085 /opt/vaultWS/install/libexec/mod_status.so
3542298083 49222 /opt/vaultWS/install/libexec/mod_tga.so
2614241357 20497 /opt/vaultWS/install/libexec/
mod_unique_id.so
515178063 20498 /opt/vaultWS/install/libexec/mod_userdir.so
462504356 28708 /opt/vaultWS/install/libexec/
mod_usertrack.so
3544776369 20506 /opt/vaultWS/install/libexec/
mod_vhost_alias.so
2780827864 1387 /etc/auth/system/files.fcdb/25.patches/
24052_PHSS.fcdb
4029446197 2693906 /opt/vaultWS/install/libexec/speedcard/
libssl.so
3847374939 35628 /opt/vaultTS/lib/libmm.a
1063204636 648 /opt/vaultTS/lib/libmm.la
2375588202 45194 /opt/vaultTS/lib/libmm.sl
2375588202 45194 /opt/vaultTS/lib/libmm.sl.11
2375588202 45194 /opt/vaultTS/lib/libmm.sl.11.23
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24052
Equivalent Patches: None
Patch Package Size: 8400 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25838
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25838.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25838. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25838.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25838.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25838.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25838.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
To allow the Apache server to utilize a
previously verified a client certificate
in a cached/reused SSL session after a
client/server disconnect without full
SSL session renegotiation, the container
(Server, Directory or Location) that is
requiring the certificate must include
+VVOptRenegotiate in the SSLOptions
directive of that container.
-----End of Document ID: PHSS_25838------------------------------------------
Document ID: PHSS_25689
Date Loaded: 20011206
Title: s700_800 11.11 N4000 41.46 firmware patch
Patch Name: PHSS_25689
Patch Description: s700_800 11.11 N4000 41.46 firmware patch
Creation Date: 01/10/01
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25689
Symptoms:
PHSS_25689:
The following features, fixes and enhancements appear in
server firmware revision 41.46:
- 1GB DIMMs have been produced with 2 different refresh
rates, both types are usable in L-Class and N-Class
servers however, the newer DIMMs that have a faster
refresh rate could not be used in the same DIMM pair as
the older DIMMs. Older PDC revisions also required DIMMs
with different refresh rates to be distributed in the
system like DIMMs of different sizes. PDC 41.46 allows
the DIMMs to mixed in the same DIMM pair and removes
distribution restrictions.
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.46 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.46
fixes these issues.
- Added support for PCI-PCI Bridge boot/swap/dump.
- Added support for Ultra 160 SCSI boot/swap/dump.
- Added FRU location to FRU id values.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25102:
The following features, fixes and enhancements appear in
server firmware revision 41.36:
1. Added 'sn' command to BCH Information menu. This
command displays the serial number stored in stable
storage.
2. Added 'scroll' command to BCH Service menu. This
command allows the display to scroll when using BCH
utilities.
3. Enabled use of PA8700 revision 2.3 CPU's.
4. Previous revisions of PDC prevented MPE systems from
properly handling a Transfer Of Control (TOC) when LDEV1
was not on an internal disk. PDC revision 41.36 properly
handles TOC's on an MPE system.
5. HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64 bit address.
6. The PDC revision number was displayed incorrectly,
it has been changed to display correctly.
7. The PCI reset time did not meet the minimum required
by the PCI specifications, it has been changed to meet
the specification.
8. Changed IODC to allow DDS4 tape drives to operate in
LVD mode on A5149A SCSI Card.
9. When a PCI I/O card is added or replaced Online, the
PCI slot is left in a state from which is not designed to
handle some types of errors. This may result in potential
data integrity issues. These OLAR operations should not be
performed on these systems until the PDC of the system is
upgraded to revision 41.36.
PHSS_22658:
The following features, fixes and enhancements appear in
server firmware revision 41.02:
1. Provide support Revision 3.1 processors
2. Provide OLA/R support
3. Provide support for new compiler toolsets
4. Serial Number command added to BCH information menu
5. Display CPU speed with BCH command "in pr"
6. Added MPE support
7. Corrected error in LMPC handler
8. Added support for RAID IODC
9. BCH command "CO DE" does not correctly default the
model string
Detailed Explanation:
1. Self explanatory
2. N4000 servers require PDC 40.49 and HP-UX 11.11 to
enable the high availability OLA/R feature. OLA/R
stands for OnLine Addition Removal and Replacement of
PCI cards. PDC revision 40.49 is not available for
field installation only PDC revision 41.02 is
available.
3. Older revisions of firmware did not support new
compiler toolsets. Added support for new toolsets.
4. Previous revisions of PDC did not allow Field Engineer
to view the serial number. Added the BCH command
"in sn" to allow Field Engineers to view the system
serial number.
5. Older revisions of firmaware did not check the speed
of the processor and defaulted to high speed, this
caused intermittant system errors. A line was added to
the BCH "in pr" command to display the speed of the
processor and add a warning message for slow speed
processors.
6. Older revisions of firmware did not support MPE. PDC
revision 41.02 is required to support MPE.
7. Under certain error conditions LPMC's caused HPMC's to
be generated. PDC revision 41.02 was changed to
properly handle the error conditions.
8. Self explanatory.
9. After changing the switches on the system board to
440Mhz from 550Mhz, the BCH command "CO DE" does not
change the model string to 9000/800/N4000-44.
The following issues have been addressed and corrected with
PDC firmware revision 40.25:
1. The speed detection section of PDC did not detect a
360/440 MHz processor when installed into a 550 MHz
system. This enabled the chance of installing a slow
speed processor in a high-speed system. PDC now
detects this condition, issues a warning message and
prevents HP-UX from booting.
2. PDC now supports boot via the A5158A (PCI 2x Fiber
Channel ) family of I/O cards.
The following issue has been addressed and corrected with
PDC firmware revision 40.15:
1. The firmware LPMC handler has been modified to properly
manage a LPMC as to not cause an HPMC in systems running
with multiple processors.
The following issues have been addressed and corrected with
PDC firmware revision 40.04:
1. PA8600 Processors are now supported with a 550 MHz
processor speed and a 133 MHz system bus speed.
2. Fiber channel boot is now supported.
3. New version of PCI bus adapter fully supported.
4. 1 GB DIMMS (2GB modules) now support memory up to 32GB.
5. Firmware Version displays single digit week (i.e. 40.4
rather than 40.04).
6. Added default for SERVICE MENU command PN, current and
previous product numbers are now displayed.
Defect Description:
PHSS_25689:
- See Symptoms.
PHSS_25102:
- See Symptoms.
PHSS_22658:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/N4000srvrflash
/usr/conf/N4000saveFW
/usr/conf/N4000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/N4000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/N4000saveFW:
Data Hdr A 00.01
/usr/conf/N4000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4026241493 42184 /usr/conf/N4000srvrflash
2404285325 32768 /usr/conf/N4000saveFW
989466718 2098432 /usr/conf/N4000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/N4000-36
9000/800/N4000-44
9000/800/N4000-55
9000/800/N4000-65
9000/800/N4000-75
Other Dependencies: None
Supersedes:
PHSS_22658 PHSS_25102
Equivalent Patches:
PHSS_25688:
s700: 11.00
s800: 11.00
Patch Package Size: 2170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25689
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25689.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25689. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25689.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25689.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25689.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25689.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/N4000-36
9000/800/N4000-44
9000/800/N4000-55
9000/800/N4000-65
9000/800/N4000-75
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25689------------------------------------------
Document ID: PHSS_25688
Date Loaded: 20011206
Title: s700_800 11.00 N4000 41.46 firmware patch
Patch Name: PHSS_25688
Patch Description: s700_800 11.00 N4000 41.46 firmware patch
Creation Date: 01/11/15
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_21679: PANIC HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25688
Symptoms:
PHSS_25688:
The following features, fixes and enhancements appear in
server firmware revision 41.46:
- 1GB DIMMs have been produced with 2 different refresh
rates, both types are usable in L-Class and N-Class
servers however, the newer DIMMs that have a faster
refresh rate could not be used in the same DIMM pair as
the older DIMMs. Older PDC revisions also required DIMMs
with different refresh rates to be distributed in the
system like DIMMs of different sizes. PDC 41.46 allows
the DIMMs to mixed in the same DIMM pair and removes
distribution restrictions.
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.46 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.46
fixes these issues.
- Added support for PCI-PCI Bridge boot/swap/dump.
- Added support for Ultra 160 SCSI boot/swap/dump.
- Added FRU location to FRU id values.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25101:
The following features, fixes and enhancements appear in
server firmware revision 41.36:
1. Added 'sn' command to BCH Information menu. This
command displays the serial number stored in stable
storage.
2. Added 'scroll' command to BCH Service menu. This
command allows the display to scroll when using BCH
utilities.
3. Enabled use of PA8700 revision 2.3 CPU's.
4. Previous revisions of PDC prevented MPE systems from
properly handling a Transfer Of Control (TOC) when LDEV1
was not on an internal disk. PDC revision 41.36 properly
handles TOC's on an MPE system.
5. HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64 bit address.
6. The PDC revision number was displayed incorrectly,
it has been changed to display correctly.
7. The PCI reset time did not meet the minimum required
by the PCI specifications, it has been changed to meet
the specification.
8. Changed IODC to allow DDS4 tape drives to operate in
LVD mode on A5149A SCSI Card.
9. When a PCI I/O card is added or replaced Online, the
PCI slot is left in a state from which is not designed to
handle some types of errors. This may result in potential
data integrity issues. These OLAR operations should not be
performed on these systems until the PDC of the system is
upgraded to revision 41.36.
PHSS_22657:
The following features, fixes and enhancements appear in
server firmware revision 41.02:
1. Provide support Revision 3.1 processors
2. Provide OLA/R support
3. Provide support for new compiler toolsets
4. Serial Number command added to BCH information menu
5. Display CPU speed with BCH command "in pr"
6. Added MPE support
7. Corrected error in LMPC handler
8. Added support for RAID IODC
9. BCH command "CO DE" does not correctly default the
model string
Detailed Explanation:
1. Self explanatory
2. N4000 servers require PDC 40.49 and HP-UX 11.11 to
enable the high availability OLA/R feature. OLA/R
stands for OnLine Addition Removal and Replacement of
PCI cards. PDC revision 40.49 is not available for
field installation only PDC revision 41.02 is
available.
3. Older revisions of firmware did not support new
compiler toolsets. Added support for new toolsets.
4. Previous revisions of PDC did not allow Field Engineer
to view the serial number. Added the BCH command
"in sn" to allow Field Engineers to view the system
serial number.
5. Older revisions of firmaware did not check the speed
of the processor and defaulted to high speed, this
caused intermittant system errors. A line was added to
the BCH "in pr" command to display the speed of the
processor and add a warning message for slow speed
processors.
6. Older revisions of firmware did not support MPE. PDC
revision 41.02 is required to support MPE.
7. Under certain error conditions LPMC's caused HPMC's to
be generated. PDC revision 41.02 was changed to
properly handle the error conditions.
8. Self explanatory.
9. After changing the switches on the system board to
440Mhz from 550Mhz, the BCH command "CO DE" does not
change the model string to 9000/800/N4000-44.
PHSS_21679:
PHSS_21679 installs PDC firmware revision 40.25 on N4000
systems. The following issues have been addressed and
corrected with PDC firmware revision 40.25:
1. The speed detection section of PDC did not detect a
360/440 MHz processor when installed into a 550 MHz
system. This enabled the chance of installing a slow
speed processor in a high-speed system. PDC now
detects this condition, issues a warning message and
prevents HP-UX from booting.
2. PDC now supports boot via the A5158A (PCI 2x Fiber
Channel ) family of I/O cards.
The following issue has been addressed and corrected with
PDC firmware revision 40.15:
1. The firmware LPMC handler has been modified to properly
manage a LPMC as to not cause an HPMC in systems running
with multiple processors.
The following issues have been addressed and corrected with
PDC firmware revision 40.04:
1. PA8600 Processors are now supported with a 550 MHz
processor speed and a 133 MHz system bus speed.
2. Fiber channel boot is now supported.
3. New version of PCI bus adapter fully supported.
4. 1 GB DIMMS (2GB modules) now support memory up to 32GB.
5. Firmware Version displays single digit week (i.e. 40.4
rather than 40.04).
6. Added default for SERVICE MENU command PN, current and
previous product numbers are now displayed.
Defect Description:
PHSS_25688:
- See Symptoms.
PHSS_25101:
- See Symptoms.
PHSS_22657:
- See Symptoms.
PHSS_21679:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/N4000srvrflash
/usr/conf/N4000saveFW
/usr/conf/N4000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/N4000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/N4000saveFW:
Data Hdr A 00.01
/usr/conf/N4000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
4179148837 42152 /usr/conf/N4000srvrflash
1691080368 28672 /usr/conf/N4000saveFW
989466718 2098432 /usr/conf/N4000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/N4000-36
9000/800/N4000-44
9000/800/N4000-55
9000/800/N4000-65
9000/800/N4000-75
Other Dependencies: None
Supersedes:
PHSS_21679 PHSS_22657 PHSS_25101
Equivalent Patches:
PHSS_25689:
s700: 11.11
s800: 11.11
Patch Package Size: 2170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25688
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25688.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25688. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25688.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25688.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25688.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25688.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/N4000-36
9000/800/N4000-44
9000/800/N4000-55
9000/800/N4000-65
9000/800/N4000-75
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25688------------------------------------------
Document ID: PHSS_25687
Date Loaded: 20011206
Title: s700_800 11.11 L3000 41.46 firmware patch
Patch Name: PHSS_25687
Patch Description: s700_800 11.11 L3000 41.46 firmware patch
Creation Date: 15/11/01
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25687
Symptoms:
PHSS_25687:
The following features, fixes and enhancements appear in
server firmware revision 41.46:
- 1GB DIMMs have been produced with 2 different refresh
rates, both types are usable in L-Class and N-Class
servers however, the newer DIMMs that have a faster
refresh rate could not be used in the same DIMM pair as
the older DIMMs. Older PDC revisions also required DIMMs
with different refresh rates to be distributed in the
system like DIMMs of different sizes. PDC 41.46 allows
the DIMMs to mixed in the same DIMM pair and removes
distribution restrictions.
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.46 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.46
fixes these issues.
- Added support for PCI-PCI Bridge boot/swap/dump.
- Added support for Ultra 160 SCSI boot/swap/dump.
- Added FRU location to FRU id values.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25104:
The following features, fixes and enhancements appear in
server firmware revision 41.36:
1. Added 'sn' command to BCH Information menu. This
command displays the serial number stored in stable
storage.
2. Added 'scroll' command to BCH Service menu. This
command allows the display to scroll when using BCH
utilities.
3. Enabled use of PA8700 revision 2.3 CPU's.
4. Previous revisions of PDC prevented MPE systems from
properly handling a Transfer Of Control (TOC) when LDEV1
was not on an internal disk. PDC revision 41.36 properly
handles TOC's on an MPE system.
5. HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64 bit address.
6. The PDC revision number was displayed incorrectly,
it has been changed to display correctly.
7. The PCI reset time did not meet the minimum required
by the PCI specifications, it has been changed to meet
the specification.
8. Changed IODC to allow DDS4 tape drives to operate in
LVD mode on A5149A SCSI Card.
9. When a PCI I/O card is added or replaced Online, the
PCI slot is left in a state from which is not designed to
handle some types of errors. This may result in potential
data integrity issues. These OLAR operations should not be
performed on these systems until the PDC of the system is
upgraded to revision 41.36.
Defect Description:
PHSS_25687:
- See Symptoms.
PHSS_25104:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/L3000srvrflash
/usr/conf/L3000saveFW
/usr/conf/L3000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/L3000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/L3000saveFW:
Data Hdr A 00.01
/usr/conf/L3000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4026241493 42184 /usr/conf/L3000srvrflash
2404285325 32768 /usr/conf/L3000saveFW
2337800702 2098432 /usr/conf/L3000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/L3000-5x
9000/800/L3000-6x
9000/800/L3000-7x
9000/800/L1500-5x
9000/800/L1500-6x
9000/800/L1500-7x
Other Dependencies: None
Supersedes:
PHSS_25104
Equivalent Patches:
PHSS_25686:
s700: 11.00
s800: 11.00
Patch Package Size: 2170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25687
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25687.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25687. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25687.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25687.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25687.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25687.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/L3000-5x
9000/800/L3000-6x
9000/800/L3000-7x
9000/800/L1500-5x
9000/800/L1500-6x
9000/800/L1500-7x
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25687------------------------------------------
Document ID: PHSS_25686
Date Loaded: 20011206
Title: s700_800 11.00 L3000 41.46 firmware patch
Patch Name: PHSS_25686
Patch Description: s700_800 11.00 L3000 41.46 firmware patch
Creation Date: 01/10/01
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25686
Symptoms:
PHSS_25686:
The following features, fixes and enhancements appear in
server firmware revision 41.46:
- 1GB DIMMs have been produced with 2 different refresh
rates, both types are usable in L-Class and N-Class
servers however, the newer DIMMs that have a faster
refresh rate could not be used in the same DIMM pair as
the older DIMMs. Older PDC revisions also required DIMMs
with different refresh rates to be distributed in the
system like DIMMs of different sizes. PDC 41.46 allows
the DIMMs to mixed in the same DIMM pair and removes
distribution restrictions.
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.46 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.46
fixes these issues.
123456789012345678901234567890123456789012345678901234567890
- Added support for PCI-PCI Bridge boot/swap/dump.
- Added support for Ultra 160 SCSI boot/swap/dump.
- Added FRU location to FRU id values.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25103:
The following features, fixes and enhancements appear in
server firmware revision 41.36:
1. Added 'sn' command to BCH Information menu. This
command displays the serial number stored in stable
storage.
2. Added 'scroll' command to BCH Service menu. This
command allows the display to scroll when using BCH
utilities.
3. Enabled use of PA8700 revision 2.3 CPU's.
4. Previous revisions of PDC prevented MPE systems from
properly handling a Transfer Of Control (TOC) when LDEV1
was not on an internal disk. PDC revision 41.36 properly
handles TOC's on an MPE system.
5. HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64 bit address.
6. The PDC revision number was displayed incorrectly,
it has been changed to display correctly.
7. The PCI reset time did not meet the minimum required
by the PCI specifications, it has been changed to meet
the specification.
8. Changed IODC to allow DDS4 tape drives to operate in
LVD mode on A5149A SCSI Card.
9. When a PCI I/O card is added or replaced Online, the
PCI slot is left in a state from which is not designed to
handle some types of errors. This may result in potential
data integrity issues. These OLAR operations should not be
performed on these systems until the PDC of the system is
upgraded to revision 41.36.
Defect Description:
PHSS_25686:
- See Symptoms.
PHSS_25103:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/L3000srvrflash
/usr/conf/L3000saveFW
/usr/conf/L3000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/L3000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/L3000saveFW:
Data Hdr A 00.01
/usr/conf/L3000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
4179148837 42152 /usr/conf/L3000srvrflash
1691080368 28672 /usr/conf/L3000saveFW
2337800702 2098432 /usr/conf/L3000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/L3000-5x
9000/800/L3000-6x
9000/800/L3000-7x
9000/800/L1500-5x
9000/800/L1500-6x
9000/800/L1500-7x
Other Dependencies: None
Supersedes:
PHSS_25103
Equivalent Patches:
PHSS_25687:
s700: 11.11
s800: 11.11
Patch Package Size: 2170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25686
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25686.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25686. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25686.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25686.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25686.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25686.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/L3000-5x
9000/800/L3000-6x
9000/800/L3000-7x
9000/800/L1500-5x
9000/800/L1500-6x
9000/800/L1500-7x
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25686------------------------------------------
Document ID: PHSS_25685
Date Loaded: 20011206
Title: s700_800 11.11 L1000/L2000 41.39 firmware patch
Patch Name: PHSS_25685
Patch Description: s700_800 11.11 L1000/L2000 41.39 firmware patch
Creation Date: 01/11/24
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25685
Symptoms:
PHSS_25685:
The following features, fixes and enhancements appear in
server firmware revision 41.39:
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.39 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.39
fixes these issues.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25105:
The following features, fixes and enhancements
appear in server firmware revision 4138:
1. - 1GB DIMMs have been produced with 2
different refresh rates, both types
are usable in L-Class and N-Class
servers however, the newer DIMMs
that have a faster refresh rate
could not be used in the same DIMM pair
as the older DIMMs. PDC 41.38 allows
the DIMMs to mixed in the same
DIMM pair.
2. - Added support for 2GB FC boot.
3. - Enabled slot 3 for internal RAID.
4. - Added support for internal RAID.
5. - Added support for PCI-PCI Bridge boot.
6. - Added support for Ultra 160 SCSI boot.
7. - Added 'SCROLL' command to BCH Service Menu.
8. - Added FRU location to FRU id values.
9. - An issue has been identified with the OLAR
functionality on L-Class
servers running HPUX 11.11 PDC revision
41.38 corrects the issue.
PHSS_23446:
Added support for model strings 9000/800/L1000-5X and
9000/800/L2000-5X to the firmware update utility.
PHSS_22656:
The following features, fixes and enhancements appear in
server firmware revision 40.48:
1. Provide support for L1000 and L2000 revision B models
(L1000B & L2000B)
2. Provide OLA/R support
3. PDC did not report overtemperature warning to HP-UX
4. GSP 'ps' command shows 1220W for power supply
5. Graphics board shows up as 'unknown' in PDC "in io"
command
6. PDC 'in io' identifies RAID card inappropriately
7. PDC revision now appears in HPMC tombstones
8. Hitting 'break' key on ASCII terminal while at PDC
causes IODC error
9. PDC 'ser pn' only displays first 5 digits of current
product number value
10. Increase the list of FRU_ID values recognized by PDC
11. PDC call PDC_PAT_COMPLET subfun 6 (get cabinet info)
fails repeatedly with -3
12. PDC must not be case sensative to FRU_ID values.
Detailed Explanation:
1. Self explanatory
2. L1000 and L2000 revision A models require PDC 40.48
and HP-UX 11.11 to enable the high availability OLA/R
feature. OLA/R stands for OnLine Addition Removal
and replacement of PCI cards.
3. Partial implementation of this fix appeared in PDC
40.14. When an overtemp shutdown occurred, PDC
notified HP-UX so it could perform an orderly
shutdown. However,
an overtemp chassis log was not created. With
PDC 40.48, a chassis log is created.
4. GSP 'ps' command reported the 930W L-Class power
supplies as "1220W". Fix is to report L-Class power
supplies as "Type 0".
5. A6150-60001 L-Class 2-D Graphics board reported as
'unknown' in PDC "in io" command. Fix is to report as
TBD.
6. Several PCI cards were not listed int the PCI
current lookup table and appeared as unknown when
using the BCH command in io. Added new PCI cards to
the lookup table.
7. The firmware revision did not appear in tombstone
printouts, added PDC rev in the tombstone output.
8. At PDC main menu, pressing the Break key on the web
console or power cycling the console caused an
unrecoverable IODC error. The PDC error handling
routines were changed to properly handle these
occurances.
9. When the BCH command ser pn was executed only the
first 5 characters of the product were displayed.
Changed the ser pn command to display 6 characters.
10. PDC 40.19 did not recognise FRU ID's of newer
revisions of replacement parts. PDC 40.48 now
correctly identifies all of the newer revisions of
replacement parts.
11. The PDC subroutine PDC_PAT_COMPLET subfun 6 did not
poll the power monitor or other PDH hardware properly
this caused EMS to report errors. PDC 40.48 firmware
correctly poll all PDH hardware so EMS will report
correct status.
12. When installing new system boards with a5191-67001 in
the PART NUMBER field of the FRU_ID the model string
changes from 9000/800/Lx00-44 to 9000/800/Lx00-36.
Changed PDC 40.48 to be insensitive to the case of
PART NUMBER entries.
The following issues have been addressed and corrected with
PDC firmware revision 40.26:
1. Server firmware revision 40.19 only recognizes
A5191-60001 as a valid part number entry within FRU_ID
of the system board. Any other value causes the
following symptoms common to 360MHz and 440MHz CPUS:
- Each CPU reports a 17D0 system alert during selftest.
17D0 indicates an "INVALID_SYS_BOARD_PART_NUM".
- The following server firmware warning is generated:
WARNING: Invalid processor clock chip setting.
The following symptoms are unique to servers with 440MHz
CPUs installed:
- Server firmware identifies 440MHz CPUs as 360MHz CPUs.
- The server model string will change from
9000/800/Lx000-44 9000/800/Lx000-36 (where x = 1 or 2).
NOTE: The server hardware is actually running 440MHz.
- The HP-UX clock gains approximately 15 minutes/hour.
2. An HPMC may occur as a result of performing a TOC
(Transfer Of Control).
The following issue has been addressed and corrected with
PDC firmware 40.19:
1. Systems with PDC revision 40.14 may experience a system
panic or system hang in response to the HP-UX command
'shutdown -h' .
The following features, fixes and enhancements appear in
PDC revision 40.14:
1. Increase maximum memory size for L1000 from 4GB to 8GB
2. Support 1GB DIMM (2GB memory module)
3. PDC did not report overtemperature warning to the OS
4. BCH recognizes only the abbreviated version of some
commands
5. New chassis code for invalid system board FRU_ID part
number
6. Hardware paths for devices below a PCI-to-PCI bridge
are displayed incorrectly
7. Firmware Version displays single digit week (i.e. 40.6
rather than 40.06)
8. BCH does not display help text for some commands
9. Change alert level for fatal (fails selftest/prevents
boot) DIMM loading alert from 8 to 15
10. Change alert level for deconfigured CPUs from 6 to 2 &
change problem detail from 3 to 8 (for iCOD)
11. New version of PCI bus adapter (Elroy 4.0) fully
supported.
12. The firmware LPMC handler has been modified to properly
manage a LPMC as to not cause an HPMC in systems running
with multiple processors.
Defect Description:
PHSS_25685:
- See Syptoms.
PHSS_25105:
- See Syptoms.
PHSS_23446:
- See Symptoms.
PHSS_22656:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/L1000srvrflash
/usr/conf/L1000saveFW
/usr/conf/L1000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/L1000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/L1000saveFW:
Data Hdr A 00.01
/usr/conf/L1000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4026241493 42184 /usr/conf/L1000srvrflash
2404285325 32768 /usr/conf/L1000saveFW
2373941246 2098432 /usr/conf/L1000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/L1000-36
9000/800/L1000-44
9000/800/L2000-36
9000/800/L2000-44
9000/800/L1000-5X
9000/800/L2000-5X
Other Dependencies: None
Supersedes:
PHSS_22656 PHSS_23446 PHSS_25105
Equivalent Patches:
PHSS_25684:
s700: 11.00
s800: 11.00
Patch Package Size: 2180 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25685
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25685.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25685. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25685.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25685.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25685.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25685.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/L1000-36
9000/800/L1000-44
9000/800/L2000-36
9000/800/L2000-44
9000/800/L1000-5X
9000/800/L2000-5X
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25685------------------------------------------
Document ID: PHSS_25684
Date Loaded: 20011206
Title: s700_800 11.00 L1000/L2000 41.39 firmware patch
Patch Name: PHSS_25684
Patch Description: s700_800 11.00 L1000/L2000 41.39 firmware patch
Creation Date: 01/11/25
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_21696: PANIC HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25684
Symptoms:
PHSS_25684:
The following features, fixes and enhancements appear in
server firmware revision 41.39:
- Earlier versions of PDC prevented online diagnostics
for reading PIM data. PDC revision 41.39 corrects this
problem.
- previous versions of PDC were unable to dump using the
A6795A 2Gb Fibre Channel HBA on all platforms, unable to
to dump to disks on Point to Point Fabric with McData
switches and unable to boot/dump with Brocade 3800 2GB
Switches with A6795A cards installed. PDC revision 41.39
fixes these issues.
- HPMC chassis codes reported an incorrect PDC base
address. When the chassis code is sent for HPMC MONARCH
SELECTED it will now report the full 64-bit address.
- Changed IODC to allow DDS4 tape drives to operate in LVD
mode on the A5149A SCSI Card.
-Improved single memory error handling.
PHSS_25106:
The following features, fixes and enhancements
appear in server firmware revision 41.38:
1. - 1GB DIMMs have been produced with
2 different refresh rates, both types
are usable in L-Class and N-Class servers
however, the newer DIMMs
that have a faster refresh rate could
not be used in the same DIMM pair
as the older DIMMs. PDC 41.38 allows
the DIMMs to mixed in the same
DIMM pair.
2. - Added support for 2GB FC boot/swap/dump.
3. - Enabled slot 3 for internal RAID.
4. - Added support for internal RAID.
5. - Added support for PCI-PCI Bridge boot/swap/dump.
6. - Added support for Ultra 160 SCSI boot/swap/dump.
7. - Added 'SCROLL' command to BCH Service Menu.
8. - Added FRU location to FRU id values.
9. - An issue has been identified with the
OLAR functionality on L-Class
servers running HPUX 11.11 PDC
revision 41.38 corrects the issue.
PHSS_23447:
Added support for model strings 9000/800/L1000-5X and
9000/800/L2000-5X to the firmware update utility.
PHSS_22655:
The following features, fixes and enhancements appear in
server firmware revision 40.48:
1. Provide support for L1000 and L2000 revision B models
(L1000B & L2000B)
2. Provide OLA/R support
3. PDC did not report overtemperature warning to HP-UX
4. GSP 'ps' command shows 1220W for power supply
5. Graphics board shows up as 'unknown' in PDC "in io"
command
6. PDC 'in io' identifies RAID card inappropriately
7. PDC revision now appears in HPMC tombstones
8. Hitting 'break' key on ASCII terminal while at PDC
causes IODC error
9. PDC 'ser pn' only displays first 5 digits of current
product number value
10. Increase the list of FRU_ID values recognized by PDC
11. PDC call PDC_PAT_COMPLET subfun 6 (get cabinet info)
fails repeatedly with -3
12. PDC must not be case sensative to FRU_ID values.
Detailed Explanation:
1. Self explanatory
2. L1000 and L2000 revision A models require PDC 40.48
and HP-UX 11.11 to enable the high availability OLA/R
feature. OLA/R stands for OnLine Addition Removal
and replacement of PCI cards.
3. Partial implementation of this fix appeared in PDC
40.14. When an overtemp shutdown occurred, PDC
notified HP-UX so it could perform an orderly
shutdown. However,
an overtemp chassis log was not created. With
PDC 40.48, a chassis log is created.
4. GSP 'ps' command reported the 930W L-Class power
supplies as "1220W". Fix is to report L-Class power
supplies as "Type 0".
5. A6150-60001 L-Class 2-D Graphics board reported as
'unknown' in PDC "in io" command. Fix is to report as
TBD.
6. Several PCI cards were not listed int the PCI
current lookup table and appeared as unknown when
using the BCH command in io. Added new PCI cards to
the lookup table.
7. The firmware revision did not appear in tombstone
printouts, added PDC rev in the tombstone output.
8. At PDC main menu, pressing the Break key on the web
console or power cycling the console caused an
unrecoverable IODC error. The PDC error handling
routines were changed to properly handle these
occurances.
9. When the BCH command ser pn was executed only the
first 5 characters of the product were displayed.
Changed the ser pn command to display 6 characters.
10. PDC 40.19 did not recognise FRU ID's of newer
revisions of replacement parts. PDC 40.48 now
correctly identifies all of the newer revisions of
replacement parts.
11. The PDC subroutine PDC_PAT_COMPLET subfun 6 did not
poll the power monitor or other PDH hardware properly
this caused EMS to report errors. PDC 40.48 firmware
correctly poll all PDH hardware so EMS will report
correct status.
12. When installing new system boards with a5191-67001 in
the PART NUMBER field of the FRU_ID the model string
changes from 9000/800/Lx00-44 to 9000/800/Lx00-36.
Changed PDC 40.48 to be insensitive to the case of
PART NUMBER entries.
PHSS_21696:
PHSS_21696 installs PDC firmware revision 40.26 on L1000
and L2000 systems.The following issues have been addressed
and corrected with PDC firmware revision 40.26:
1. Server firmware revision 40.19 only recognizes
A5191-60001 as a valid part number entry within FRU_ID
of the system board. Any other value causes the
following symptoms common to 360MHz and 440MHz CPUS:
- Each CPU reports a 17D0 system alert during selftest.
17D0 indicates an "INVALID_SYS_BOARD_PART_NUM".
- The following server firmware warning is generated:
WARNING: Invalid processor clock chip setting.
The following symptoms are unique to servers with 440MHz
CPUs installed:
- Server firmware identifies 440MHz CPUs as 360MHz CPUs.
- The server model string will change from
9000/800/Lx000-44 9000/800/Lx000-36 (where x = 1 or 2).
NOTE: The server hardware is actually running 440MHz.
- The HP-UX clock gains approximately 15 minutes/hour.
2. An HPMC may occur as a result of performing a TOC
(Transfer Of Control).
The following issue has been addressed and corrected with
PDC firmware 40.19:
1. Systems with PDC revision 40.14 may experience a system
panic or system hang in response to the HP-UX command
'shutdown -h' .
The following features, fixes and enhancements appear in
PDC revision 40.14:
1. Increase maximum memory size for L1000 from 4GB to 8GB
2. Support 1GB DIMM (2GB memory module)
3. PDC did not report overtemperature warning to the OS
4. BCH recognizes only the abbreviated version of some
commands
5. New chassis code for invalid system board FRU_ID part
number
6. Hardware paths for devices below a PCI-to-PCI bridge
are displayed incorrectly
7. Firmware Version displays single digit week (i.e. 40.6
rather than 40.06)
8. BCH does not display help text for some commands
9. Change alert level for fatal (fails selftest/prevents
boot) DIMM loading alert from 8 to 15
10. Change alert level for deconfigured CPUs from 6 to 2 &
change problem detail from 3 to 8 (for iCOD)
11. New version of PCI bus adapter (Elroy 4.0) fully
supported.
12. The firmware LPMC handler has been modified to properly
manage a LPMC as to not cause an HPMC in systems running
with multiple processors.
Defect Description:
PHSS_25684:
- See Symptoms.
PHSS_25106:
- See Symptoms.
PHSS_23447:
- See Symptoms.
PHSS_22655:
- See Symptoms.
PHSS_21696:
- See Symptoms.
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/L1000srvrflash
/usr/conf/L1000saveFW
/usr/conf/L1000fw.wrap
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/L1000srvrflash:
Server firmware reflash utility version 1.0 for N an
d L Class Servers
/usr/conf/L1000saveFW:
Data Hdr A 00.01
/usr/conf/L1000fw.wrap:
Data Hdr A.00.01
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
4179148837 42152 /usr/conf/L1000srvrflash
1691080368 28672 /usr/conf/L1000saveFW
2373941246 2098432 /usr/conf/L1000fw.wrap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800/L1000-36
9000/800/L1000-44
9000/800/L2000-36
9000/800/L2000-44
9000/800/L1000-5X
9000/800/L2000-5X
Other Dependencies: None
Supersedes:
PHSS_21696 PHSS_22655 PHSS_23447 PHSS_25106
Equivalent Patches:
PHSS_25685:
s700: 11.11
s800: 11.11
Patch Package Size: 2170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25684
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25684.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25684. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25684.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25684.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25684.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25684.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch will only install and update the firmware on
these systems:
9000/800/L1000-36
9000/800/L1000-44
9000/800/L2000-36
9000/800/L2000-44
9000/800/L1000-5X
9000/800/L2000-5X
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by touching the file '/tmp/force_patch_install'
before installing the patch. This may be useful when
creating a 'golden' archive image for Ignite-UX that may be
used on several different hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
If the SUPPORT-TOOLS or Online Diagnostics software is
installed, the existing firmware will be saved during the
installation of the patch. In this case, if the patch is
removed, the original firmware will be restored. If neither
the SUPPORT-TOOLS nor Online Diagnostics software is
installed, the existing firmware will not be saved during
the installation of the patch. In this case, if the patch
is removed the original firmware will not be restored and
the firmware installed by the patch will remain loaded
after the patch is removed.
The firmware update is accomplished by temporarily modifying
the autoboot file on the primary boot disk. To identify the
disk, patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
-----End of Document ID: PHSS_25684------------------------------------------
Document ID: PHSS_25646
Date Loaded: 20011206
Title: s700_800 11.X OpenMail B.06.00 December 01 Periodic Patch
Patch Name: PHSS_25646
Patch Description: s700_800 11.X OpenMail B.06.00 December 01 Periodic Patch
Creation Date: 01/11/22
Post Date: 01/12/06
Hardware Platforms - OS Releases:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
Products:
OpenMail B.06.00
Filesets:
OpenMail.OM-ADM,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-AMECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-AMEICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-APPL,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-BB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CCMOB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CORE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-DESK,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-DSYNC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ENGCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ENGICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FINCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FINICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FRECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FREICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-GERCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-GERICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-IMAP4,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ITACAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ITAICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-LC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-LDAP,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-MAN,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NOTES,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PMOVER,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-POP3,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PTBCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PTBICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-RC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SMS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SPACAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SPAICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SWECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SWEICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-UNIX,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-X400,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25646
Symptoms:
PHSS_25646:
CR: JAGad83534 SR: 8606214343
If an auto-redirect is enabled for a users inbox, then all
other auto- actions are excluded from execution for that
mailbox.
CR: JAGad83915 SR: 8606214723
If, when creating an auto-forward rule using the PAW-client
the user deletes the auto-forward covering text, local
delivery fails to forward the message.
CR: JAGad83932 SR: 8606214740
B.06 and B.07
This concerns the UAL Checklist command, when the flag is
set to search the directory on the internet-addr (167)
attribute.
When more than one match is found, the command does not
return the entries found as alternatives. This is unlike
UAL Checkname, which does.
This affects the OMGUI, for example. When entering the
duplicate internet address into a DL, the behaviour varies
depending on whether the Auto Name Checking option is on.
If on, Checkname is used, and you see the X400 attributes
of the entries. If off, you get an error when the message
is Mailed. When you click on the name in error, you get a
message that no alternatives can be displayed, or else you
get an empty box that is supposed to show the alternatives.
CR: JAGad84893 SR: 8606215716
If a message that contains an ORN with a DDVn field greater
than the maximum 128 bytes, the X400 outgoing gateway
correctly rejects this message, and will generate a
non-delivery if appropriate.
If the message is a return of contents (the normal type of
non-delivery), then all subsequent messages that are not
return of contents will be rejected by the gateway. An
error 6019 appears in the omshowlog output for each
rejected message.
After a number of the 6019 errors (200 at most), the
gateway will abort, with log output showing 'too many
transaction files open'.
CR: JAGad84922 SR: 8606215745
If no auto-reply text is provided for an auto-reply rule,
then local delivery fails to send the auto-reply message.
CR: JAGad87649 SR: 8606218500
Using the Outlook client delegate permissions cannot be set
if the delegate has the Common Name (CN) attribute set. An
error is displayed in the Outlook interface.
CR: JAGad88671 SR: 8606219531
When the X400 outgoing gateway processes a message with a
non-textual content item, and with GENERATE_FTPBP=TRUE in
the ~sys/madmd.cfg file, x400.hpx.out leaks approximately
4Kbytes of memory on the message.
The workaround is to stop and start the X400 gateway
periodically, before the process fails with insufficient
memory.
CR: JAGad90057 SR: 8606220921
An Internet Ack which contains a NULL character will cause
unix.in to fail.
CR: JAGad91276 SR: 8606222161
omupdtis does not return an error result when interrupted.
CR: JAGad93282 SR: 8606224187
The unix.out gateway, when processing tnef routed messages,
should generate IDs for Mapi Named Properties, in the range
8000-FFFE. The gateway increments the ID each time that a
named property is processed, generating IDs like 80000003,
8001000b, 80020003....
If the gateway runs for some time, the Named Property IDs
become undefined, once FFFE has been reached.
CR: JAGad94888 SR: 8606225815
The OpenMail daemons omvvrelay, ompop3, omimap and omportal
(B.06.00) cannot be started or stopped manually by root in
a VirtualVault 4.5 environment, due to root not having
sufficient authorisation.
PHSS_25462:
CR: JAGad88889 SR: 8606219749
IMAP: rereading messages with many attachments can result
in raw base64 encoded information being displayed.
CR: JAGad90490 SR: 8606221356
Reading Non-Delivery Notifications for a non-english user
(e.g. German) using an IMAP cleint (e.g. Netscape
Navigator) gives text when the accented characters (e.g.
umlaute) are displayed incorrectly.
PHSS_24874:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
To:
_//org/co/admd/prmd////RFC-822/ppinetia.coma.b.c
CR: JAGad67601 SR: 8606198411
Message with a large distribution list (thousands of
recipients) can take a long, long time to pass through the
X.400 gateway (from OpenMail to X.400).
CR: JAGad68810 SR: 8606199624
omshowcda -d <dir_name> displays the mask used to extract
directory entries. The format of this mask changed with GR6
PP-Mar. It used to be:
S/G/I
and now it is:
S=/G=/I=
This will also occur for other directory related commands
that display attribute masks.
CR: JAGad69543 SR: 8606200362
Occasionally some message body parts, which require base 64
mime encoding, cause the item.browse binary to perform a
segmentation violation. This occurs when a user attempts to
read the message from the intray or folder area using an
IMAP client (Netscape communicator).
CR: JAGad70640 SR: 8606201464
Some scripts included in the OM-APPL component assume that
the 'cut' command is located in /usr/bin. In RedHat 7.1,
'cut' is located in /bin. The scripts affected are
omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl,
omdelapppdln, omshowapp, omshowapppdl and omshowapppdln.
CR: JAGad71090 SR: 8606201916
Web Client 6.0 may, under certain cirumstances, display the
incorrect item count when listing items in the tray areas
or the folder areas.
CR: JAGad73144 SR: 8606203966
Requesting virtual licences from other machines using GR6
Dec 2000 PP fails in some cases, and the license server may
abort. The failure happens when there is a decaying license
in the shadow file. omaudlic on the other machine shows
that the licences have been granted. The failure depends on
the order of entries within the shadow file, and therefore
appears to be intermittent. It does not seem to be related
to any one platform.
CR: JAGad74715 SR: 8606205540
This applies to B.06.00.00 and B.07.00.00
Use of ldapmodify to replace the mhsORAddress or omAddress
attributes does not work if attempting to replace existing
individual attributes, other than S, S-TX, G and G-TX.
For instance, if the entry for S=user111 has an OU1
configured, then
# ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v
dn: cn=user111, o=OpenMail
changetype: modify
replace: mhsORAddresses
mhsORAddresses: S=user111/ou1=japan3
gives
ldap_modify: Operations error
ldap_modify: additional info: [OM 16092] An attribute has
multiple values, but is notconfigured as multi-value.
Parameter : Directory Entry Modifier
Attribute : OU1Max allowed size : 32
Required syntax : PRINTABLE-STRING
The error can also be seen on the server side, on the
omslapd debug output.
The recommended method is to use ldapmodify to modify the
individual attributes explicitly.
For instance, the input to ldapmodify would be
dn:...
changetype: modify
replace: 5
5: <new_OU1_value>
The internal names of the OU<n> attributes are used as they
are not mapped by default in the ~openmail/sys/ldap.attribs
file. Mappings could of course be added to this file, so
that more meaningful tags could be used in ldapmodify.
CR: JAGad75038 SR: 8606205863
Directory entries added using omaddent that contain
OCTET-STRING attributes have octets with certain values
stripped out. ommodent shows the same problem.
The FREEBUSY directory attributes used by Outlook FreeBusy
lookup are examples of OCTET-STRING data. A situation where
the FREEBUSY attributes may become incorrect is when
omdiropt is run on the FREEBUSY directory. This is because
omdiropt uses omaddent.
Octet 014 (14 decimal) is one value that gets stripped.
There may be some other values.
CR: JAGad75975 SR: 8606206802
The problem is with the way that sendmail converts the
address and OpenMail subsequently parses it.
If an entry has the format ", then sendmail quotes it and
adds an extra to the " sequence.
So us"er <user.local>, goes to "us\"er" <user/local>,
Openmail then splits up the address list using commans as
the separator. If a separator is in a quote, it ignores it.
In the above example, the quote after the \ is taken to be
a closing quote. This means that things get out of sync, as
the last quote is taken to be an opening, rather than
closing, quote and the address list becomes mangled.
In addition, the mangled address list may now contain
entries in excess of 1024 characters This can cause a fatal
error.
CR: JAGad79081 SR: 8606209895
Certain printable chars may be used in the components, e.g.
Surname, of OM Personal Names, but should be represented by
special characters on input (see man page omattribs). Such
a char is that 'space' should be input as '_' to allow for
Surnames like "Van Gogh".
IMAP makes no allowance for this mapping, and so fails to
login because the username as input does not exist as an OM
user.
PHSS_24095:
CR: JAGad40563 SR: 8606171299
The web clients do not work with HTTPS and the Apache web
server.
When the user tries to signon they are presented with the
following message:
Bad Request
Your browser sent a request that this server could not
understand.
Reason: You're speaking plain HTTP to an SSL-enabled server
port.
CR: JAGad44030 SR: 8606174784
Openmail does not have a converter from unicode to IA5, but
it does have one from unicode to ISO8859_1.
When the item browser is used to display a text message
using the default format, it has no problem in displaying
the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the
configuration file.
However, if OM_DEF_USER_CHAR is set to IA5, then the item
browser isn't able to do the conversion and reports an
error. As the error reported in the log file was that a
character set conversion between MIME-UTF8 and IA5 was
failing, then this is probably the case.
The second problem is the way that the item browser
displays the message in MIME format.
Adding the mapping of UTF-8 to UTF8 in the mime.cs file
means that the character set for the message is now UTF8
which is recognised by OpenMail and the message is
correctly displayed on most clients. However, for Netscape
Messenger, which uses the item browser MIME option, there
is a problem.
The steering file ~sys/brwmime.str specified that generally
character sets should be converted to ISO8859_1 unless
otherwise specified. This means that the item browser
attempts a conversion from UTF8 to ISO8859_1 and fails.
It should be noted that UNICODE is not generally supported
on OpenMail when messages are in the MIME format.
CR: JAGad45881 SR: 8606176644
Omcontain aborts with a segmentation violation on LINUX,
when trying to delete a message attachment located in the
user's intray and results in the message attachment
remaining in the intray.
CR: JAGad46439 SR: 8606177205
For an OpenMail server that is configured to support
Czech...
Messages being sent from X400 with 1992 standard General
Text: context-specific 0 (23 octets):
GeneralString (21 octets):
1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32
. ( B . . - B . ~ 1 1 1 1 . . 2 2 2
are not correctly converted by the X400 In Mapper. They
should be converted to files of type 1736 with character
set T61BASE, and the data of the file should be consistent
with this.
CR: JAGad47890 SR: 8606178664
Some vir*ses can be flagged as being clean if the machine
on which they were scanned had been incorrectly configured
for scanning.
CR: JAGad50818 SR: 8606181602
If a message is sent from a user who has an INTERNET_ADDR
defined, to another machine, e.g. via the SMINTFC gateway,
replies to that message do not get returned via the same
route - they always get returned via the INTERNET gateway.
This occurs when the receiving server does does not have
the user's INTERNET_ADDR defined in the directory, and when
the sending server is version GR7
CR: JAGad55411 SR: 8606186206
When shutting down the Remote Client Interface a
segmentation violation is occuring in the Notification
Monitor occasionally because of a buffer over-run or
under-run.
CR: JAGad56484 SR: 8606187277
The OpenMail delegate implementation does not include an
equivalent for Exchange's "Delegate can see my private
items" option (disabled by default in Exchange). Hence when
forwarding Meeting Requests no distinction is made between
Private items and others.
CR: JAGad56620 SR: 8606187413
Message delivery rulesets are not working with empty
subjects.
CR: JAGad57754 SR: 8606188546
omredirtcp logs errors "getsockname: Bad file number" when
no error has occurred.
CR: JAGad58840 SR: 8606189626
MAPI addressbook download fails when trying to download a
directory whose first entry is a large entry such as a pdl
because a buffer overflow occurs.
CR: JAGad64229 SR: 8606195023
Some of the OpenMail patch install scripts may use return
codes which are invalid in Software Distibutor (SD). In
addition, symbolic names such as $SUCCESS, $FAILURE and
$WARNING should be instead of 0, 1 and 2.
Some of the messages do not follow the conventions, with a
word such as ERROR in column 1 of the first line only, and
the text indented to column 10.
CR: JAGad64671 SR: 8606195467
When performing searches of large message stores if the
ual.remote associated with the in.imap41d terminates due to
inactivity or is deliberately killed then in.imap41d goes
into a spin. When using TOP or glance the in.imap41d
processes appear to be consuming a lot of CPU activity,
however, they will not impact on system performance
because the kernel will have assigned them a low priority.
PHSS_24029:
CR: JAGad48440 SR: 8606179216
8-bit text (e.g. German national chars) is displayed as
7-bit by IMAP clients, Netscape and Outlook Express.
CR: JAGad57988 SR: 8606188772
Messages containing ARPA Message Headers (e.g. Subject:)
with 8-bit text (e.g. German national chars) are displayed
in MIME source format by Netscape IMAP clients. This occurs
on the 2nd. and subsequent re- browse of the message. The
initial browse of the message is displayed correctly.
CR: JAGad63387 SR: 8606194177
A coding defect while processing MIME data sometimes causes
a fatal error within the item.browse binary.
On the Netscape Client the user is presented with the
message:
"The current command did not succeed. The mail server
responded: Some of the requested messages no longer exist."
PHSS_23726:
CR: JAGad53837 SR: 8606184631
Large attachments (>30K) in forwarded messages are not
visible to Netscape IMAP client after moving from intray to
another folder.
PHSS_23343:
CR: JAGab33574 SR: 1653231704
OpenMail for Solaris's service router will abort if a
distribution list contains a blank name in it.
The following error is logged and can be seen using
omshowlog :
SERIOUS ERROR Service Router(Service Router)
09.04.97 [OM 10250] Process about to terminate due to
error. Signal (Segmentation Violation) trapped by process
4613; code = 0. Procedure trace follows:
< - da_GetAttribDefn
-> nm_GetFieldMemPtr
< - nm_GetFieldMemPtr
-> da_GetAttribDefn
-> da_GetMemAttribDefn
< - da_GetAttribDefn
-> nm_GetFieldMemPtr
< - nm_GetFieldMemPtr
-> da_GetAttribDefn
CR: JAGab39939 SR: 8606100957
Omfmtent -u creates output that is corrupted. This occures
when an attribute name is specified and the attribute value
is not. The format of the output is incorrect because it
lists the attribute name but assigns no value to it making
the output unusable in scripts.
ie:
Input to omfmtent :
s=kessler/i=c/g=richard/q=/ou1=hdqt
Output of omfmtent :
1=kessler/3=c/2=richard/4/5=hdqt
As you can see by the above example, the output from the
omfmtent command is missing an "=" after the 4.
CR: JAGab68963 SR: 8606102906
The new server feature of REPEAT REMINDERS in the OMGUI and
MOB GUI do not stop sending out reminders after the Expiry
date.
CR: JAGad24268 SR: 8606154951
omupdtis and associated commands sometimes report illegal
message store container references e.g.
~/sys/1000035/0000001:3
CR: JAGad31664 SR: 8606162348
Can't reply in OMGUI and ccMail to messages from internet
whose address has comments.
CR: JAGad35090 SR: 8606165799
If 2 OpenMail users have the same name (but different
mailnodes) Single User Restore sometimes selects the wrong
message store to be restored.
CR: JAGad38822 SR: 8606169547
The Content Disposition and Content ID fields of a message
become corrupt when replying/forwarding using the Ccmail 6
client.
CR: JAGad41463 SR: 8606172203
The Application Link Layer component does not pass all the
basic acceptance tests on Solaris.
CR: JAGad41471 SR: 8606172211
The UAL sometimes aborts on Redhat 7.0 systems when using
the directory relay service, with the following in the
OpenMail log:
SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57
[OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 28277;
code = 0. Procedure trace follows:
-> pc_recv_logical_block
<- pc_recv_logical_block
<- pc_recvmessage
-> ual_SendMessage
<- ual_SendMessage
-> ual_RecvReply
-> ual_GetFreeBusyTime
-> ual_ConvORNCheck
-> ual_ConvertORN
-> ual_GetUserCharSet
<- ual_GetUserCharSet
<- ual_ConvertORN
<- ual_ConvORNCheck
-> ual_GetUsersHost
-> nm_ParseORN
<- nm_ParseORN
User Name: UAL TestUser2 / Test, UAL
Pid of logging process: 28277
CR: JAGad41637 SR: 8606172377
Wrong user config file being used when accessing a delegate
mailbox.
CR: JAGad42631 SR: 8606173373
Openmail GR6 experiencing OM 1209 whenever omscan is run.
omscan logs errors in the log file which are nothing to
worry about and are normal behaviour. These errors should
be correctly trapped to avoid worrying administrators that
they may be a problem
CR: JAGad43052 SR: 8606173797
When a message with accented characters in the subject is
copied across message stores using Netscape messenger, the
subject of the message has the MIME character set specifier
in it when viewed using omcontain, OMGUI, Outlook. The
subject appears OK when using Netscape Messenger.
CR: JAGad43053 SR: 8606173798
When a message is copied from one message store to another
using Netscape Message, and an accented character exists in
it's content, then the message content file is corrupted.
However, the content of the message remains OK in the IMAP
index file. This means that the content can be viewed using
Netscape Message, but not when using OMGUI or Outlook.
CR: JAGad44810 SR: 8606175570
If a user has an address attribute with a backslash in,
then when the user's address is validated (checked) the
address attributes are displayed within the freeform field
(to:). If a backslash is present it prevents the message
being sent and displays the message "the user name is not
routable"
CR: JAGad45449 SR: 8606176209
Outlook OFS: Item created offline and synced, and then
modified offline but synced online causes a duplicate to be
created.
CR: JAGad45880 SR: 8606176642
The IMAP/item.browse aborts with a segmentation violation
on LINUX, when trying to encode an html attachment into
"Quoted-Printable" format.
CR: JAGad46896 SR: 8606177664
The OpenMail Internet gateway rejects multipart/signed
messages if one of its composite, multipart or message,
part's boundary-end markers is missing.
CR: JAGad48103 SR: 8606178878
If omprepsur is not able to salvage certain files, omdosur
is supposed to substitute some dummy containers instead and
then continue to create a valid omcpoutu archive. Infact,
omdosur was aborting straight after processing the missing
container and so was creating a corrupt omcpoutu archive.
CR: JAGad49581 SR: 8606180360
The original fix for JAGac29290 was missing two files:
i4target_ux10 and i4target_ux11. They should be included.
JAGac29290 added the ability to run OpenMail on systems
where the LSSERV component was not installed.
PHSS_23082:
CR: JAGad41842 SR: 8606172582
Outlook OFS: The UAL_GETSYNC extracts T.61 text content
files without performing any character set conversion on
them.
This affects Czech text that is synchronized and will also
affect Japanese, Korean and Chinese text.
CR: JAGad42033 SR: 8606172773
Itemed moved from Inbox whilst offline gets sync'ed twice:
Once when the MOVE is synced, and then again when the
folder is next synced.
CR: JAGad42115 SR: 8606172855
When 2 Outlook clients are connected to the same user
mailbox (eg. delegate and principal) there are occasions
when Calendar data is changed offline and the appointment
date emboldening is not updated for the online user after a
sync.
CR: JAGad42645 SR: 8606173387
They are occasions when the synchronization a folder
(typically the Inbox) will not pick up all of the newly
added messages.
This is most likely to occur on Inboxes with more than 32
items that have had items added and deleted since the last
synchronization. The items not sync'ed to the local Inbox
will be in a block starting with one delivered immediately
after the last sync.
CR: JAGad42878 SR: 8606173621
Message that is deleted completely on the server and
modified offline causes a sync. error when the folder is
next synced.
CR: JAGad44420 SR: 8606175176
Using Outlook OFS can cause spurious WARNINGs to be
reported in the OpenMail error log. Happens most frequently
when mailing messages that get saved to the Drafts folder
during message construction.
The warnings of the following type:
WARNING Remote Client (U/I Access )
01.04.01 11:11:35 [OM.UI 578] The Direct Reference supplied
is invalid User Name: JONATHAN GEORGE / HP-Pinewood, om1
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ct_ofs_read
<- ct_ofs_read
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ual_ListChangeLogAdd
-> ual_ResolveDirectRef
-> ct_FindDITEntryByRef
-> ct_DecodeDirectRef
<- ct_DecodeDirectRef
-> ct_FindDITEntry
<- ct_FindDITEntry
<- ct_FindDITEntryByRef
PHSS_22996:
CR: JAGad29260 SR: 8606159934
If a message coming in through the unix gateway, destined
for a Notes user, contains an empty From address in the
header section (HFrom: <>), omrouter non-delivers this
message and the following error messages are logged:
08/29/2000 12:39:11 PM OMRTR-GW1210: Failed to add entry
to text list.Entry : *NumCCRecips*Bad*
08/29/2000 12:39:11 PM OMRTR-GW2190: Sending Non-Delivery
Notification to ...
08/29/2000 12:39:11 PM OMRTR-GW2191: Successfully sent
Non-Delivery
PHSS_22991:
CR: JAGad42968 SR: 8606173711
It is possible using Outlook with a MAPI connection to
OpenMail to send a message with an internet address
containing 8-bit characters in the domain name.
The outgoing Internet Gateway discards these domain names,
causing an attempt to be made to deliver the message to a
recipient with the same address but no domain name.
This is not correct: if an address is invalid, message
delivery should not be attempted to a partial address in
this manner, as there are potential privacy issues.
PHSS_22700:
CR: JAGad21983 SR: 8606152653
The UXO_CHECK_TYPES_OF_DDA general.cfg configuration option
can be used to specify synonyms for the RFC-822 domain
defined attrubute type (DDT1).
However, for addresses which are NOT routed through the
internet gateway, those using DDT1=RFC-822 are treated
differently to those which use DDT1=<synonym for RFC-822>
For instance, assuming :
There is a route for "unix" through the internet gateway.
There is a route for "if" through the SendMail interface.
general.cfg contains these settings :
UXI_NAME_MAPPING=TRUE
UXO_NAME_MAPPING=TRUE
BRW_NAME_MAPPING=TRUE
UXO_CHECK_TYPES_OF_DDA=a,RFC-822,HPMEXT1,HPMEXT2,HPMEXT3,HP
EXT4
Then, the addresses are :
As entered Displayed in internet mailbox
a/unix(RFC-822|rm.cow) rm.cow
b/unix(a|rm.cow) rm.cow
c/if (RFC-822|rm.cow) rm.cow
d/if (a|rm.cow) d/if////////a/r#a#m#f#cowm.cow
There are arguments both ways for treating the addresses
routed through "if", however, the treatment should be
consistent.
CR: JAGad25146 SR: 8606155833
No way to specify aliases when creating many users with
'omaddu -bulk'.
CR: JAGad25316 SR: 8606156005
On an Ensim Linux machine.
When child processes terminate, they do not disappear
completely as expected, instead they become zombie
processes. These zombie processes are marked with <defunct>
when looking at process id information on a system.
This in turn can cause some processes, such as advmail.sckd
to hang using large amounts of system resource.
This will also cause problems when the system runs out of
available process ids because they are all tied up by
zombie processes.
CR: JAGad26547 SR: 8606157213
Subject and body of message generated for Japanese users
exceeding their message store limit should be in Japanese.
CR: JAGad27572 SR: 8606158242
According to RFC-1741 binhex file attachments should not be
encoded for transport. Item browser by default uses base64
encoding on binary files, with the result that the Eudora
client is unable to handle the binhex file attachment.
CR: JAGad28647 SR: 8606159318
Service Router takes a long time to stop (omoff -d 0 -s
router) and memory consumption is incrementing on heavily
loaded systems when vir*s ruleset is enabled
(ALL-ROUTER.VIR).
In fact each message that passes through service router
causes a loss of just over 1K of memory.
CR: JAGad28840 SR: 8606159513
Various inconsistencies have been identified in the code
within function definitions or calls, e.g. missing or extra
parameters or wrong type of parameter.
CR: JAGad29235 SR: 8606159909
Automatic filing of an incoming message to a folder by the
OpenMail auto-actions doesn't update the item count on the
Web Client folder page in the current session.
CR: JAGad29644 SR: 8606160320
The Service Router suffers from [OM 28874] errors when
processing certain messages from the SendMail interface
When doing filetype coercion on the binary attachment it is
reading past the end of file while trying to work out what
the file type is.
CR: JAGad29892 SR: 8606160571
Extensions to the UAL protocol required to support MAPI
Offline Folder Sync. development (OpenMail/MAPI B.06.00
release).
CR: JAGad31458 SR: 8606162142
Using OpenMail Graphical Interface version B.06.00.00 with
OpenMail B.06 and the client language set to GERMAN, it is
no longer possible to logon.
CR: JAGad31479 SR: 8606162163
On an Ensim machine, the IMAP server randomly drops socket
connections to the UAL giving the error message:
sock3/BYE: r {OpenMail IMAP Server not available}
CR: JAGad32112 SR: 8606162796
Netscape Messenger hangs during first access of a message
with a pathname containing backslash characters in the
content-type.
CR: JAGad33512 SR: 8606164212
The folder size is not updated in the Web Client 5.10
Filing Cabinet listing even after filing a few messages to
the folder. The user needs to logoff and re-login to view
the updated size.
CR: JAGad33773 SR: 8606164474
The OpenMail Internet gateway rejects multipart/signed
messages if one of the multipart boundary-end markers is
missing. Similarly, if such a message is encountered in the
OpenMail message store, the Item Browser may hang while
attempting to display the message.
CR: JAGad34214 SR: 8606164917
OpenMail GR6 + Oct00PP - Outlook Express (IMAP) fails to
download a message that contains a "special" character in
the friendly name. Special = ()"
CR: JAGad34502 SR: 8606165208
Under some circumstances moving or copying a message to the
Bulletin Board Area (rather than an individual BB) causes a
fatal UAL error: "The content record requested does not
exist in this container."
CR: JAGad34729 SR: 8606165435
The top line in the script is #!/bin/sh which does not
exist on machines running solaris.
CR: JAGad37344 SR: 8606168062
A new username that differs from an existing one in case
only (eg. "John deVere" as compared to "John Devere") was
not recognised as clashing, potentially resulting in more
than one user with the same name.
CR: JAGad37410 SR: 8606168129
omlicmon aborts when virtual licensing is used and OpenMail
is not omshut/omrc for long periods (months). Same issue
also would show up when not using virtual licensing, but
when the nodelock file is "touched" a lot.
omlicmon aborts with the following in omshowlog output:
SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00
19:30:16 [OM 14460] Unexpected error in License monitor.
Group = 1; Reason = 24.
Error text follows :
Too many open files
SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00
19:30:16 [SYS 24] Too many open files
File Name: OMDATADIR/temp/0ge23mu
-> lic_OpenShadowFile
<- lic_OpenShadowFile
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> lic_ListShadowFile
<- lic_ListShadowFile
-> lic_CloseShadowFile
<- lic_CloseShadowFile
-> lic_OpenShadowFile
<- lic_OpenShadowFile
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
CR: JAGad37711 SR: 8606168431
The OpenMail notif.mon program does not output entry and
exit procedure-level trace to the omshowlog log files.
PHSS_22458:
CR: JAGad30987 SR: 8606161671
OpenMail support required for MAPI Offline Folder Sync. EEP
PHSS_22362:
CR: JAGab84570 SR: 8606112256
Randomly lost BB ACL flag, causes ACLs to be relaxed on BBs.
CR: JAGad05041 SR: 8606135910
Even if the UAL_MSTORE_SIZE_LIMIT is specified and
UAL_SIZE_MSG_TO_ENU is set to TRUE in the user's
configuration file, when this user's message store size
exceeds limit, no message is sent to the ENU to notify this
fact.
CR: JAGad05207 SR: 8606136077
Multibyte subject of warning message for mbox exceeding the
size limit is garbled when viewed with IMAP4 and POP3
clients.
CR: JAGad11128 SR: 8606141768
omcpinu fails to restore mailboxes with the error
"[OM.PM 1004] Internal problem detected, see the log files"
CR: JAGad13619 SR: 8606144279
Unix gateway aborts when certain messages are being sent
out. These messages originate from the cc:Mail client and
have an invalid CONTENT_FILE record, containing
miscellaneous text from the message in the
CONTENT-DISPOSITION field.
CR: JAGad14574 SR: 8606145237
When a tray is accessed by an IMAP client, a sequence number
is assigned to each item.
omcpinu does not assign unique sequence numbers to items
which it copies into a user's message store. This means that
IMAP clients, e.g. Netscape Messager, can become confused
and fail to display all items in the user's tray.
CR: JAGad15232 SR: 8606145896
Multiple OM 16130 errors get logged to the fatal log file
when a Japanese OMGUI client is used to print a message via
the OpenMail server.
CR: JAGad15339 SR: 8606146003
If an address has the i-tx field and using address mapping
format 3 then the address comes out as
name.i*i.surnamexxx.yyy.zzz
CR: JAGad21220 SR: 8606151881
Following ServiceGuard Failover, omrc sometimes exits with
the following error:
"omrc : There are still ual.remote/ual.local
processes running from a previous OpenMail start-up.
If you wish to restart OpenMail cleanly,
run omshut or wait for the following
processes to terminate, then run omrc:
Active Session PID:"
CR: JAGad21785 SR: 8606152455
The format of sendmail.cf has changed for Sendmail 8.10.
OpenMail needs to be able to configure this file during
installation.
CR: JAGad21810 SR: 8606152480
OpenMail gets compilation errors when built with RedHat 6.3.
CR: JAGad23468 SR: 8606154150
If you install Openmail B.06 on a Linux machine e.g. using
"rpm -i" and then remove it e.g. using "rpm -e" a lot of
files get left on the machine.
CR: JAGad23509 SR: 8606154191
Linux RedHat 6.3 ships xinetd instead of inetd. This means
that during OpenMail installation the openmailpxy and ccmtp
services are not set up correctly.
CR: JAGad23675 SR: 8606154357
unix.in process terminates with bus error when processing a
TNEF attachment.
CR: JAGad23678 SR: 8606154360
Message "The server responded: Cannot append that message"
is displayed when trying to move a message from the (local)
"Sent Items" folder to an OpenMail folder using Outlook.
If UAL tracing is switched on, the problem seems to be in
the UAL include file command processing :
INCLUDE FILE Command: Flags=0x20001,
File='OMDATADIR/user/u000091/TMPA22529/02rbts9'
INCLUDE FILE Command: MsgRef=0, DirectRef=000fdda33baa2e12,
ToCode=0, FromCode=0 CharSet=iso-8859-1
INCLUDE FILE Command: Subject = ''
INCLUDE FILE Command: Creator = ''
INCLUDE FILE Reply : NewItemRef=0, NewAbsRef=0, DirectRef=,
Error Text =''
**** REPLY Error Number = 1502 Group = 0, Reason = 0
GET ERROR MSG Command: ErrNo=1502, ErrNoExtra1=0,
ErrNoExtra2=0 GET ERROR MSG Reply: ErrorText1:
Requested conversion is not available on this system
GET ERROR MSG Reply: ErrorText2:
CR: JAGad24043 SR: 8606154726
Certain types of non-delivery notification from OpenDesk
(such as when a message is sent to an invalid OpenDesk
mailnode) do not have the correct Ack ID, after the OpenMail
Desk gateway has processed it. If the original message came
in via X400, then this problem can lead to the OpenMail X400
gateway rejecting the NDN because the ACK ID does not
contain the original CAP (Country, Admin Domain and Private
Domain) information.
CR: JAGad25016 SR: 8606155703
RedHat's rpmlint reports lots of errors regarding the
openmail rpm packages. The number of these errors needs to
be reduced.
CR: JAGad27743 SR: 8606158413
If the general.cfg setting :
MDC_DDS_DELETE_DATA=TRUE
is active, then messages browsed using IMAP
clients appear to be blank.
PHSS_21945:
CR: JAGab33837 SR: 1653262501
If a recepient name in the DL is ambiguous while sending a
message or while checking DL names from the Web Client 5.10,
the list of alternate names is always sorted on the default
sorting order even if an alternate sorting order has been
specified in the profile file (using the tag
DL-ALT-NAME-SORT).
CR: JAGab63204 SR: 8606101643
This is an interoperability problem and an ER for Web
Clients.
When the Web Client attaches a local file, the file name is
not displayed correctly on Internet clients (Outlook Express
in IE4).
The worst situation occurs when a BINARY file is attached
(e.g., BMP). The filename is lost and, because it is a
binary, OE will display the item's filename as something
like ATT00225.dat. It is almost impossible to open such item
because both the filetype and filename extension are
unknown.
Happens for both Web Client 5.10 and Web Client 6.0.
CR: JAGab72994 SR: 8606105114
IMAP clients are unable to view attachments of messages
which have no body parts (i.e. the message is only an
attachment).
CR: JAGac29290 SR: 8606114526
It should be possible to install and run OpenMail on HP-UX
systems where the LSSERV components have not been installed.
This already works on Solaris and Linux.
CR: JAGad00687 SR: 8606131537
While viewing the auto-answer text in PAW using IE, line
breaks are getting removed and the entire text is appearing
in a single line. This problem does not occur on Netscape.
In addition, the column size of the auto-answer text box
should be increased to 72-80 characters so that the
cut/paste operation from clipboard will be easier. The
current column size is 40.
CR: JAGad01673 SR: 8606132524
The background search process fails to do a search on the
contents of a note.
CR: JAGad01880 SR: 8606132732
The unix gateway fails to parse certain incoming messages
containing Delivery Status Notification reports.
CR: JAGad02855 SR: 8606133711
Desk Gateway socket handler (desksock.recv) could sometimes
abort with an ENOBUFS error, if memory is short on the
machine.
CR: JAGad03000 SR: 8606133860
If an attempt is made to update the 000002k file (which
holds Outlook delegate information) by using tfbrowse to
convert this to a textual representation, edit the textual
representation and then convert it back to transaction file
format, corruption takes place.
For instance, if the name "Outlook Delegate/local" is the
name of the delegate and this process is undergone without
any edits, after replacing the 000002k file with the new
file, the Delegates tab under Tools,Options shows
"Delegate/Outlook///local" where before it showed "Outlook
Delegate".
CR: JAGad03146 SR: 8606134007
Login problem with Web Client 6.0.
CR: JAGad03894 SR: 8606134759
omlimits warning messages are not delivered to a user's
mailbox when the mailbox size has been exceeded. The problem
is specific to users who are using a different language
setting to the openmail server.
CR: JAGad04005 SR: 8606134871
Japanese cc:Mail Mobile users has a reply problem when the
original message is created by Outlook + MAPI.
CR: JAGad06793 SR: 8606137667
When submitting messages via the SMS2000 X25 protocol, the
originator sometimes got back an NDN with the following
error text:
'Message unable to be mapped at gateway' [OM 9400]
Supplementary Information:
(SMS) SMS2000: Operation rejected because argument
value(s) missing or invalid. [Result = 1]
In all cases that were investigated, the recipient had
infact received the SMS message, so the NDN was very
misleading. Also, when this happened, the recipient would
sometimes receive the message two or three times.
CR: JAGad07023 SR: 8606137874
Opendesk Gateway (outgoing) sometimes aborts, when trying to
map the ACK database file into memory.
CR: JAGad07491 SR: 8606138290
Attachment descriptions of file attachment are corrupted
when accessing a B.06.00 OpenMail server using
WinOMGUI-J or the ICE-NIPPON web client profile.
The filecode is displayed instead of the file description.
The display in WinOMGUI-J looks something like :
KONO KOMOKU NO TAIPU HA p. (2147) DE
TEKISUTOTOSHITE..DEKIMASEN
Where capitals represent Japanese Katakana/Hiragana
characters.
CR: JAGad08966 SR: 8606139655
The Mime internet gateway does not recognise fred.txt.vbs as
being of type "vbs". The extension after the final dot
should be used when determining the type of a file
CR: JAGad11000 SR: 8606141637
In certain network environments, since the changes to the
UAL file transfer protocol made in the February 2000
periodic patches, some UAL sessions could disconnect or hang
when sending messages.
CR: JAGad11143 SR: 8606141783
With the genearal.cfg tweak SR_FILTER_TYPES_OF_ATT=2188
set,the vbs attachment name is deleted but not the
Content-Disposition header from the vbs attachment.
CR: JAGad12244 SR: 8606142895
An extension of the UAL_GETFIL command is required to allow
a client to obtain the name of a server file that contains
the settings for the parameters to the Outlook secur*ty
patch. These settings must configurable on both a system and
per user basis.
CR: JAGad12543 SR: 8606143206
The portal daemon dies if the tweak UAL_SINGLE_TEMP_DIR has
been specified in the general.cfg file and a hostname lookup
request with a new character set is received from a Web
Client 6.0 session.
CR: JAGad12554 SR: 8606143218
If an ACL is created for a Request Server Script, and a user
with a space character in its mailnode name is added to that
ACL with execute permissions, any request made by that user
to that script fails. The user should be able to access the
script if they have been added to the ACL with the
appropriate permissions.
CR: JAGad21211 SR: 8606151872
Cannot back-out Feb00 or May00 Periodic patches, to a
pre-Feb00 version. omunpatch would report errors of the
following form:
ld.so.1: omeval: fatal: relocation error: file
OMBINDIR/lib/libom_nfda.so: symbol
er_ErrorInfo: referenced symbol not found
Note, backing out from May00 to Feb00 is OK.
PHSS_21698:
CR: JAGad05750 SR: 8606136626
Problems decoding UTF7 for non-ASCII folder names in IMAP
client
PHSS_21618:
CR: JAGad04018 SR: 8606134884
With the general.cfg option :
BRW_NAME_MAPPING=TRUE
enabled.
The name mapping behaviour is not applied to "Return-Path:"
lines for messages originating within the OpenMail network.
For instance, if the OpenMail user "gren/local" had an
internet address mapping of "grenlanza.pwd.hp.com", then a
message from this OpenMail user will contain the following
lines when browsed using an IMAP or POP3 client :
Return-Path: <gren/locallanza.pwd.hp.com>
From: grenlanza.pwd.hp.com
PHSS_21440:
CR: JAGab32379 SR: 1653240259
Unix gateway aborts with OM-UX 1131 if DDV1 address
has multibyte characters
CR: JAGab32452 SR: 5003366708
Event logging in all areas of SMS is poor.
CR: JAGab32488 SR: 5003454405
Messages sent with precedence bulk, junk, or list receive
many autoreply messages back (when recipients switch on the
autoreply) which is unnecessary.
CR: JAGab33999 SR: 1653285569
Missing CREATOR rec. from Del. Envelope causes X400 to
non-deliver msg.
CR: JAGab34077 SR: 1653296350
Acks are not being re-routed when the SR_RESOLVE_MASK
general.cfg option is set.
CR: JAGab34096 SR: 1653298653
When using a PDL within another PDL, the PDL can end up
pointing at itself as its parent
CR: JAGab34157 SR: 1653306589
omscan when run in fix mode (omscan -a -f) removes
"lost+found" directories, making fsck impossible
CR: JAGab34186 SR: 1653310714
OpenMail does not deliver incoming internet messages
correctly when there are whitespaces around the "=" in a
MIME Parameter in the qf file, e.g.
'HContent-Type: Multipart/mixed; boundary = "123456789"'
(Note the spaces around the '=').
On a SUN/Solaris server the messsage is rejected with an [OM
10250] error. On a HP-UX server, the message is delivered,
but without the bodyparts.
CR: JAGab34785 SR: 5003465195
Openmail GUI 6.0 allows users to send Repeat Reminder
messages, under some circunstances, the messages disappear
completely from the client's Out box, eventhough, the
messages are still being sent out as scheduled.
CR: JAGab34850 SR: D500253328
Some general.cfg values could contain charset names that
include an underscore. For instance at incoming Desk and
UNIX gateways.
But general.cfg disallows use of underscore, or replaces it
with space maybe. As a result,
the above gateways do not work for such character sets.
CR: JAGab74208 SR: 8606105866
On GR6 create a message and send it to yourself using
Outlook. Using omcontain check that the Inbox and Sent Items
(Pending Tray) copies of the message have an object file
(MAPI.ObjectProperties).
omcpoutu the user, delete the user, re-add the user, omcpinu
the user.
Now use omcontain to check the message object file - it's
gone!
CR: JAGab74694 SR: 8606105948
ORNs in text version of tf with no '/' are lost by tfbrowse
-g
CR: JAGab76033 SR: 8606106702
Local Delivery aborts when File in ~openmail/data is
missing.
CR: JAGab76643 SR: 8606107035
If the UAL monitor makes 3 unsuccessful consecutive attempts
to connect, then it is terminated. There is no delay between
these attempts and resulting termination means that the
monitor has to be restarted before any further requests can
be handled.
A tweek, allowing a time delay between attempts to connect,
and further additional attempts before failing, would mean
that this problem was less likely to happen.
CR: JAGab78064 SR: 8606107773
Items containing more than one 'Content-Disposition' lines
for an item can cause IMAP4 clients to hang when trying to
browse the item.
CR: JAGab78752 SR: 8606108351
Local delivery fails with a bus error, reporting the
following trace when the LD_AUTOREPLY_CHECK_ON is set and
multiple Local Deliveries are in operation.
SERIOUS ERROR Local Delivery(Local Delivery)
10.28.99 10:36:09 [OM 10250] Process about to terminate due
to error. Signal (Bus Error) trapped by process 6957; code =
0. Procedure trace follows:
<- tf_GetINT32
-> tf_MarkPrevRecord
<- tf_MarkPrevRecord
-> tf_GetINT32
<- tf_GetINT32
-> tf_GetINT32
<- tf_GetINT32
-> tf_ReadRecord
<- tf_ReadRecord
-> tf_GetINT16
<- tf_GetINT16
-> tf_GetINT32
<- tf_GetINT32
-> ld_AAReplyAlreadySent
-> im_ItemRef2FName
<- im_ItemRef2FName
CR: JAGab82030 SR: 8606109330
cc:Mail Mobile 6.22 OpenMail edition cannot reply to
messages which contain RTF files. When an attempt is made
to reply to the message, the original RTF text is displayed,
however, no modifications can be made to it.
Items which have original filenames (created by Outlook
clients) were being treated as file attachments regardless
of whether they had actually now been converted to text.
CR: JAGab82546 SR: 8606109847
The problem occurs when a quoted-printable subject field of
a message containing multiple 8-bit characters separated by
a '?' character is received at the unix gateway. Only the
8-bit characters before the '?' are decoded correctly.
CR: JAGab84515 SR: 8606112206
Japanese messages which are stored in a folder on the server
using IMAP4 are not readable from other standard OpenMail
clients.
CR: JAGab84577 SR: 8606112263
Serialised file handles are not free'd after container
compaction has occured. This can cause Local Delivery to
abort when it runs out of file handles. The following error
is generated: [OM 28870] "To many serialised items open".
CR: JAGac29346 SR: 8606114582
omcheck -i does not work on Linux, for filesets where the
check data file is less than 8K in size (e.g. everything
except the OM-CORE fileset).
CR: JAGac29459 SR: 8606114696
MIME Content disposition still has filename under some
conditions when it need not. This causes problems for some
clients (mostly MS ones)
Also, Content-Dispositions are mixed. For example, a
multipart alternative body part has the first alternative
marked as inline and the other as an attachment when they
should both be inline or attachments.
CR: JAGac39658 SR: 8606124275
The unix gateway crashes when receiving certain incoming
messages. The message is not delivered and no non-delivery
acknowledgement is returned.
CR: JAGac40185 SR: 8606124793
There are particular messages that arrive through the
internet(mime) gateway that causes "Outlook" to lose
connection upon reading the folder where they are located
in.
With "omgui" there is no problem is accessing/reading the
folder/msg.
Outlook's error-message when opening the folder with the
problem msg in:
UAL Network Error:
Failed to send data. The connection may have been lost.
Software caused connection reset.
Connection Type: Windows Sockets
The ual.remote session aborted on the server; in omshowlog
you'll find:
SERIOUS ERROR Remote Client (U/I Access ) 12.30.99
08:16:58 [OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 22383;
code = 0. Procedure trace follows:
-> ual_IsMappingAvail
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- ual_IsMappingAvail
-> ual_IsMappingAvail
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- ual_IsMappingAvail
User Name: kinderkanal / hppine83, 01>!]
CR: JAGac40230 SR: 8606124838
The unix gateway truncates the incoming UUENCODED attachment
file name at the first space.
CR: JAGac42791 SR: 8606125848
omdbmon sometimes aborts with SYS:22 error
CR: JAGac78718 SR: 8606127917
ccmobile users cannot reply to Microsoft RTF messages.
Even with ConvertToRTF=1 set in ccmtp.ini, the reply is
virtually illegible to the Outlook user as the standard
cc:mail reply colours of yellow text on a blue background
become yellow text on a white background.
CR: JAGac79005 SR: 8606128205
The checks introduced by JAGab33916 to detect whether
an X400 user is infact local, did not work with non-delivery
rulesets
CR: JAGac86611 SR: 8606129065
item.browse sometimes aborts when processing a msg with
multibyte attachment.
CR: JAGac86632 SR: 8606129086
ualth doesn't always detect new messages arriving in
intrays.
CR: JAGac86756 SR: 8606129210
omaddu without options causes segmentation violation on
Solaris & Linux systems (GR6+Feb2000 PP)
When omaddu is executed with invalid arguments, the usage
strings are printed in a different way on Linux & Solaris &
are in improper format. On Linux, some garbage charecters
appear in the Usage string. On Solaris, each usage string is
printed twice.
CR: JAGac86786 SR: 8606129240
Segmentation Violation in test viral scanning library.
CR: JAGac86878 SR: 8606129332
Dirsync impacts client directory access significantly
CR: JAGac87789 SR: 8606129454
The directory synchronisation program does not modify the
slave directory entry correctly when attributes have been
removed (deleted) from the master directory entry.
Note:
This problem only occurs when the 'omresyncds' command is
used to trigger a directory resynchronisation.
The normal directory resynchronisation does not exhibit this
problem.
CR: JAGac87845 SR: 8606129510
This is an enhancement. Mobile devices do not understand
HTML and they do not support Javascript and Frames, hence a
new profile is required for connecting to OpenMail from such
devices.
CR: JAGac87847 SR: 8606129512
When OpenMail is installed, certain directories such as /etc
are left with the wrong permissions. Sendmail 8.9 is very
strict about permissions and it will issue a large number of
error messages; it may even stop delivering the mail
altogether. OpenMail does not warn the user about this
problem. omrc should issue a warning when the permissions
are wrong.
CR: JAGac87851 SR: 8606129516
Web Client profile selection page is not accepting the HTTPS
protocol in the URL
CR: JAGac88829 SR: 8606129914
The November 1999 and February 2000 B.06.00 periodic patches
incorrectly documented the default value for the
general.cfg setting UXO_ITEMSUB_IS_FNAME as being TRUE.
CR: JAGac95131 SR: 8606130260
When a message enters OpenMail through the internet gateway,
the comments that are on an smtp address are lost. And
consequently, they cannot be displayed when the message is
read.
For example, the sender:
"John A. Smith" <103343.1432compuserve.com>
is saved as
<103343.1432compuserve.com>
CR: JAGac95600 SR: 8606130710
in.imap41d crashes when attempting to accept a client
connection (on an already busy machine with many clients
connected).
CR: JAGad00184 SR: 8606131026
Missing system shared library is causing webselect.cgi to
abort when it is accessed in a VirtualVault environment.
CR: JAGad00185 SR: 8606131027
The portal daemon uses a default value of 3 for the number
of matching login names. This sometimes confuses the users
when they are not able to find their names in the list.
CR: JAGad00350 SR: 8606131199
If a backlog of 500 or more messages have accumulated in the
~openmail/sms/data directory, while the sms.server has been
shut down, when the sms.server process is restarted, it
fails to process the backlog.
CR: JAGad00539 SR: 8606131389
When a fatal error occurs in the sms.server process, the
error message is only seen if the sms.server process is run
in the foreground, in which case the message appears on the
screen. Nothing is logged to the fatal or omshowlog files.
If sms.server is run in the background (default) then there
is no clue as to what went wrong.
CR: JAGad00698 SR: 8606131548
A large value for the DRS default connection timeout is
causing performance problems for the portal daemon
CR: JAGad01319 SR: 8606132170
The B.05.10.00 version of omsendin does not recognise the
8.9.3 version of sendmail.cf. It also does not recognise the
8.8.8 version available on some versions of Solaris and
HP-UX.
The B.05.10.00 and B.06.00.00 versions of omsendin do not
reliably add an equal sign to the list in the OperatorChars
option of sendmail.cf.
CR: JAGad01353 SR: 8606132204
If there are more than about 60 top level folders in a
user's mailbox, then omtidyu may fail to find messages for
deletion in the filing cabinet.
The error message :
Maximum number of open Lists would be exceeded
is displayed and omtidyu exits.
CR: JAGad01557 SR: 8606132408
Notification server aborts in Service Guard environment with
two or more standby redundant lan cards.
CR: JAGad01812 SR: 8606132664
Possible inability to send message using web clients
CR: JAGad01851 SR: 8606132703
omaddred will not accept filter unless -I option is given
also.
CR: JAGad01856 SR: 8606132708
ual library on the server is very slow - reads data 8 bytes
at a time!
CR: JAGad02689 SR: 8606133544
Outlook Delegate access sometimes fails when accessing the
Calendar after Inbox items have been read. (Only seems to
happen using Outlook 2000)
The difference between OL97 and OL2000 is that when (as a
delegate) I read a meeting request in the principal's Inbox
the following happens:
OL97: Calendar info is explicitly retrieved
LocalFreebusy message is retrieved
OL2000: LocalFreebusy message is retrieved
Calendar info is retrieved
The problem is caused by the fact that when the
LocalFreebusy is obtained first an implicit list of the
Filing Cabinet and Calendar takes place and these implicit
list have restricted information in them and in the case of
delegate access the AccessCaps are not set up. The
subsequent retrieval of the Calendar information picks up
the implicitly generated list information and the incorrect
AccessCaps.
So this problem will occur on OL2000 every time a delegate
tries to process a meeting request before opening the
Calendar.
CR: JAGad03759 SR: 8606134624
The remote client interface is crashing occasionally when
using an IMAP client under Linux.
The omshowlog command shows that a segmentation violation
has occured in the Remote Client Interface.
CR: JAGad03776 SR: 8606134641
Attempting to access the PAW on an EP1 Linux box simply
gives the ICE web client.
CR: JAGad04546 SR: 8606135412
If you install any periodic patch for B.06 earlier than May
00, and then remove it e.g. using swremove (on HPUX), all
the previous versions of the patched files get correctly
restored EXCEPT for anything in the ...B.06.00.00/lib
directory. This problem only occurs on B.06 patches, B.05
patches are fine.
CR: JAGad04673 SR: 8606135539
While reading a message, the WAP client is not able to
display the message content body page containing a URL. The
error message "Page cannot be displayed" is shown thus
indicating a WML syntax error.
PHSS_20777:
CR: JAGab32483 SR: 5003444679
Customer would like to disable sending when a user exceeds
there omlimit limits.
A new option to omlimits has been added which allows sending
to be disabled when required.
CR: JAGab33916 SR: 1653272351
NDN is non-delivered back to the originating user. When a
message is sent to a non-existant user, the NDN being
generated at the local delivery , has the primary recipient
marked with all CAP[O] attr. Since we have a X.400 route
added for this CAP[O] explicitly, the
NDN is routed via X.400. But X.400 aborts while constructing
the message and the message(NDN) is not delivered back to
the originating user.
CR: JAGab34044 SR: 1653291617
When a Web Client running on multiple OpenMail system is
accessed,the CGI program aborts. An error 'Which OpenMail
system?' is written to the Web Server log.
CR: JAGab65807 SR: 8606101854
UAL aborts if Notification Server runs out of memory
CR: JAGab69180 SR: 8606103019
In the situation where 2 managers have 2 different delegates
who recieve the manager's meeting requests, and a meeting
request is sent to both managers only one delegate receives
the meeting request.
CR: JAGab72452 SR: 8606104741
messages received from remote openmail systems are lost when
attempting to deliver to a local mailnode which
has a rule-set defined that defers mails depending on their
size.
CR: JAGab72649 SR: 8606104884
Aliases login doesn't seem to function properly .
CR: JAGab72864 SR: 8606105045
NDN_EXTRA_INFO is not included in outgoing messages from
the Internet Gateway.
For instance, if a rule for an OpenMail route (see ommodrt
-d)
uses a file containing the lines :
SIZE=10 PRIORITY=LOW ACTION=REJECT NDN-INFO="Msg reject as
over 10MB" SIZE=10 PRIORITY=MEDIUM ACTION=REJECT
NDN-INFO="Msg reject as over 10MB"
Messages which are rejected because they match this rule
should contain the text : "Msg reject as over 10MB" as
specified in the rule file. Internet messages do not
contain this.
CR: JAGab75968 SR: 8606106664
Problem with openmail setuid programs
CR: JAGab75998 SR: 8606106674
The code for the test scanning library and the code supplied
by Trend Micro, are not returning the same values (in fact
the complete
opposites)
CR: JAGab76793 SR: 8606107113
SMS gtw stops conversion of characters after sign in conv
to GSM 03.40
CR: JAGab77480 SR: 8606107301
binary touch coverage checking needs to be done in a
different way.
CR: JAGab77872 SR: 8606107609
Entering a non-null subject through IE does not get
registered by the browser and the subject gets stored as
blanks.
CR: JAGab81837 SR: 8606109138
smimetxt does not process a pgp mime message correctly.
This is because of the quoted protocol.
CR: JAGab82255 SR: 8606109555
With multiple sign-ons message store sizes reported by
omscan and clients can be incorrect or do not change until
log out.
each process records it's own size changes but other
processes do not have access to this information. It is only
written to disk when the process shuts down.
Pending deletes only change sizes when the phsyical delete
takes place.
CR: JAGab83272 SR: 8606110523
Currently all the users using a profile will be connected to
the same server. This limitation should be removed by having
an automatic lookup facility to locate a user's OpenMail
server hostname and then connecting to it.
CR: JAGab83274 SR: 8606110525
Openmail LDAP server does not force an unbind of an
authenticated session when an anonymous bind is received.
This is supposed to be LDAP V3 functionality.
CR: JAGab83278 SR: 8606110529
This is an enhancement. To prevent sensitive information
from being displayed via the internet, the Bulletin Board
feature will be denied from Web Client 6.0.
CR: JAGab83749 SR: 8606110999
To improve the access-control for OpenMail via Virtual
Vault, a feature is required by which the administrator can
selectively enable/disable the Web Client access for a user.
CR: JAGab83752 SR: 8606111002
This is an enhancement. Users of IMAP/POP don't have access
to the auto-actions functionality of OpenMail. Providing a
truncated Web Client profile will be useful to them.
CR: JAGab84076 SR: 8606111938
Japanese conversion to ISO-2022-JP does not fully conform to
RFC-1468. The end of text should be in ASCII (ESC "(B").
CR: JAGab84362 SR: 8606112091
Messages are undelivered when the file transfer parameter
IM_FILE_ATTRIBUTES is not present.
CR: JAGac20259 SR: 8606113989
The message store search is failing for the Web Client 6.0
if the previous search results are displayed and the search
is submitted in
succssion a few times
CR: JAGac20262 SR: 8606113992
If any DL in the DL folder is created/updated, then the DL
folder contents don't get displayed within the same session.
CR: JAGac23147 SR: 8606114169
omreqlic requests to linux machines have there replies
rejected 50% of the time with error [OM 28211 ] logged in
the log file.
CR: JAGac29140 SR: 8606114376
Same as submitter text
CR: JAGac29288 SR: 8606114524
If I log onto hpopdlct.pwd.hp.com as user Silver with no
password and perform a search for all messages, then the
resulting list should contain (currently) 8 items but the
list is empty. The UAL is returning a 555 (invalid list ref)
to a request for the search list file.
CR: JAGac39969 SR: 8606124586
Cannot execute Domino 4.5 Notes Executables on Solaris
2.5.1.
When the attempt is made to execute any of the four Notes
Api programs in OMBINDIR/notes.inst/sun/4500, the
following message is
displayed:
libc internal error: _rmutex_unlock: rmutex not held.
CR: JAGac40302 SR: 8606124910
The situation arises when using Netscape version 4.06 and
later. When used with earlier versions of Netscape, and with
IE4 and IE5 the OpenMail Web Client 6.0 does not exhibit the
problem. The circumstances
are as follows:
When an attempt is made using the OpenMail Web Client 6.0 to
create a Rule to, say, automatically autoforward or redirect
incoming mail (eg during a vacation period), and the "Date
Range" option is selected, the user is presented with two
date range fields, which can be edited,
that initially contain by default today's date, and a date a
week from today. These dates are presented with a year 100
instead of 2000.
When an attempt is made using the OpenMail Web Client 6.0 to
search for messages matching some filter criteria on the
delivery/create/expiration dates(for example, all messages
delivered on a particular date),
the user is presented with the default date as today's date.
This date is presented with a year 100 instead of 2000.
CR: JAGac40677 SR: 8606125286
Unable to customise sendmail.cf version 8.9.1 when
installing on Solaris
PHSS_20552:
CR: JAGab83434 SR: 8606110686
The PC Admin Client can not connect to the OpenMail server.
PHSS_20013:
CR: JAGab32576 SR: D500419564
The existence of "filename" field in the MIME header for
bodypart text will cause most browsers to handle it as an
attachment, not the bodypart text.
The field is redundant for bodypart text.
Please see related problem JAGab37437 which relates to the
same problem for the internet gateway.
CR: JAGab34141 SR: 1653304451
When the dirsync server , encounters a MODIFY Req for an
entry that doesn't exist, it basically ignores it if it is a
OM<->OM sync. The function ds_DoUpdate, which handles this,
goes ahead to add the request, if we have a OM<->SoftSwitch
Sync. A combination of both pEntry1 and pEntry2 which would
contain all the necessary
attributes, should have been added.
CR: JAGab34162 SR: 1653307066
Web Client 6.0 program aborts while attempting to logon with
a long multi-byte user name.
CR: JAGab34164 SR: 1653307249
Basically, the customer was using the 1984 X.400 standards,
which doesn't support -TX ATTR. And, when a mail is sent
from One OM User to another OM User (who has -TX ATTR) , and
if the mail is routed via X.400, then we encounter a doubly
wrapped message at xport.in.
This message, though it is decoded, the external Dummy DL is
used in this case. Instead, the Internal Encoded DL should
be used, which contains the -TX ATTR.
CR: JAGab34183 SR: 1653309591
Cannot mail to a recepient having OU*-TX and DDV fields in
his address.
CR: JAGab34770 SR: 5003458851
The failing of the generation of an NDN causes Local
Delivery, Service Router or Unix Gateway to loop and
eventually abort.
CR: JAGab35487 SR: D500353086
When adding several users to a public distribution list
(PDL), omaddpdln fails and the following message is logged
to the
OpenMail log (viewable with omshowlog) :
WARNING Administration(omaddpdln ) 03.16.98
09:27:05 [OM 2214] Unable to re-allocate memory. realloc
errno 12 size 77729
ERROR Administration(omaddpdln ) 03.16.98
09:27:06 [OM 2207] Unable to allocate memory.
< - da_FindAttribIntName
-> da_FindAttribIntName
< - da_FindAttribIntName
-> nm_IsT61Field
< - nm_IsT61Field
-> nm_IsT61Field
< - nm_IsT61Field
-> nm_IsT61Field
< - nm_IsT61Field
-> nm_IsT61Field
< - nm_IsT61Field
-> nm_IsT61Field
< - nm_IsT61Field
-> nm_IsT61Field
< - nm_IsT61Field
CR: JAGab35885 SR: D500413443
Move a BB with Items in it to another BB and Sync to the
Remote Server, Only the BB gets added on the RemoteServer,
Items do not get added hence resulting in BBs out of sync.
CR: JAGab36268 SR: D500430124
tf.browse -g can't handle people mover records when newline
characters are found in a string.
CR: JAGab36274 SR: D500430421
The structure of the message store does not allow more than
358,999 users to be configured on a server.
CR: JAGab37437 SR: D500420604
Using the subject of an item in the "filename=" part of a
Content-Disposition line of a MIME message often causes
problems for Internet mail readers.
It should be possible to disable this behaviour.
Please see related problem JAGab32576 (SR D500419564)
which relates to the same problem for Pop3 and IMAP4
client access to the Openmail message store.
CR: JAGab39182 SR: 8606100829
If a user is added as a delegate using Outlook and
subsequently that user has part of his name or mail address
modified then the old delegate name can be listed within
Outlook but cannot be
deleted.
CR: JAGab39209 SR: 8606100833
Directory Mapping uses non-x400 attributes such as FF for
lookup.
CR: JAGab43863 SR: 8606101161
item.browse crashes when " is present in the attached
filename.
CR: JAGab45433 SR: 8606101253
The Openmail POP3 server (in.pop3d) since PP4 consumes more
CPU time than before PP4.
CR: JAGab48848 SR: 8606101412
Server changes to allow Entrust integration:
1. UAL_CHKNAM command extended to return internet-style
address
to match email address in user's certificate.
2. 'omshowu' command has extra option: -S to display a
user's
internet address.
3. New directory attribute introduced: SMIME-ADDR (attr.
no. 1300)
4. Modify Unix Gateway to process new Clear Signed message
format.
5. Modify Item Browser to process new Clear Signed message
format.
6. Write smimetxt : a converter from S/MIME to text.
CR: JAGab48993 SR: 8606101413
Server and MAPI/SP performance improvements are required for
the Outlook 5.30 client.
CR: JAGab52686 SR: 8606101484
When OpenMail internet mail gateway service tries to send
out a message which has a long subject in multibyte
(Japanese) language, the service process loops endlessly in
handling this message, passes huge blank message data to
sendmail. It makes OpenMail's gateway
service stop and server's disk full on /var/spool/mqueue.
Problem is more likely to occur when
UXO_MIME_SUBJECT_ENCODING is set to "B" or "Q".
CR: JAGab63192 SR: 8606101630
When an invalid Read Acknowledgement is received by the x400
out mapper, the mapper aborts rather than gracefully
swallowing the error.
CR: JAGab63519 SR: 8606101674
POP3 "list" and "stat" commands are inefficient in in.pop3d
CR: JAGab65100 SR: 8606101738
GR6 fixes:
D500 405621
IMAP server loops when UAL session times out.
D500 419747
Server-push prevents use of NS datagrams for UAL_NEWMSG
command
These fixes are applicable to B.05.10 clients and need to be
included in the GR5_PATCH source. (Especially applicable to
IMAP and POP clients)
CR: JAGab65826 SR: 8606101865
Not deactivating containers correctly.
CR: JAGab65894 SR: 8606101892
When a user is running 2 clients, then the sessions can be
come out of sync concerning their knowledge of the tray
sizes. It is therefore possible to end up with a negative
tray size.
For instance:
This can happen with the filing cabinet is client 1 moves
some items into it.
Client 2 may then delete these items, so will decrease the
tray size, having not increased it in the first place.
If an attempt is made to copy stuff back into the filing
cabinet from client 2, its tray size is perceived to be
negative. This is treated as a hugh positive number and so
will exceed it's tray limit.
CR: JAGab68818 SR: 8606102816
ccmht2rtf double freeing on exit and so giving a bad exit
code. NB the exit code was only ever checked for the
July99PP.
CR: JAGab69420 SR: 8606103098
SCO did not allow non-root users to do "ps" listings.
However, omrunning was SetUID root on all platforms.
CR: JAGab69554 SR: 8606103168
Long login names get truncated in the logon page of the Web
Client 6.0, the next time the page is accessed.
CR: JAGab69581 SR: 8606103183
For some messages either being browsed by internet clients
or being sent out through the Internet Gateway using
MIME format, inline body parts have a filename specified.
The messages contain a line like :
Content-Disposition: inline; filename="BDY.RTF"
Although this is correct according to the RFC 2183
standard, many internet clients will not display the item
inline - they are treated as an attachment instead.
This is a significant usability problem and thus, it should
be possible to configure OpenMail such that it will not
include a filename for any "inline" items.
CR: JAGab69827 SR: 8606103270
SUR(omdosur) fails when restoring a mailbox containing
messages generated by outlook in MAPI mode but works when
restoring a mailbox containing messages generated by other
clients such as OMGUI.
omdosur fails with the error message : Cannot create file
CR: JAGab70399 SR: 8606103536
If a message is sent from in internet user to an OpenMail
user who has an autoforward set which :
1. forwards the message to an internet user
2. retains the original sender of the message.
The autoforwarded message received by the internet user
does NOT have the original sender.
CR: JAGab70691 SR: 8606103672
The UAL call is returning error when the changed/newly
created private DLs are accessed.
CR: JAGab70712 SR: 8606103683
The internet gateway's unix.in process segmentation violates
when processing certain MIME messages containing TNEF
encoded files
CR: JAGab70735 SR: 8606103696
The following default Notes Gateway database files are
corrupted by
installing the August periodic patches :
HP-UX B.05.10 patch PHSS_19170 and PHSS_19171 :
OMBINDIR/notes.inst/hpux/4103/omconfig.ntf
OMBINDIR/notes.inst/hpux/4103/omnames.ntf
OMBINDIR/notes.inst/hpux/4500/omconfig.ntf
OMBINDIR/notes.inst/hpux/4500/omnames.ntf
OMBINDIR/notes.inst/hpux/r337/omconfig.ntf
OMBINDIR/notes.inst/hpux/r337/omnames.ntf
AIX B.05.10 patch PASS_17010 :
OMBINDIR/notes.inst/aix/4103/omconfig.ntf
OMBINDIR/notes.inst/aix/4103/omnames.ntf
OMBINDIR/notes.inst/aix/4500/omconfig.ntf
OMBINDIR/notes.inst/aix/4500/omnames.ntf
OMBINDIR/notes.inst/aix/r337/omconfig.ntf
OMBINDIR/notes.inst/aix/r337/omnames.ntf
Solaris B.05.10 patch PFSS_17010 :
OMBINDIR/notes.inst/sun/4500/omconfig.ntf
OMBINDIR/notes.inst/sun/4500/omconfig.ntf
OMBINDIR/notes.inst/sun/4500/omnames.ntf
HP-UX B.06.00 patch PHSS_19172 and PHSS_19173 :
OMBINDIR/notes.inst/hpux/4500/omconfig.ntf
OMBINDIR/notes.inst/hpux/4500/omnames.ntf
OMBINDIR/notes.inst/hpux/4620/omconfig.ntf
OMBINDIR/notes.inst/hpux/4620/omnames.ntf
AIX B.06.00 patch PASS_17011 :
OMBINDIR/notes.inst/aix/4500/omconfig.ntf
OMBINDIR/notes.inst/aix/4500/omnames.ntf
OMBINDIR/notes.inst/aix/4620/omconfig.ntf
OMBINDIR/notes.inst/aix/4620/omnames.ntf
Solaris B.06.00 patch PFSS_17011 :
OMBINDIR/notes.inst/sun/4500/omconfig.ntf
OMBINDIR/notes.inst/sun/4500/omnames.ntf
OMBINDIR/notes.inst/sun/4620/omconfig.ntf
OMBINDIR/notes.inst/sun/4620/omnames.ntf
This is only a problem when installing a NEW OpenMail
Connector for Lotus Notes. Existing installed OpenMail Notes
connectors should not be affected.
CR: JAGab71129 SR: 8606103949
Users that have had Physical Delivery (PD or PD-TX)
attributes added to their directory entries cannot then be
looked up cross-server for the purposes of getting their
Outlook FreeBusy time or their
Outlook delegate capabilities.
This causes FreeBusy checking when planning a meeting and
replying on behalf of a principal to fail.
CR: JAGab72352 SR: 8606104673
The CompMAPIProps of the Sent Items messages get truncated
by the UAL when these Props are being rewritten after the
mesg has been UAL_MOVEd to the Pending Tray. (Code in
ual_mapi.c overwrites the input buffer containing the MAPI
props (routine ual_ConvMAPIProps)
CR: JAGab73411 SR: 8606105379
The checking performed by omaddred is insufficient.
CR: JAGab74688 SR: 8606105942
Repeated calling of the UAL command UAL_DELCAP (get delegate
caps) eventually causes a serious server (ual.remote) error:
"A fatal error has occurred - see the system log file.
Too many Transaction Files open, cannot open any more."
CR: JAGab74934 SR: 8606106089
Messages from Lotus contain a 2 digit year field after 2000
whereas x.400 expects a 4 digit year after 2000 as per the
mawg specs for file transfer bodyparts.
CR: JAGab75964 SR: 8606106663
Not checking parameters enough
PHSS_20046:
CR: JAGab77877 SR: 8606107612
Service Router leaks memory when rulesets are enabled.
PHSS_19173:
CR: JAGab32489 SR: 5003454785
When Transient DRS children timeout, there are situations
where the DRS could abort.
CR: JAGab34013 SR: 1653286757
The unix.in process is not able to process some messages
sent by outlook
express. The error in omshowlog:
SERIOUS ERROR Internet Mail (Incoming ) 10.29.98
07:09:04 [OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 29848;
code = 0.
Procedure trace follows:
< - ux_InStrCaseCmp
-> ux_InStrCaseCmp
< - ux_InStrCaseCmp
-> ux_InParseArpaList
-> mim_ScanArpaStrForSpecialChar
< - mim_ScanArpaStrForSpecialChar
-> mim_SpaceTrimming
< - mim_SpaceTrimming
-> ux_InConvArpaORNToORN
...
The message will remain in the sendmail queue until it has
expired. It is related to the layout of the email-addresses:
"< "< "Sandrina Hernou""" < shernoubru-hub.dhl.com>
Too many of these will fail the unix.in process.
CR: JAGab34149 SR: 1653305789
A kind of corrupt message in outtray, which lacks real data
for a DL, can cause omcpinu to fail with bus error.
CR: JAGab34153 SR: 1653306381
If an autoforward is set to a non-existant Internet user on
a remote machine, the NDN can loop forever between sendmail
and Openmail.
CR: JAGab34175 SR: 1653308544
Delivery Acks sent from HP Desk and destined for an X400
user, are not accepted by a Microsoft Exchange MTA.
CR: JAGab36232 SR: D500428383
Viral cleaning capability required for OpenMail.
CR: JAGab36250 SR: D500429423
The following commands do not work on Solaris :
omresetmn
omaddmnmp
ommodmnmp
omdelmnmp
omshowmnmp
The output of the commands is similar to :
OMBINDIR/bin/omshowmnmp: function: not found
CR: JAGab36271 SR: D500430249
Orphans containing "MAPI 1.0 embedded message" created by
some tnef files going through unix.in. This only happens
after the June 99 PP.
CR: JAGab36273 SR: D500430413
If the UAL test harness is used in simple list mode and an
item in a list does not have a creator specified, then on
Solaris, and perhaps AIX, the test harness may abort with a
segmentation violation.
CR: JAGab37632 SR: 1653308734
Gapi fails with OM_TEMPORA_ERROR when it encounters
attachments from Internet and also RFC2157 compliant.
CR: JAGab39965 SR: 8606100966
When listing files that contain blank lines, the Openmail cd
browser may duplicate said lines.
CR: JAGab49811 SR: 8606101415
The UAL cannot connect to a local Directory Relay Server in
Simple Service Guard configurations.
CR: JAGab67687 SR: 8606102175
A new defect was introduced with the July OpenMail periodic
patches.
If a cc:Mail user receives a message from an Outlook user
that contains an RTF attachment (by default an Outlook user
will send RTF text), then any attempt to reply to or forward
that message will fail. Instead
you will get a cc:Mail error dialog box containing the text:
'The file conversion did not succeed [Codes: 1501:0:0]
[SRCUAL.C"207]'
You cannot then forward that message. If you try to reply
to it, everything may appear to be as expected but a body
part of the message received is missing.
PHSS_18906:
CR: JAGab34711 SR: 5003444174
Corruption in the DIT upsets OpenMail very seriously, but
problems do not become visible until more damage is done.
CR: JAGab34106 SR: 1653299818
omdbmon process occassionally aborts with a SYS 22 error
CR: JAGab36206 SR: D500427419
Performance improvement
CR: JAGab36209 SR: D500427443
Inefficient code path in the source
CR: JAGab36208 SR: D500427435
Inefficient code paths
CR: JAGab36207 SR: D500427427
Excessive function calls in the openmail code.
CR: JAGab36251 SR: D500429431
An interim enhancement to partially address 1653 240598. Aim
for 20% (heavily system dependent) reduction in elasped/cpu
time.
CR: JAGab32586 SR: D500428334
Unix Gateway fails while trying to decode TNEF
CR: JAGab33495 SR: 1653221341
It needs to be made clear that processes accessing a
directory before omdiropt has completed will continue to use
the original directory, not the new one.
CR: JAGab36218 SR: D500427906
Att names decoded from TNEF sometimes mismatch attachments.
CR: JAGab36255 SR: D500429530
No 3 requirement for SR 1653229252 not included in May PP.
3. at 'Attach Local File' window, the icon label "tenpu"
(attach) is already used in 'New Message' window. We
recommend that this be changed to "tenpu jikkou".
CR: JAGab36235 SR: D500428839
When omdref is used with a Direct Reference belonging to the
Bulletin Area folder (i.e. has item type -70), an error
occurs, and the following output is displayed
Failed to open parent of <Direct Ref> 3/2407: The
file-id/item-number supplied is invalid: it must be greater
then zero
CR: JAGab34006 SR: 1653286120
If a coding error in cd.browse causes it to crash,
a blank attachment, rather than an error message,
can result.
CR: JAGab35879 SR: D500413104
With multiple queues, the possibility that a message
obsoleting a previous message may arrive before the message
it will replace. This is particularly the case if the
replacement message is being used to cancel the message (it
will therefore be smaller and is more likely to overtake the
original).
This is not a completely new problem (it could happen with
sendmail) but is more likely now as there are more points at
which it could happen.
The Samsung client makes use of this feature.
CR: JAGab36219 SR: D500427914
Multibyte filenames handled incorrectly when extracted from
winmail.dat
CR: JAGab34063 SR: 1653294579
MIME encoded internet messages originating from a MAPI
client often contain an attachment of type :
'application/ms-tnef' This contains information about MAPI
properties of the original message. It may also contain
attachments to the message.
By default, the OpenMail internet gateway saves the whole of
this attachment in a file called "WINMAIL.DAT". Clients
using pre-OpenMail MAPI B.05.20 service providers expect
this WINMAIL.DAT file, however, they do not expect it to
contain attachments and do not recognise them. Similarly,
non-MAPI clients only recognise a WINMAIL.DAT file and do
not know that attachments to the original message are
encoded inside them, effectively data loss.
The OpenMail internet gateway can be configured to work
better with OpenMail MAPI B.05.20 service providers and
later by setting the general.cfg option :
UX_PRE_5_20_COMPATIBILITY_MODE=FALSE
If this is set, the information from the
'application/ms-tnef' attachment is extracted into an object
file, except for original message attachments encoded in it,
which are extracted as separate attachments to the message.
CR: JAGab34116 SR: 1653300889
The outbound unix gateway was using the content originator
as the SMTP envelope originator. This meant that if the
envelope originator (aka Return-Path:) was different from
the content originator (aka From:) then the envelope
originator was simply discarded.
CR: JAGab34151 SR: 1653305979
If the SR_RESOLVE_MASK general.cfg option is being used then
any redirection that occurs in order to send Outlook
calendar meeting requestes to delegates will fail to be
delivered to teh delegate. A Non-delivery notification gets
generated instead and returned to the original meeting
request sender.
CR: JAGab34126 SR: 1653302042
Receipt acks going back to Exchange via X.400 have the ORN
part of the message id stripped. This causes the ack to be
not matched when received by the Exchange system. See the
submitter text for more details.
CR: JAGab36217 SR: D500427898
Certain messages from the Openmail Notes Gateway that
contain 8-bit characters cause the X400 Gateway to fail
to process the message.
CR: JAGab34781 SR: 5003463190
Items in a folder or bulletin board which have been placed
there using the Outlook client's "post" functionality cannot
be read using cc:Mail
CR: JAGab34121 SR: 1653301507
After the B.05.10 October 1998 periodic patch has been
installed, a a designate with appropriate capabilities can
no longer delete items from a bulletin board.
CR: JAGab34021 SR: 1653287946
Bulletin board synchronisation messages arriving out of
order can cause synchronisation failures.
Example : Message 1 for : 'Add Item A'. Message 2 for :
'Delete Item A'. If 'Message 2' arrives before 'Message 1',
Item A will be added and will never be deleted.
Previously, the problem text of this SR documented another
scenario which could result in synchronisation problems.
This has been entered as a new SR - see D500 427351.
CR: JAGab34111 SR: 1653300392
If a network problem occurs while some big file is being
attached to a message in a Web Client 5.10 session, the user
is not able to access his mailbox until the processes on the
server are killed by the administrator.
CR: JAGab35943 SR: D500415729
For the OpenMail Web Client (B.05.00), the size is not
displayed on sending when a file has been attached to the
message.
CR: JAGab34128 SR: 1653302414
mt_transfer failure error when Single Asn encoded bodyparts
found in the message
CR: JAGab32579 SR: D500425553
When ITO uses omacmd to call omopcsm or omadmr, there is
often a SEGVIOLATION.
CR: JAGab34178 SR: 1653308759
MSMail messages to Internet recipients non-delivered by
Internet gateway
PHSS_18283:
CR: JAGab35997 SR: D500418079
If some permissions are set (using Outlook) on a private
folder these permissions are lost if the folder is moved
(but retained if the folder is copied).
CR: JAGab36190 SR: D500426809
If local.delivery is not retaining the message to delivery
it into the InTray then only the first AA_REDIRECT record
gets processed.
CR: JAGab32581 SR: D500426841
There are circumstances where the Container flag BB_HAS_ACL
gets unset when it shouldn't. The effect of this is that if
some explicit permissions are assigned to a folder these
permissions will be ignored when calculating the access
caps. of that folder (eg. for delegate access).
CR: JAGab34022 SR: 1653287953
If an item is added to a bulletin board and almost
immediately deleted. 2 synchronisation messages are
created. If these arrive out of order, the item may be
added and NOT deleted, because the first message attempts to
delete an item which does not exist.
This SR asks for a higher level of warning to be associated
with the failed deletion so that this situation can be
detected.
omshowlog -l 7 should show a message similar to :
[OM 23989] Bulletin Board Synchronisation has attempted to
DELETE an item that doesn't exist yet on this system.
See related SR 1653287946.
CR: JAGab34089 SR: 1653297937
A bulletin board changelog entry is not written when a basic
item is dragged from a container OUTSIDE the bulletin board
into the bulletin board.
CR: JAGab36171 SR: D500426189
Segmentation violation by ual.remote causes socket
disconnection failure reported at Outlook user interface.
The trace shows that a large number of notifications
(relating to BBs and BB items) are being generated in a
short space of time. This high frequency of notifications
is causing a segmentation violation in the code that
registers that notifications are waiting for the client.
CR: JAGab36168 SR: D500426130
A user performing what is essentially a read-only operation
can cause notifications to be raised on BBs abd BB items.
These unnecessary notifications can have an impact on
performance on systems where a large number of Outlook
(and/or IMAP) users are accessing the Public folders (BBs in
OpenMail terms).
CR: JAGab36200 SR: D500427070
When base exists and filter does not the return code should
be 0 with no entries returned, but the return code is 32.
32 should only be returned if the base entry does not exist.
CR: JAGab32582 SR: D500426965
The remote Outlook delegate capabilities check protocol
supported by advmail.sckd does not work properly on the AIX
and Solaris platforms:
AIX - Segmentation violation --- Solaris - returns incorrect
'send-on-behalf-of' setting for user. -------
CR: JAGab34091 SR: 1653297986
Forwarded messages whose internal message comprises of a
distribution list only (no first text part or other
attachments) will cause the Internet gateway unix.out
program to abort on Solaris machines if UUENCODE routes are
used.
On HP-UX, a mal-formed message is generated teminating with
the line :
Encoding:
CR: JAGab36170 SR: D500426163
Default BB ACL/permissions don't allow new items to be added
by an Outlook client. The default permissions for an
Outlook client should be: visible,read,create,sub-folder
but instead they are: visible,read,sub-folder
Other clients (eg. OMGUI, cc:Mail) are not affected.
CR: JAGab34099 SR: 1653299024
X400 inmappper does not strip external attributes of FROM
addresses.
CR: JAGab33809 SR: 1653256966
Under certain conditions, the Openmail Lotus Notes Gateway
can truncate long domain names for Notes users.
CR: JAGab34746 SR: 5003450593
The problem is that when the -g option is set the -I option
fails to work correctly.
The problem can be shown by first setting up an dirsync
agreement with the -I option set but not -g :-
1) omaddds -e -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" 2)
omaddds -i -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" -t "990101
00:00" -P 1 -I 3) omaddent -d DIRB -e
"S=Tester/G=A/OU1=Pinewood/OU2=hppwdj95/PHONE-1= 333" *
Restart Dirsync * ~ Entry appears in DIRA with
'PROPAGATED-BY=209' ~ 4) ommodent -d DIRA -e "S=Tester" -n
"PROPAGATED-BY=400" 5) ommodent -d DIRB -e "S=Tester" -n
"PHONE-1=666" * Wait for sync to take place * ~ Entry in
DIRA is modified to PHONE-1=666 (Correct) ~
Now if you modify the agreement to also use the -g option :-
1) ommodds -i 1 -g "S/G/OU1" * Restart dirsync * 2) ommodent
-d DIRB -e "S=Tester" -n "PHONE-1=888" * Wait for sync to
take place" ~ Entry fails to be propagated ~
The error message sent to the ENU states that :- Entry not
in the Directory or Propagated By Identifier differs.
If the PROPAGATED-BY attribute is set back to its original
value for the entry in DIRA then changes are made to the
entry in DIRB then these changes are propagated correctly.
CR: JAGab34083 SR: 1653297242
MIME filenames derived from T.61 subjects are truncated at
the first space, however, MIME filenames derived from either
the original filename or the Subject of an item can contain
a space. This is inconsistent.
CR: JAGab33573 SR: 1653231563
Acknowledgements are sent marked "urgent" by OpenMail. A
way of configuring this so that they are either sent with
the same priority as the original message or sent with a
specific acknowldegement level would be desirable.
For instance, a general.cfg option like : AK_ACK_MSG_PRI=0
could be used to force all acknowledgements to be sent with
normal priority. (valid values : 0, 1 (non-urgent) and 2
(urgent))
In addition, the following configuration option could be
used to tie the priority of the acknowledgement message to
be the same as the that for the message being acknowledged :
AK_ACK_SAME_PRI=TRUE
AK_ACK_SAME_PRI takes precedence over AK_ACK_MSG_PRI,
although under some circumstances, the priority of the
message isn't known at the time an acknowledgement is being
generated and the AK_ACK_MSG_PRI setting is used.
CR: JAGab35777 SR: D500401539
FREE/BUSY detail information is not available when referring
to a schedule of users who have multi-byte names.
CR: JAGab32360 SR: 1653229252
Miscellaneous enhancements to the OpenMail Web Client :
1. at 'New Message' window, the nuance of the Japanese label
"ma-ji" (merge) does not seem to portray the nuance of
the action. It is better if the label is changed to
"atesaki" (destination), to show the user he can select a
destination when he clicks this icon.
2. at 'Merge Distribution List from Distribution List
Folder' window, again the nuance of the label "ma-ji" is
not appropriate. It could be better as "atesaki
torikomi" than "ma-ji jikkou"
3. at 'Attach Local File' window, the icon label "tenpu"
(attach) is already used in 'New Message' window. We
recommend that this be changed to "tenpu jikkou".
4. at 'New Message' window, icon label "sakujo" (delete) is
what the program does to the message. For the user, it
is better to be "kyanseru" (cancel) in Katakana, for a
better feel that the user is in fact cancelling the
message he is creating.
CR: JAGab32523 SR: D500337337
When IBM extended characters in SJIS portion (0xfa40-0xfefe)
entering OpenMail (UNIXJIS -> OMJIS), some of them are
illegally entering OpenMail, so the specification need to
be cleared and the code need to be fixed - either to
accept IBM extended chars or not.
CR: JAGab36169 SR: D500426155
unix.in creates an orphan for each TNEF-encoded nested
message it processes.
CR: JAGab36162 SR: D500425934
The tidy-up routines called at the end of a UAL session can
cause a segmentation error.
CR: JAGab34730 SR: 5003446914
The OpenMail command ommoddir can be used to set the
Directory Change Log Life, and so can the Directory
Synchronisation commands 'omaddds -n' and 'ommodds -n'.
Internally, these 2 log life values are held in different
places.
The man pages for omaddds and ommodds do not explain the
interaction between these 2 log life settings, or how to
reduce the log life.
Further the 'omaddds -n' command cannot be used to set the
log life to less than the default value of 7. This is not
explained.
CR: JAGab36133 SR: D500424820
Missing FROM line in MDN/DSN messages
CR: JAGab34757 SR: 5003453712
Ux gateway closes down when it gets a 571 return from SM.
It should just give a fail responce and carry on.
CR: JAGab35992 SR: D500417568
If a message with an incorrect addressee is sent into
Openmail via any 'incoming connection' protocol, e.g.
SMS2000I, no NDN is returned.
CR: JAGab35778 SR: D500401547
Distorted preview of message is shown in Intray if body text
of the message starts with English and then Japanese
characters follow.
CR: JAGab35772 SR: D500399246
Internet gateway can produce incorrect sender addresses
CR: JAGab34545 SR: 5003406132
It is possible to build omscan with the '-N' linker option.
This will allow omscan to have access to the 'text' internal
memory segment, as well as the 'data' internal memory
segment. This means that the should have access to more
memory during run-time, and so maxdsize can be bigger.
CR: JAGab34737 SR: 5003448654
If a message is sent to an address of the format:
//ex/us/mci/scjmail/rfc-822/rootbeast.mayfield.hp.com
ie. No name and no OU's but just CAPO attributes and DDA
fields
the Service Router will attempt to resolve the name even
though there is a valid route for the mailnode
//ex/us/mci/scjmail.
In certain circumstances this can cause huge delays in the
processing of the message.
This problem applies to any routable ORN that does not
contain a Surname field.
CR: JAGab32580 SR: D500426676
Server general.cfg:
UXI_TREAT_AS_MIME_SUBJECT=T UXI_UNIX_MAIL_CHARSET=UNIXJIS
UXO_MIME_OMIT_DEF_CTENC_HDR=T UXO_MIME_SUBJECT_ENCODING=B
UXO_MIME_SUBJECT_BENC_NONASCII=T UXO_MIME_SUBJECT_FOLDING=T
UXO_MIME_TEXTFILE_ENCODING=N
Clients: Outlook Express J, Outlook 98 Internet mode J,
Pocket Outlook Express
These clients generate ISO-2022-JP + B-encoding filename and
name fields. OpenMail can accept those filenames well, but
the outgoing Internet G/W lower cases the B-encoding
filename, so as a result, the filename will be garbage. For
some clients, it is not possible to download the file,
probably because of the filename corruption.
CR: JAGab34109 SR: 1653299974
A certain kind of Lotus CD document makes cd.browse loop.
CR: JAGab36221 SR: D500428029
Paper clip marks appear in Inbox when messages are sent as
Plain Text and contain multi-byte characters in the body
part, despite no attached files exist in the messages. This
happens with Japanese Outlook98, MAPI-SP5.30(beta) and
Windows 95 and NT4.0.
CR: JAGab36194 SR: D500426882
If a non-openmail file is found when scanning the sub domain
in omscan and it happens to be the first file in the
directory the an attempt to record the item is made with no
item information available.
CR: JAGab36236 SR: D500428953
The details listed for a newly attached message generated as
a result of a notification do not have the 'unread' flag
set. This causes the client (Outlook) to display the
message as already being read.
CR: JAGab36234 SR: D500428821
Netscape creates the mime message with no trailing blank
lines, which can be seen in the mime blob in the message
store. The Item browser then ADDS a blank line at the end
of the text message! Netscape then correctly says that the
message is altered.
CR: JAGab34968 SR: D500293266
omdirex import filters ending in a ")" character make
omdirex fail.
For instance, (OU1=pine)&(OU1=wood)
A UAL error (4500,3,16030) is reported. The 16030 means
mismatched parenthesis.
CR: JAGab32583 SR: D500427344
This problem asks for a more comprehensive fix to the
problem addressed in SR 1653287953.
If an item is added to a bulletin board and almost
immediately deleted. 2 synchronisation messages are
created. If these arrive out of order, the item may be
added and NOT deleted, because the first message attempts to
delete an item which does not exist.
omshowlog -l 7 should show a message similar to :
[OM 23989] Bulletin Board Synchronisation has attempted to
DELETE an item that doesn't exist yet on this system.
BUT, additional information should be supplied which will
allow the administrator to determine which Bulletin board
the item could not be deleted from and the message-id of the
item.
See related SR 1653287946.
CR: JAGab36055 SR: D500421016
omscan's orphan processing phase can now be frozen
in memory to avoid impacting other processes, and
re-started at a later time.
To freeze omscan :
kill -s SIGUSR2 #####
where ##### is the parent omscan process
(there are 2 processes)
To unfreeze omscan :
kill -s SIGUSR2 #####
CR: JAGab36239 SR: D500429050
The LDAP minidit example shuts down and restarts the slapd
server, as it changes the configuration. In some case, the
script could think that slapd had shutdown before it
actually had, causing the subsequent startup to fail. The
main affect of this is when the minidit is run repeatedly,
as in the autotests.
CR: JAGab34717 SR: 5003444901
omscan is terminating early with an 'ILLEGAL INSTRUCTION'.
The last thing that was logged was : SERIOUS ERROR
Administration(omscan ) 12.18.98 03:45:21 [OM 10250] Process
about to terminate due to error. Signal (Illegal
Instruction) trapped by process 288914; code = 0. Procedure
trace follows: <- scn_RecordItem -> im_FName2ItemRef ->
GetFNameElements <- GetFNameElements -> GetElementIndices <-
GetElementIndices -> os_str2ul <- os_str2ul -> os_str2ul <-
os_str2ul -> im_FormFullItemRef <- im_FormFullItemRef <-
im_FName2ItemRef -> scn_GetRecordedItem <-
scn_GetRecordedItem -> scn_RecordItem
CR: JAGab36230 SR: D500428318
VirtualVault - If an alias is specified for the
DEFAULT-OMSERVER or OMSERVER field in the change root
environment, Web Client 6.0 returns an error [SYS 1]Not
owner. Currently only IP addresses are accepted.
CR: JAGab36231 SR: D500428326
VirtualVault - The ownerships of the files in the change
root environment should be changed to bin:hpoffice, wherever
possible.
CR: JAGab34719 SR: 5003445072
After mulitple replies to a message from ccMail through
the Openmail Notes Gateway to Notes, the text becomes
double-line spaced.
CR: JAGab34136 SR: 1653303784
In patches to OpenMail B.05.10 after PP4 (B.05.10.D0) the
following problem occurs.
Create a new message Attach a local file to this message.
In the web page that is then displayed, there is a table
with attachment information. The field for the size of the
new attachment contains just the letter K. It should
contain the size of the attachment in kilobytes.
In more general terms, the %%KSIZE%% token used to return
the size of the attachment is blank.
CR: JAGab36242 SR: D500429183
notif.mon tries to allocate space for a huge number of file
descriptors because AIX says it can have that many.
CR: JAGab36241 SR: D500429175
On AIX version 4.3, the ldap tools, ldapadd, ldapsearch,...,
fail to connect to the host. This message is produced:
ldap_bind: Can't contact LDAP server
To date, this problem has only shown up on AIX 4.3 plus Y2K
patches. However, the OpenMail defect could in principle
have caused a similar problem on 4.3 without patches.
CR: JAGab34145 SR: 1653304717
The Item Browser fails when the filename of an attachement
contains a semi-colon (;). The Item Browser crashes causing
a Bus Error.
Defect Description:
PHSS_25646:
CR: JAGad83534 SR: 8606214343
This is an enhancement to the behaviour of the
auto-actions. Auto- redirect may now be controlled by two
directives from the config file; EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT. The values they take are 0
or 1. Before the introduction of this enhancement an
auto-redirect prevented other auto-actions from being
honoured. The first of these two directives ensures that if
any other auto-actions are enabled then they are honoured,
however the trigger message is delivered to the intray. The
second directive will delete the trigger message from the
intray.
CR: JAGad83915 SR: 8606214723
An empty auto-forward covering text string prevents the
file, held within the users g directory, which holds the
covering text from being generated. If this file is not
present the local delivery agent fails to forward the
message.
CR: JAGad83932 SR: 8606214740
The UAL checklist command did a check to see if the
specified address matched the internet address before
looking for a match on the X400 attributes.
If alternatives were found, then the list of alternatives
was compiled by researching the directory. however, the
search to create the list was only being done on the X400
attributes and no internet search was done on the internet
directory. This resulted in no matches being found and the
list being empty.
In addition, the internet search was done only on the
internet attribute. So if X400 attributes had been
specified, these were ignored when determining a match from
the internet directory.
CR: JAGad84893 SR: 8606215716
After processing a erroneous Return of Contents, the X400
outgoing gateway failed to clear a global data item. This
led to subsequent messages being incorrectly handled, and
rejected with 6019 log error numbers. Processing following
the detection of the 6019 errors failed to close the
transaction file of the message or distibution list, and
eventually the limit for the maximum number of open
transaction files was reached.
CR: JAGad84922 SR: 8606215745
An empty auto-reply covering text string prevents the file,
held within the users g directory, which holds the covering
text from being generated. If this file is not present the
local delivery agent fails to generate an auto-reply
message.
CR: JAGad87649 SR: 8606218500
The UAL_BBACL command that set Outlook permissions on
folders uses the ACL name checking code which (incorrectly)
will not allow the Common Name field to be specified with
other Mnemonic ORN fields. Eg. Teresa
Green/acme,sales/CN=tg will be rejected as an invalid
delegate name.
CR: JAGad88671 SR: 8606219531
The code in the X400 intrinsics, that processes non-textual
content items using the EMA BodyPart 15 rules, allocates
memory on a per message basis for a number of linked data
structures, and fails to release all of them at the end of
the message.
CR: JAGad90057 SR: 8606220921
When the message type is multipart/report, the message is
written out to a temporary file. The length of the line is
noted and if less than 1, an error is reported. If the
first character of a line is null, then the length is 0,
incorrectly causing a fatal error.
CR: JAGad91276 SR: 8606222161
The omupdtis code traps the SIGHUP and SIGTERM to allow
processing of the omupdtis command to be interrupted but
does not set a error return when this happens.
CR: JAGad93282 SR: 8606224187
The Named Property Id is incremented each time a named
property is generated. There is no check for the actual
maximum of FFFE, or for overflow at FFFF. So once the value
FFFE was exceeded, the named property id's take undefined
values.
CR: JAGad94888 SR: 8606225815
At VV4.5 root does not have the required authorisation
level to execute the setlevel command.
PHSS_25462:
CR: JAGad88889 SR: 8606219749
Extra spurious content is displayed for an IMAP client when
there are more that 9 top level contents. This is due to an
incorrect comparison of the content item number.
CR: JAGad90490 SR: 8606221356
Non-ascii NDN text from message catalogue is not given the
correct charset specification in the MIME header.
PHSS_24874:
CR: JAGad30137 SR: 8606160818
This form of message is not a multi-part message, and the
code that reads and processes the '.' terminator in this
case omitted to include the newline character in the check.
Hence the code attempted to continue to read stdin, and
hence the hang, as unix.in is waiting for more from
sendmail
CR: JAGad31466 SR: 8606162150
Exchange Connector resyncs were removing any
entry that had a non-addressing attribute changed on the
Exchange side - this was caused by the fact that the DS
entries coming from Exchange do NOT have a LID attribute so
the normal method of getting the entry using DA_SOURCE_LID
does not work.
CR: JAGad65896 SR: 8606196695
This was caused by an error in the code that scans Arpa
ORNs, when attempting to map domain names to Openmail
mailnodes using the unixmap.in configuration file.
CR: JAGad67601 SR: 8606198411
The code that is used to build the PDUs for outgoing X.400
messages is not under our control, we use XAPI libraries to
give us a higher level interface to ASN.1 structures and
independence from the underlying MTA. This code is not
particularly efficient and it uses quite large structures
in memory when a PDU is being contructed. In the case of a
message that has a Distribution List with 10,000 names it
will take a long time and use a lot of resources.
The fix for this problem is to add some general.cfg options
to replace large distribution lists with a single name
distribution list. This will not prevent the message from
reaching the intended recipients, but it will speed up the
transfer of the message through the X.400 gateway. If this
DL replacement occurs then the message cannot be
successfully replied to 'all' (as the original distribution
list has been removed).
The general.cfg options are:
X4O_MAX_DL_NAMES=n
where n is the maximum number of names allowed in a
DistList before they get replaced with a single stub DL
name. Default is the current behaviour... there is no
limit.
where the string contains the stub DistList name in
positional ORN format (each ORN field separated with a '/'
character). %s can be used in this string and will be
substituted with the number of names found in the original
DistList. For example: X4O_MAX_DL_NAMES=1000
X4O_MAX_DL_NAMES_ORN=DistList/%s-Name///Black/Hole
will produce a name that the user sees as:
TO: 1001-Name DistList /Black,Hole
when a DistList with 1001 names is send through the X.400
gateway. The default for this ORN string is:
DISTRIBUTION-LIST/%s-NAME///MAIL-SYS
CR: JAGad68810 SR: 8606199624
The fix for JAGab39939 (omfmtent produces illegal directory
entries for entries with null values) has caused omshowcda
to display the directory mask to be displayed differently.
CR: JAGad69543 SR: 8606200362
A coding defect within the item.browse binary resulted in a
failure while mime encoding a message.
CR: JAGad70640 SR: 8606201464
Some scripts supplied with OM-APPL specified the full path
name for the 'cut' command. They needed to be enhanced to
support a different location on some OS versions.
CR: JAGad71090 SR: 8606201916
Hidden items within the message store were included within
the item count when listing the tray or folder areas.
CR: JAGad73144 SR: 8606203966
The failure occurs after the license server sends the
request to the other license server, or when receiving the
reply. When scanning the shadow file, and a decaying
license is found in the shadow file before an active
license, the license server treats all following entries
as decaying, and eventually aborts.
CR: JAGad74715 SR: 8606205540
A coding error resulted in the mhsORAddress and omAddress
attribute being mapped only to the the Openmail S, S-TX, G
and G-TX attributes for the modify:replace option.
Consequently, when building the OpenMail modification data,
only the former surname and givenname attributes were
deleted and 2 values were supplied for OU1 and other
modified attributes.
CR: JAGad75038 SR: 8606205863
When processing ORNs, omaddent converts to T61 and then
breaks the ORN down into a set of T61 substrings. This may
mean adding some bytes (T61 characters) at the start of
each substring. For non-T61 values, these bytes are later
removed before the value is stored in the directory. This
defect was also removing bytes whose values are the same as
the T61 characters, but which were not added by the initial
parsing.
CR: JAGad75975 SR: 8606206802
Sendmail modifies entries of the form
user/"test <user/test>
to
"user//"test" <user/test>.
Openmail takes this and assumes that the second " ends the
quoted text, then the third quote opens further quoted text
and the To: input can become out of sync.
Further, it becomes possible for mangled addresses to be
greater in size that that expected causing a serious error
to occur.
CR: JAGad79081 SR: 8606209895
A coding defect in the IMAP Server does not take any
account of the special chars in OM Personal Names as input
and therefore fails to map them into those they represent.
PHSS_24095:
CR: JAGad40563 SR: 8606171299
The Root-URL is used initially when sending back the
Location: header on signon. The SERVER-PROTOCOL environment
variable is used to construct part of the URL. It appears
that the Apache web server sets the SERVER-PROTOCOL
variable to HTTP/1.0 regardless of whether you are talking
HTTP or HTTPS, however it identifies the fact that we are
talking HTTPS by setting the environment variable
HTTPS="on"
CR: JAGad44030 SR: 8606174784
The item browser fails to convert UTF8 to ISO8859_1 when a
message is in MIME format, even though a converter exists.
It recognises that a converter exists, but fails to convert
the UTF8 characters to UCS2 first in the case of the MIME
format. The conversion is then incorrect. In the case of
non MIME text, this two stage conversion is completed
successfully.
UNICODE conversions for MIME formatted messages are not
generally supported in OpenMail and so the 2 step
conversion required had not been implemented.
CR: JAGad45881 SR: 8606176644
The attempted deletion of an attachment in a user's intray,
using a pointer to a null container entry, resulted in a
segmentation violation and the subsequent premature abort
of omcontain.
CR: JAGad46439 SR: 8606177205
The General Text handling code at the incoming X400
interface was written on the assumption that the
interchange charset for non-Latin-1 single byte languages
would be based on an ISO8859_n charset, as used in General
Text bodyparts.
When the Czech version of OpenMail was done, it was decided
to use T61BASE as the interchange charset. However, the
X400 incoming mapper was not changed to properly convert
and map the bodyparts.
CR: JAGad47890 SR: 8606178664
Incorrectly configured vir*s scanning library was causing
messages containing vir*s to not be scanned and potentially
cleaned.
CR: JAGad50818 SR: 8606181602
When the OMGUI processes a reply, it takes the Distribution
List of the original message and supplies it to UAL
Checklist, requesting Lookup of the 167 attribute in the
UnixMap directory for ORNs that have a group 5 internet
address field.
Messages received from GR7 may contain the internet address
of Openmail users as well as of internet users. If the GR7
internet addresses are not present in the directory of the
server where the reply is constructed, the 167 lookup will
fail to find a match. The code then assumes the recipient
is an internet user and adds the address of the internet
Gateway to the ORN.
CR: JAGad55411 SR: 8606186206
The segmentation violation in the Notification Monitor is
caused by dirty data in a buffer which then causes a buffer
under-run or over-run to then occur. This dirty data
appears to be generated by a large number of
deregistrations for notifications which happens when the
RCI is shut down and timing problems cause a write to the
buffer to be killed thus generating the dirty data which is
then read. The current write is in two stages with the
possibility that the process can be terminated inbetween
these two writes.
CR: JAGad56484 SR: 8606187277
Currently the client does not set up a filter on the
Outlook delegate redirection to prevent private items being
redirected.
The best solution to this problem is to change the server
code so that by default a private Outlook meeting request
will NOT be redirected to a delegate. This behaviour can be
overridden by the LD_SENSITIVE_ITEM_DELEG_REDIR=TRUE
config option (user.cfg and general.cfg)
CR: JAGad56620 SR: 8606187413
Subject is not currently matched (via user-supplied script)
if the subject of the message is null (blank).
The fix is to change the code to allow a blank subject to
be matched. The old behaviour will be reinstated by setting
the RSL_MATCH_BLANK_SUBJECT=FALSE
general.cfg option.
CR: JAGad57754 SR: 8606188546
Porting changes for Linux have caused a problem with the
EINTR signal handling to become visible in the syslog.
EINTR signal handling corrected so that this interrupt is
silently swallowed.
CR: JAGad58840 SR: 8606189626
The failure to download the directory was caused by a
buffer overflow when reading in a large directory entry in
order to pass them to the client.
CR: JAGad64229 SR: 8606195023
The patch installation scripts contained hard-coded exit
codes of 0, 1 and 2, instead of the preferred $SUCCESS,
etc. Also, there were some cases where values other than 0,
1 or 2 could be returned.
CR: JAGad64671 SR: 8606195467
in.imap41d was going into a spin in the function imapsearch
because although conn->state was set to TERMINATED when the
ual socket had died this was not checked for.
PHSS_24029:
CR: JAGad48440 SR: 8606179216
A coding defect in the brw component assumes that text
messages without a specifed CharSet are 7-bit text.
CR: JAGad57988 SR: 8606188772
A coding defect in the brw component results in message
headers, containing 8-bit chars, being counted twice in
computing the total SIZE of message. This incorrect SIZE
causes the Netscape IMAP client to become confused and to
give up displaying as a message and revert to just
displaying the MIME Source.
CR: JAGad63387 SR: 8606194177
The cause of this failure was due to incorrectly parsing
the Content-Disposition response header which sometimes
resulted in corrupted memory.
PHSS_23726:
CR: JAGad53837 SR: 8606184631
A coding defect in the ct component causes an
inconsistancy, in respect of MIME boundary markers, in a
message when it is copied from one folder to another.
However only Netscape on displaying larger messages is
affected by this discrepancy. It is lead to believe that
the copied message's boundary markers are those of the
message from which it was copied.
PHSS_23343:
CR: JAGab33574 SR: 1653231704
A recipient-processing library call, was trying to perform
a copy of a NULL ORN string.
CR: JAGab39939 SR: 8606100957
The parser does not take into account the case when there
is an attribute name but no attribute value.
CR: JAGab68963 SR: 8606102906
When a Repeat Reminder is set, the message is placed in the
message list DEFER.UA by the UAL. While calculating the
next submission date-time of the message, the final
reminder date is calculated based on the current date and
the value of the current reminder.
If the next submission date of the reminder message is less
than the final reminder date, then the message is placed on
the Service router for routing. Otherwise it is deleted
from the message list, so that no more repeat reminders
will be sent. But since the final reminder date is
calculated using the current date the submission date is
ALWAYS less than the final reminder date.
CR: JAGad24268 SR: 8606154951
A coding error in the item structure server was causing it
to sometimes corrupt the item references it was reporting.
CR: JAGad31664 SR: 8606162348
The Outgoing Internet Gateway is confused by addresses that
can be generated by the cc:Mail client, such as :
"S=Friendly Name .gren/OU1=mime/
DDT1=RFC-822/DDV1=Friendly Name <grennowhere.hp.com>/
INTERNET-ADDR=Friendly Name <grennowhere.hp.com>"
===========================================================
A coding defect in the ux component tries to enclose the
"Comment <userdomain>" within angle brackets <>, by only
inserting a start bracket < at the beginning, before
passing it to Sendmail, resulting in unmatched brackets,
which naturally generates a Sendmail error.
CR: JAGad35090 SR: 8606165799
The algorithm used to select the approprate user's message
store to restore selects the last message store that
matches just the name part of the user's address.
CR: JAGad38822 SR: 8606169547
A coding problem in ual.remote causes the Content
Disposition and Content ID fields of a mesage to become
corrupt when forwarding/replying to email using Ccmail 6.*
clients.
CR: JAGad41463 SR: 8606172203
The omshowapp script was not being run appropriatly as it
needs to be run under ksh on solaris.
CR: JAGad41471 SR: 8606172211
A segmentation fault occures when parsing a blank line at
the top of the mnMapFile which is located in the
varOMBINDIR/sys directory.
CR: JAGad41637 SR: 8606172377
The delegates unix id and unix username were used when
signing on but the openmail id was not. This meant that
when the change went in to use user.cfg files by openmail
id and not unix id that the wrong file was checked.
CR: JAGad42631 SR: 8606173373
If an orphan message is deleted during the omscan process,
an attempt to open the orphan message causes the error
message OM [1209].
CR: JAGad43052 SR: 8606173797
The IMAP daemon was not converting MIME subject before
copying an item into the OpenMail message store.
CR: JAGad43053 SR: 8606173798
This problem is caused by the IMAP server daemon failing to
convert content the character set from MIME to OpenMail
when appending a file to the OpenMail message store.
CR: JAGad44810 SR: 8606175570
Certain characters ,=/ when placed within the FF field get
escaped with the backslash character
When a backslash character is present with the address
field (ORN field) and the user validates the name and tries
to send a message to that adddress then the error "name is
not routable is displayed".
CR: JAGad45449 SR: 8606176209
When a folder is listed (UAL_PRPLST/UAL_LIST) any messages
in the list that not have TextPreview data setup get it
dynamically generated. This causes the ModifiedDate in the
ctner to be updated. This updated ModifiedDate in the ctner
means that the sync. process treats this as a conflict. The
fix is to suppress the ModifiedDate update for this
behind-the-scenes modification. As far a synchronisation
goes the TextPreview is a 'computed' field, dynamically
created in an offline store and is not synchronised data-
so this change is good both architecturally and
pragmatically.
CR: JAGad45880 SR: 8606176642
The attempted encoding of a ' ' character followed by a
'n' as the 1015 and 1016 characters of a line in an html
attachment resulted in the premature abort of the
item.browser and a subsequent segmentation violation.
CR: JAGad46896 SR: 8606177664
A coding defect in the ux component tries to run off the
end of the temporary file holding the Multipart/Signed part
of the Sendmail message, when this part has missing
end-boundaries of composite contents types, Multipart or
Message.
CR: JAGad48103 SR: 8606178878
Some changes introduced to omdosur as part of the 5.20 MAPI
work, was failing to take into account the possibility of a
missing container.
CR: JAGad49581 SR: 8606180360
Files i4target_ux10 and i4target_ux11 were missing from CR
JAGac29290.
PHSS_23082:
CR: JAGad41842 SR: 8606172582
The UAL_GETSYNC routine does not extract T.61 content
correctly and the resulting content file does not undergo
any character set conversion so the data remains as T.61.
CR: JAGad42033 SR: 8606172773
Move from Inbox is really a copy and delete and the
generation of the DirectRef for the moved item must be
delayed until after the move in order to get the correct
value.
CR: JAGad42115 SR: 8606172855
Update of Local FreeBusy information is caused by the
removal of the Local FreeBusy property for the user and the
generation of a notification that the Local FreeBusy
message has been modified. This causes the Local FreeBusy
information to be regenerated and rewritten by the Outlook
client.
There are some circumstances when there is no FreeBusy
information present and this fact meant that the Local
FreeBusy message was not modified and therefore no
notification was generated and the FB info was not
regenerated.
CR: JAGad42645 SR: 8606173387
For a synchronisation the calculation of where the first
newly attached sync. message at the end of a large folder
can be incorrect if items near the end of the folder have
been deleted.
CR: JAGad42878 SR: 8606173621
Modified offline item generates and explicit GET_ITEM
command with the sync. actions. If this item does not exist
on the server a spurious error is generated in the
UAL_GETSYNC action file.
CR: JAGad44420 SR: 8606175176
If OFS has been enabled by an Outlook user then there are
occasions when the OFS change log will contain information
about items that are no longer present in the message
store. Handling such change log entries is causing the
WARNINGs to be generated even though no error has occurred.
These WARNINGs should be downgraded to minor events.
This behaviour is especially likely to occur when a message
is being constructed by Outlook and the message gets
automatically saved to the Drafts folder (by default after
3 minutes) before the message is mailed.
PHSS_22996:
CR: JAGad29260 SR: 8606159934
A coding error in the notes.out part of the Notes Gateway
resulted in blank From:, To:, Cc: or Bcc: entries being
dropped without adjusting the accompanying counts of said
entries.
PHSS_22991:
CR: JAGad42968 SR: 8606173711
A design defect in the mim component restricts the search
for an internet address within an ORN to the ordinary DDA
fields of the ORN. However an 8-bit address is stored in a
teletex DDA-TX field, which is ignored by this search and
so the internet address is effectively discarded.
PHSS_22700:
CR: JAGad21983 SR: 8606152653
UXO_CHECK_TYPES_OF_DDA synonyms for DDT1 setting are not
treated in exactly the same way as RFC-822.
CR: JAGad25146 SR: 8606155833
The file of new users previously contained only usernames;
ie. nowhere for aliases to be specified.
The format of this file has been extended to allow
specification of aliases. The file format is described in
the new man page for omaddu, which is part of this fix.
Note that it is not possible to specify aliases when using
the '-u' option with '-bulk'. Aliases can only be specified
in an input file to omaddu -bulk.
CR: JAGad25316 SR: 8606156005
When handling the SIGCLD or SIGCHLD signals on an Ensim
Linux machine, the SIG_IGN fails causing zombie (<defunct>)
processes to be created. These processes remain on system
exhausting process ids. These zombie processes are only
removed when the parent process is closed down.
The zombie (<defunct>) processes can also cause the parent
process to hang using large amounts of CPU.
CR: JAGad26547 SR: 8606157213
omlimit functionality was altered in a way which required
new messages, however, these messages were not localised.
CR: JAGad27572 SR: 8606158242
When Eudora sends an "application/mac-binhex40" file to a
Unix internet account, the attachment has the following
MIME information with it :
Content-Type: application/mac-binhex40;
name="Birkenstock.doc" Content-Disposition: attachment;
filename="Birkenstock.doc"
and the file is not encoded.
A message sent to an OpenMail user in the same way has the
following MIME information when the message is browsed by
an IMAP or POP3 client :
Content-Disposition: attachment; filename="Birkenstock.doc"
Content-Type: application/mac-binhex40;
name="Birkenstock.doc" Content-Transfer-Encoding: base64
and the file IS encoded.
Clients like Eudora ignore the encoding and assume the file
has not been encoded. For instance, when opening a Word
document, Eudora 5 and earlier will open the file before
removing the encoding.
CR: JAGad28647 SR: 8606159318
A coding defect, introduced when Vir*s Rule Sets were
introduced, in the Rules Sets component of the Service
Router was causing this process to unnecessarily expand its
memory with increasing number of requests, when the Default
Vir*s file was activated.
CR: JAGad28840 SR: 8606159513
Various inconsistencies identified in the code within
function definitions or calls.
&nb