|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 800 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun Jun 08 2003 - 14:15:51 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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://support.itrc.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://support.itrc.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 800 11.X patch digest
Created: Sun Jun 8 7:05:11 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHNE_29244 s700_800 11.04 (VVOS) EISA 100BT cumulative patch
PHSS_29066 s700_800 11.X OpenMail B.07.00 June 03 Periodic Patch
PHSS_29064 s700_800 11.X OpenMail B.06.00 June 03 Periodic Patch
PHSS_29057 s700_800 11.04 Virtualvault 4.6 SSH expired password change
PHSS_28667 s700_800 11.X OV ITO7.1X DataComm Component Solaris A.07.12
PHSS_28461 s700_800 11.00 OV OST3.12 Cumulative A.03.12 patch
PHSS_28453 s700_800 11.X OV ITO7.1X DataComm Component AIX A.07.12
PHNE_28799 s700_800 11.11 100BT unified driver cumulative patch
PHKL_27947 s700_800 11.00 JFS 3.3 Sticky-bit;read ahead;vx33_maxlink
PHSS_29206 s700_800 11.X OV NNM6.2 Intermediate Patch, May 2003
PHSS_29135 s700_800 11.X OV DP5.00 patch - SSEA packet
PHKL_28557 s700_800 11.11 I/O,PA 8700 2.2,vPar,PCI-X,CDUMP,IM perf
PHCO_28672 s700_800 11.11 diff3(1) cumulative patch
PHSS_28951 s700_800 11.X OV ITO7.1X Msg/Act Linux Agent A.07.20
PHSS_28827 s700_800 11.22 Aries cumulative patch
PHNE_28895 s700_800 11.11 cumulative ARPA Transport patch
PHKL_28265 s700_800 11.11 Compressed Dump enablement
PHKL_28263 s700_800 11.11 Compressed Dump enablement
PHKL_28244 s700_800 11.11 Compressed Dump enablement
PHKL_28239 s700_800 11.11 Superdome early dump fix, CDUMP enablement
PHKL_28238 s700_800 11.11 VxVM,EMC,Psets&vPar,slpq1,earlyKRS,CDUMP
PHKL_28237 s700_800 11.11 vPar enablement, CDUMP enablement patch
PHCO_28243 s700_800 11.11 crashutil cumulative, CDUMP enablement
PHCO_28242 s700_800 11.11 Compressed Dump enablement
PHCO_28241 s700_800 11.11 savecrash cumulative, CDUMP enablement
PHCO_28240 s700_800 11.11 Compressed Dump enablement
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHNE_29244
Date Loaded: 20030605
Title: s700_800 11.04 (VVOS) EISA 100BT cumulative patch
Patch Name: PHNE_29244
Patch Description: s700_800 11.04 (VVOS) EISA 100BT cumulative patch
Creation Date: 03/05/29
Post Date: 03/06/05
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
EISA100BT B.11.04.01 B.11.04.02 B.11.04.03 B.11.04.04
Filesets:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_29244: PANIC
Based on PHNE_28636: PANIC
Based on PHNE_27534: PANIC ABORT
lanadmin(1M) command aborts when querying
EISA 10/100BT interface with '-ax' options.
Based on PHNE_24725: PANIC
PHNE_25070: HANG
Based on PHNE_23981: HANG
PHNE_22985: PANIC
Based on PHNE_19200: PANIC
PHNE_18790: PANIC
Based on PHNE_16154: PANIC
Based on PHNE_13543: OTHER
Multicast & Promiscuous mode not working
Category Tags:
defect_repair enhancement general_release critical panic
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_29244
Symptoms:
PHNE_29244:
Repackage of HP-UX patch PHNE_28636 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_28636:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
2. ( SR:8606289350 CR:JAGae53281 )
When the lanadmin(1M) command is used with the "-x"
option to query the EISA 10/100BT interface, the system
may panic.
HP1_ospif_dlpi_ioctl+0x9f0
hp_dlpi_process_ioctl+0x268
hp_dlpi_wput+0x5ec
putnext+0x16c
wait_iocack+0x6c
str_istr_ioctl+0x698
hpstreams_ioctl_int+0x3d4
hpstreams_ioctl+0x50
spec_ioctl+0xb0
vno_ioctl+0x8c
ioctl+0x258
syscall+0x1c8
Based on HP-UX patch PHNE_27534:
1. ( SR:8606188846 CR:JAGad58062 )
EISA 10/100BT card experiences multiple internal resets
with the following message logged to NetTL log file.
"bdm_watchdog: TX did not complete on time, resetting
adapter btlan01".
2. ( SR:8606248819 CR:JAGae15216 )
EISA 100BT driver panics with "Data page fault" in
_bigmac_cmdfmt_tx().
3. ( SR:8606266748 CR:JAGae30993 )
lanadmin(1M) command core dumps when querying
EISA 10/100BT interface with "-ax" option.
Based on HP-UX patch PHNE_24725:
1. EISA 100BT driver panics with "Data Page Fault" in
bdm_rcv_buf_alloc(). -- JAGaa45963
PHNE_25070:
port of HP-UX patch PHNE_23981 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_23981:
1. EISA FDDI driver hangs because of EISA 100BT's
bus locking. -- JAGad50169
2. Reproducible system hang in oim_open() when
starting SAP. -- JAGad54480
3. suid bit set to lanadmin library. -- JAGad67830
PHNE_22985:
port of HP-UX patch PHNE_19200 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_19200:
1. EISA100BT sends corrupted MAC address for DLPI
test-xid requests. -- JAGaa41098
2. linkloop to self doesn't return error when cable is not
connected. -- JAGab03857
3. IP multicast datagrams looped back in the driver.
-- JAGaa41968
4. EISA100BT driver doesn't set ifOper status correctly
in the MIB structure. -- JAGaa21367
5. Some required EISA100BT structures are not available
for Q4. -- JAGaa21642
6. Automatic speed configuration doesn't work for EISA100BT.
-- JAGab46349
7. EISA100BT start-up doesn't give a warning when set to
full duplex. -- JAGaa21652
8. Setting the speed is not possible in hpeisabtconf file.
-- JAGab65054
9. nettl traces are not formatted correctly. -- JAGab64926
10. Minimum frame length in 10BT mode should be 60 bytes
instead of 64 bytes. -- JAGab64392
11. ER: Allow the MTU size configuration using lanadmin.
-- JAGab64413
12. ER: IOCTL support is required for speed and duplex
setting using SAM. -- JAGab64697
13. EISA100BT generates duplicate packets under heavy load.
-- JAGab64911
14. Service Guard doesn't work with new interface naming
convention. -- JAGab64435
15. Startup script does not allow for non-sequential arrays.
-- JAGab70575
16. Panic with 'Already Owns this Spinlock' on EISA 100BT.
-- JAGab68637
17. "lanadmin -S 0" command hangs.
-- JAGab72670
18. DLPI primitive to set physical address succeeds even
for invalid values -- JAGab84309
19. Driver does not return error for invalid multicast
addresses. -- JAGab84311
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. -- JAGad09607
PHNE_18790:
Repackage HP-UX patch PHNE_16403 for VVOS.
Based on HP_UX patch PHNE_16403:
1. Performance degradation.
Based on HP-UX patch PHNE_16154:
1. EISA 100BASE-T card does not come up on 715/100/E
workstations.
2. When there is heavy network traffic, EISA 100BASE-T
card does not come up at boot time.
3. EISA 100BASE-T panics on D and C class with Data
Page fault under heavy load.
Based on HP-UX patch PHNE_13543:
1. SAP promiscuous mode and layer2 multicast are not
supported.
2. EISA 100BT returns current MAC address to a factory
MAC address request.
3. Startup scripts to alter the MAC address or the
duplex mode will not function.
Defect Description:
PHNE_29244:
Repacakged HP-UX patch PHNE_28636 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_28636:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
Resolution:
Adequate frame padding is done.
2. ( SR:8606289350 CR:JAGae53281 )
When EISA 10/100BT interface self-test fails, a field in
the driver data structure is not initialized properly.
The system panics when the lanadmin(1M) command with
"-x" option tries to access this uninitialized field.
Resolution:
Proper check has been added to avoid accessing
uninitialized field in the driver data structure.
Based on HP-UX patch PHNE_27534:
1. ( SR:8606188846 CR:JAGad58062 )
The "Command Unit" of the EISA 10/100BT card goes into
an "IDLE" state even when there are packets queued up
for transmit. This would cause the card to be unaware
of new packets posted for transmission resulting in
bdm_watchdog timer going off thus triggering a card
reset.
Resolution:
If the "Command Unit" has gone into "IDLE" state and
transmit queue is not empty, then the "Command Unit" is
restarted in bigmac watchdog routine.
2. ( SR:8606248819 CR:JAGae15216 )
In response to EISA 100BT driver's dump command request,
the card's internal registers have to be dumped on to the
host's preallocated memory location. Instead, the data
was written on to the transmit descriptor thus corrupting
the transmit descriptor ring.
Resolution:
A separate descriptor has been allocated for the dump
command.
3. ( SR:8606266748 CR:JAGae30993 )
Parameter returned to "lanadmin" was not properly
initialized in EISA 100BT driver shared library.
Resolution:
Return parameter is initialized.
Based on HP-UX patch PHNE_24725:
1. Under heavy load driver was corrupting free buffer list.
Later when driver tries to allocate memory in
bdm_rcv_buf_alloc() it was panicing with data page fault.
Resolution:
Code has been modified to take care of this situation.
PHNE_25070:
Port HP-UX patch PHNE_23981 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_23981:
1. EISA 100BT was holding bus unnecessarily because of
which EISA FDDI driver was hanging.
Resolution:
Unnecessary bus locking has been removed.
2. In the oim_open() function, a linked list was
processed improperly in a while loop.
Resolution:
Processing of the linked list has been modified in
the while loop.
3. The lanadmin library was set with suid bit.
Resolution:
File permissions have been modified.
PHNE_22985:
port of HP-UX patch PHNE_19200 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_19200:
1. An upper layer didn't set the source MAC address
while passing the packet to the driver and driver
expected MAC address to be set by upper layer.
Resolution:
Modified transmit path to copy source MAC address
for outbound packets.
2. Driver was not checking interface status for
loopback packets.
Resolution:
Code is modified to check interface status before
looping back the packet.
3. Driver didn't check whether it needs to loop back
the multicast packet to the local host.
Resolution:
The code was modified to check whether driver needs
to loop back the multicast packet.
4. EISA100BT driver was not consistent in setting ifOper
Status in the MIB with respect to lanscan.
Resolution:
Modified code to have consistency for lanadmin &
lanscan states.
5. Some required EISA100BT structures are not available
for Q4.
Resolution:
Added the necessary structures that are required for
Q4 support.
6. EISA100BT start-up script was not passing the speed
value to the 'lanadmin' command.
Resolution:
Start-up script was modified to pass the speed value
to the 'lanadmin' command.
7. EISA100BT start-up script didn't check for full duplex
mode setting.
Resolution:
Added a check for invalid duplex mode.
8. hpeisabtconf file didn't support SPEED variable.
Resolution:
Added SPEED variable in hpeisabtconf file.
9. EISA100BT subsystem formatter was not able to
format the packets properly.
Resolution:
Rewrote the subsystem formatter to fix formatting
problems.
10. EISA100BT driver supported a minimum packet length
of 64 bytes in 10BT mode instead of the standard 60
bytes.
Resolution:
Modified the driver to support a minimum packet
length of 60 bytes instead of 64 bytes.
11. ER: Allow the MTU size configuration using lanadmin.
Resolution:
Added new IOCTL requests to support set/reset MTU
values.
12. ER: IOCTL support is required for speed and duplex
setting using SAM.
Resolution:
Modified driver to support additional ioctl requests
that are required for SAM support.
13. EISA100BT card was sending duplicate packets under
heavy UDP traffic.
Resolution:
Modified transmit path to flush/purge the data in the
cache and synchronized shared memory access between
card and memory.
14. While changing the driver to new naming convention,
the ifDescr MIB variable was not modified to reflect the
same.
Resolution:
Modified the ifDescr MIB variable to use the new naming
convention.
15. Startup script was not able to recognize interface
entries in non-sequential order in file
/etc/rc.config.d/hpeisabtconf
Resolution:
Startup script is modified to process all interface
entries in file /etc/rc.config.d/hpeisabtconf, even
if they are in non-sequential order.
16. The panic happens when the driver receives a
SET_SPEED ioctl when there are pending inbound
packets.
Resolution:
Modified the code to release lock and
reclaim it again after processing pending inbound
packets.
17. Driver used to return negative value for invalid speed
values, due to which DLPI sleeps, and hence the lanadmin
command used to hang.
Resolution:
The driver now returns EINVAL to DLPI in case of an
invalid speed value.
18. The DLPI primitive to set physical address succeeds
even for invalid values (all bits 0's or 1's).
Resolution:
A check has been added for these invalid addresses.
19. Driver returns success for invalid multicast hardware
addresses which do not have the least significant bit
of the first byte set.
Resolution:
A check is now made to ensure that this bit is set.
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. Card was sending a loop back
packet to sense speed with new MAC address and was
not getting this packet back.
Resolution:
Card will send a loop back packet with Factory MAC
address to sense speed. After loopback test card
will be set with new MAC address.
PHNE_18790:
Repackage HP-UX patch PHNE_16403 for VVOS.
Based on HP-UX patch PHNE_16403:
1. A busy-wait in the performance path caused the
performance degradation.
Based on HP-UX patch PHNE_16154:
1. The driver did not set the speed correctly in 10Mb mode.
This occurred mainly on 715/100/E systems.
2. The driver sent a loopback packet without sensing the
media speed. The default speed was set to 100Mb. So,
under heavy network traffic the driver failed to receive
the loopback packet in 10Mb mode.
3. The driver did not do proper MP synchronization.
Based on HP-UX patch PHNE_13543:
1. Specific code for support of Promiscuous mode, layer2
multicast did not exist.
2. Returned incorrectly the current MAC address instead
of factory MAC address.
3. Wrong variable name in hpeisabtconf.
Enhancement:
No (superseded patches contained enhancements)
PHNE_25070:
Please review the Defect Description text for more
information.
PHNE_22985:
Based on HP-UX patch PHNE_19200:
- Allow the MTU size configuration using lanadmin.
- IOCTL support is provided for speed and duplex
setting using SAM.
PHNE_18790:
Based on HP-UX patch PHNE_16403:
- Performance improvement was made.
SR:
8606180948 8606185278 8606198641 8606164026 5003397125
5003451450 5003440230 1653289090 1653296236 4701430116
5003434928 1653311423 8606103630 8606102706 8606104897
8606112070 8606112072 8606140285 1653275446 1653264465
1653267237 1653263970 1653253013 1653250639 1653249318
8606188846 8606248819 8606266748 8606289350 8606294055
Patch Files:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat
/usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/sbin/hpeisabt_init
/usr/newconfig/etc/rc.config.d/hpeisabtconf
/sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.02,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.03,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.04,
fa=HP-UX_B.11.04_32,v=HP:
/usr/lib/libeisa100btfmt.sl
/usr/lib/nls/msg/C/fmteisa100bt.cat
what(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan0.a:
FILESET EISA100BT: libbtlan0: Version: B.11.00.07 P
HNE_28636 $Date: 2003/02/07 21:50:53 $
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat:
None
/usr/lib/lanadmin/libdsbtlan0.sl:
EISA100BT LANADMIN: libdsbtlan0: Version: B.11.00.0
7 PHNE_28636 $Date: 2003/02/07 22:22:54 $
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/sbin/hpeisabt_init:
None
/usr/newconfig/etc/rc.config.d/hpeisabtconf:
None
/sbin/init.d/hpeisabt:
None
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
/usr/lib/libeisa100btfmt.sl:
EISA100BT NETTL: libeisa100btfmt: Version: B.11.00.
07 PHNE_28636 $Date: 2003/02/07 22:25:57 $
/usr/lib/nls/msg/C/fmteisa100bt.cat:
None
cksum(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
1121102905 309392 /usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
3862894740 3138 /usr/lib/nls/msg/C/dsbtlan0.cat
1455904787 36864 /usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
780528253 5258 /usr/sbin/hpeisabt_init
340626021 1254 /usr/newconfig/etc/rc.config.d/hpeisabtconf
2418239947 7667 /sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
1526256771 16384 /usr/lib/libeisa100btfmt.sl
3989282158 5124 /usr/lib/nls/msg/C/fmteisa100bt.cat
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHNE_18560
s800: 11.04: PHNE_18560
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_18790 PHNE_22985 PHNE_25070
Equivalent Patches:
PHNE_28636:
s700: 11.00
s800: 11.00
Patch Package Size: 190 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 PHNE_29244
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_29244.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_29244. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
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 PHNE_29244.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_29244.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_29244.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. A new copy of the hpeisabtconf file is provided
under the directory /usr/newconfig/etc/rc.config.d.
This new hpeisabtconf is modified to support new
speed/duplex setting options for startup script.
Copy this configuration file and incorporate any
previous modifications to the
/etc/rc.config.d/hpeisabtconf file to this new
copy and replace the working configuration file
/etc/rc.config.d/hpeisabtconf with it.
-----End of Document ID: PHNE_29244------------------------------------------
Document ID: PHSS_29066
Date Loaded: 20030604
Title: s700_800 11.X OpenMail B.07.00 June 03 Periodic Patch
Patch Name: PHSS_29066
Patch Description: s700_800 11.X OpenMail B.07.00 June 03 Periodic Patch
Creation Date: 03/05/14
Post Date: 03/06/04
Hardware Platforms - OS Releases:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
Products:
OpenMail B.07.00
Filesets:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-X400,fr=B.07.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_29066
Symptoms:
PHSS_29066:
CR: JAGae59759 SR: 8606296148
When an Asian user on GR6 browses a NDN msg using an IMAP
client, the NDN is displayed in English, not in the user's
local language, with the non-delivered recipient name being
corrupted and truncated, as in :-
imaizumi-ma 15=;
and the following error is logged a few times to the
'fatal' log file:-
[OM 16130] Unable to open localised attribute tag file for
interchange character set ISO8859_1.
Additionally, if the user is on a mailnode with TTX
attributes, the Item Browser may go into a loop continually
logging many ERROR [OM 16130]'s. On GR6 this causes the
IMAP client to hang when the msg is viewed and the
mailstore filestore to fill up with work files.
For GR7, IMAP browsing is carried out using the newer Mime
Browser which does not exhibit this problem.
CR: JAGae62810 SR: 8606299316
If an attempt is made to install an OpenMail patch on a
system which does not have the base OpenMail product
installed, an ERROR status is returned in swagent.log. On
an HP-UX 11.11 system, it would be more appropriate to
return an EXCLUDE status.
CR: JAGae70969 SR: 8606307934
An item has the content line "Content-Type: text/html;
charset=" - i.e. is the character set value is NULL. The
following IMAP command is given.
". UID FETCH 1 (FLAGS)"
The flags are displayed correctly.
The further IMAP command is then given
". UID FETCH 1 (rfc822.size)"
This causes the response "NO some of the requested messages
no longer exist", and the size information is not
displayed. This also happens other requests of header
information.
CR: JAGae70977 SR: 8606307942
A user has a number of corrupt mail items. When the IMAP
command ". UID FETCH n (rfc822.size)" is issued for any one
of these items, the following response is given
"NO some of the requested messages no longer exist".
and so the mail item is not displayed.
However, these items can be displayed using other clients.
The only data displayed is the "subject", but a user is
then able to delete these items from their mail box.
It was also noticed that omscan does not detect these items
as being corrupt.
CR: JAGae70980 SR: 8606307945
When some mail items, containing a folder item, are viewed
from an IMAP client, the content is lost.
The item browser fails to return the requested message
content, and so the IMAP DAEMON responds with
"No some of the requested messages no longer exist"
when an IMAP "UID FETCH (BODY[1.MIME])" command is given.
CR: JAGae70984 SR: 8606307949
After some messages have become corrupt, the UAL
GET_OBJFILES command returns a corrupt object file. When an
attempt is made to create the body structure from the data
in this corrupt file, the IMAP daemon child process hangs.
The following response is given
"NO some of the requested messages no longer exist"
and only the messages up to the point of the corrupt one
are displayed.
CR: JAGae70985 SR: 8606307950
Sometimes the UAL returns no absolute value for delivery
acknowledgements. IMAP uses the absolute value to assign
the UID value, and is assigning a value of 0 in these
cases. Attempting to access an item with a UID value of 0
doesn't work, as the IMAP daemon see this as an invalid
value. So the following response is given
"NO some of the requested messages no longer exist"
and the mail item is not displayed.
As an example, if items 1 and 3 have UID values of 0, then
the IMAP command ". UID FETCH 1:4 (FLAGS)" processes items
2-4, whereas the command ". UID FETCH 1,2,3,4 (FLAGS)"
processes items 2 and 4. This is inconsistent.
The presence of items with 0 UID values can confuse clients
such as Netscape 4.7. This client seems to issue a fetch
command with a UID 2 greater than he actual value in the
above case.
CR: JAGae72697 SR: 8606309822
User is logging-in to GR7 using OMGUI with LocalCharSet, in
OMGUI.INI, set to an Asian CharSet.
If the user mistypes his password by including an 8-bit
non-ASCII char, then he gets an error "Login Failed: The
connection to the server has been lost ..." (1801-1038)
instead of the usual "Login Failed: Server Error 655.
Password supplied is incorrect" (1801-1009)
The UAL Remote Client Interface crashes, after logging
events like :-
WARNING [OM 24142] Conversion from SJIS to ISO8859_1 not
found.
WARNING [OM 24146] A character set conversion has failed.
WARNING [OM.UI 408] Error reported by cvc_ConvertString:
SJIS -> ISO8859_1
SERIOUS ERROR [OM 10270] Process about to terminate due to
error. Signal (Bus Error) trapped by process 13938
PHSS_28592:
CR: JAGab82932 SR: 8606110229
When an Outlook created msg with embedded image, is sent
over the Internet, the image is no longer visible to a
recipient, on a non-Linux server, using Outlook. Instead,
it is replaced by a BINARY file "Untitled Attachment" which
is not executable, even if it is first saved as a file with
the correct extension. In fact it is not even in the
correct format for its application, Paintbox.
Also occurs with embedded .XLS spreadsheets and probably
any other type of file that can be embedded in the main msg
body. It does not seem to happen with embedded Word .DOCs,
probably because RTF is capable of representing these
entirely.
Problem does not appear when same msg is sent internally to
OM recipient over OpenMail SMINTFC gateway or sent over the
Internet to a recipient on a Linux server; the embedded
image is visible just like it was sent out from Outlook.
CR: JAGae50393 SR: 8606286454
The ~/sys/mime.types has no filetype for *.vsd or visio.
The same problem for the AutoCAD file (.dwg).
CR: JAGae52304 SR: 8606288373
UAL PUT_SYNC_CHANGES command processes an action file which
is passed to it. If this action file contains records which
are larger than 4096 byes, then the remote client interface
may become corrupted.
A typical symptom of this corruption is that the rci hangs
and fails to return a reply.
CR: JAGae52624 SR: 8606288693
There are some missing quotes in the OpenMail patch
checkinstall scripts. All instances of the problem involve
calls to awk imbedded in a backtick execution, such as
`echo "$FSET_SIZES" | awk ' ... ... `
The shell expects the single quote after awk to be closed
before the backtick is closed. At the moment, the closing
backtick appears to end the awk sequence, so the scripts
execute properly. But the scripts do need to be repaired in
case the behaviour of the shell changes.
CR: JAGae53719 SR: 8606289790
The Item Browser goes into a loop on any message containing
a MIME body part with two (or more) non-consecutive MIME
Content-Disposition Headers.
This construct appears to be used by some emailers for
embedding graphics in the main body of the message. However
such constructs are at the very least ambiguous, and most
probably invalid. It is open to individual Browsers on how
they handle it, if at all.
On GR6 this causes any IMAP browser to hang when the msg is
viewed and the mailstore filestore to fill up with work
files.
For GR7, IMAP browsing is carried out using the newer Mime
Browser which does not exhibit this problem.
PHSS_28157:
CR: JAGad93625 SR: 8606224537
There is no mechanism within omshut to remove ice.user
sessions. This could cause problems for any process which
requires all OpenMail processes to have terminated before
continuing.
CR: JAGae37593 SR: 8606273505
The incoming Internet Gateway, on receiving a msg with a
MIME part with a non-ASCII filename, does not recognise the
filename. This happens while it is working out the mapping,
given in mime.types, from MIME contents-types to OM
filetypes.
The true filename is not lost, as it shows correctly in the
stored msg by all the browsers; it is just not used in the
filetype mapping, resulting in the MIME part being
incorrectly mapped to be BINARY filetype.
It works OK when the filename is in plain ASCII.
CR: JAGae41797 SR: 8606277728
A message coming into OpenMail via the Internet gateway
causes a segmentation violation and is put on the delayed
queue to be retried later and to fail again. Error in log:
SERIOUS ERROR Internet Mail (Incoming )
09.10.02 06:55:09
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 17922
Procedure trace follows:
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
<- ux_InParseCommandLine
-> GetMailText
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
<- ux_InParseCommandLine
-> GetMailText
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
CR: JAGae41856 SR: 8606277792
After reading and processing incoming Bulletin Board
messages, the BB Server waits unnecessarily and
inconsistently before exporting the resultant
synchronization requests to other servers, in 50% of cases
depending on the whether an even number of messages were
just read.
By default, this delay could be up to 1 hour.
CR: JAGae42370 SR: 8606278311
The incoming Internet gateway (unix.in) fails to decode the
valid WINMAIL.DAT attachment (TNEF) of some messages. The
TNEF is valid and should be converted at the Internet
gateway into MAPI properties.
These messages cause a warning to be logged:
WARNING Internet Mail (Incoming ) 09.06.02 09:07:45
[OM.UX 1546] MAPI property within TNEF attachment is too
big. The TNEF attachment may be corrupt.
The WINMAIL.DAT attachment is retained and converted into a
text attachment. This attachment seems to cause some
clients problems when browsing the message (e.g.
Netscape/IMAP hangs).
This problem only occurs when the general.cfg tweak
UX_PRE_5_20_COMPATIBILITY_MODE=FALSE is set (this is the
default on GR7).
CR: JAGae42811 SR: 8606278755
Some messages that originate from an OpenMail system cannot
be moved from a PST to an Exchange server. They produce a
"Can't move the items. The item could not be moved. It was
either already moved or deleted, or access was denied."
error.
CR: JAGae43470 SR: 8606279417
A forwarded DL, containing long lines, probably resulting
from comments in addresses and/or encoded non-ASCII char
sets, which is forwarded on its own via the Internet
Gateway, is corrupted at the recipient, with lines being
truncated in the middle of addresses.
The problem does not occur to the DL when the complete
message is forwarded.
CR: JAGae44306 SR: 8606280333
When attachments with common PC file extensions,
like .PDF, .PS, .FM, .MPP, .ZIP are received from the
outside Internet with unexpected, but not incorrect, MIME
Contents Types, they are not recognised as being their
correct filetype.
The are treated instead as the BINARY filetype and
therefore cannot always be selected from PC OMGUI and
associated with their corresponding PC application, e.g.
.PDF files are not always automatically passed on to Adobe
Acrobat.
PHSS_27680:
CR: JAGad71050 SR: 8606201876
Symptoms: Downloaded quoted-printable .CSV (Comma Separated
Values) file attachment to PC is missing carriage returns.
Despite it being perfectly acceptable to MS Excel.
Problem: OM does not know that .CSV files are really text
files and therefore they need their newlines uprated to
CRLF on PCs.
CR: JAGae07887 SR: 8606238864
omcpinu with the '-e' option fails to correctly merge
folders whose names contain multibyte data.
CR: JAGae18540 SR: 8606254208
The check_relay feature of sendmail does not work when
sendmail is invoked from omredirtcp.
CR: JAGae24659 SR: 8606260336
The "man" page for omupdtis etc. gives the directory path
containing the Item Structure Server database (default or
otherwise) as "/var/opt/openmail/dir/../is/" in 3 places.
Although this is correct, it is not clear to the reader
that the UNIX directory convention of "../" is being used
here to mean "the parent of".
This is confusing and prone to be misinterpreted.
CR: JAGae24724 SR: 8606260401
OpenMail does not support sendmail on AIX 5.1L. The
sendmail.cf file is in a different location compared with
AIX 4.x. In addition, omrc needs to check file permissions
when sendmail versions later than 8.9 are in use.
CR: JAGae26104 SR: 8606261785
The autotests imap_JAGae15283.u and imap_JAGae12028.u fail
about 80% of the time on Linux because they run "StartSvc
imap" immediately after "StopSvc imap" and the imap daemon
fails to start.
On HPUX11, running omoff -s imap followed by omon -s imap,
several times in quick succession causes the state of the
imap to fail to start properly.
CR: JAGae27170 SR: 8606262840
When Bulletin Board changes are being synchronised - if a
basic item (i.e. message content rather than a whole
message) is added to a Bulletin Board and then deleted in
the same email client session the ADD will be synchronised
but the DELETE will not be.
CR: JAGae31209 SR: 8606266965
omredirtcp sometimes cannot be restarted. It either fails
silently or writes a "bind failed: Address already in use"
error message to the syslog.
CR: JAGae32060 SR: 8606267820
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation. (This is another example of the
problem described in JAGad95079.)
CR: JAGae32230 SR: 8606267991
Mime Browser Controller terminates, without logging, when a
client connection, ual.remote, goes away between requesting
a browse and getting the reply.
This most likely occurs when some user stops browsing in
the midstream, on a heavily loaded system; maybe closing
his client.
Mime Browser Controller then chooses to terminate itself
rather than service all the other many connections.
CR: JAGae32345 SR: 8606268107
When a large number of users are connected to OpenMail on a
machine running RedHat Linux, there are memory management
problems resulting in segmentation violations and other
errors.
CR: JAGae33094 SR: 8606268859
A message with a "Mail from" command containing a
comment-only email address coming into OpenMail via the
Internet gateway causes a message with no originator to be
generated. If this message is routed via the X.400 gateway
it is rejected as an originator is a mandatory field.
CR: JAGae33310 SR: 8606269075
When the outbound Internet gateway processes a message that
contains recipients on both the TNEF and MIME routes the
steering file used may be either the MIME one
(~openmail/sys/mimeout.str) or the TNEF one
(~openmail/sys/tnefout.str) depending on the order of the
recipients. The message should be split in this case and
the appropriate steering file used for each type of
recipient.
CR: JAGae33867 SR: 8606269632
Using PC Admin new PDL members cannot be successfully
added. An OM16095 error is reported:
"Illegal attribute type within compound value."
The PDL member can be added successfully using the backend
OpenMail 'omaddpdln' command.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the omrc command may give incorrect '[OM
10350] Warning: File system is full' messages. The message
does not state which file system is meant to be full.
CR: JAGae36951 SR: 8606272845
A message from an Internet user with a non-ASCII comment in
his name cannot be successfully replied to when using the
Outlook client. The reply is rejected at the Internet
gateway with a 'Name cannot be mapped' error. A
non-delivery report is returned. The same message can be
successfuly replied to with the OMGUI client.
PHSS_27062:
CR: JAGad38110 SR: 8606168832
The Web Clients create temporary files under /var/tmp which
may have world-writable permissions, and always have
world-readable permissions.
CR: JAGae05328 SR: 8606236267
omtclsh (used within the webadmin interface) could hang on
Linux RedHat 7.2
CR: JAGae12028 SR: 8606245558
Using an IMAP client to copy/move a message from a local
folder to an OpenMail folder leaves the new message with
the user running the IMAP session as the message creator
and an incorrect received date.
This is only a problem if a non-IMAP client is subsequently
used to read the message.
CR: JAGae12031 SR: 8606245561
Using the ICE web client to log on to Openmail - as soon as
you select a button or click on something in the Main Menu
you get the logon page again with a SESSION EXPIRED error
message.
CR: JAGae17136 SR: 8606251070
Handling of the SIGCLD (SIGCHLD) interrupt changed at Dec.
2000 to make the code suitable for both SystemV and BSD
unix variants. However this change has caused some problems
now that the death of a child process is not ignored. These
problems include:
1. ual.remote zombie process accumulating.
2. scripts no longer executable from TCL within web client
page templates.
3. omredirtcp not invoking sendmail successfully in some
circumstances.
CR: JAGae18238 SR: 8606253906
When a new password is supplied as a result of an old
password being either expired or pre-expired by the
administrator the new password is not checked against any
password composition rules set using omconfpwd. (This
problem only occurs with OpenMail B.07.00)
CR: JAGae19347 SR: 8606255018
It is not possible to configure the Internet gateway to
produce simple inline RTF content without associated
filename information. This filename info. often causes
email clients to treat the RTF as an attachment.
Configuration for this feature is possible when a
multipart/alternative MIME structure is being generated.
However a Content Disposition of 'inline' isn't
configurable for a simple (non-multipart/alternative)
content unless a 'filename' attribute is added as well.
CR: JAGae22300 SR: 8606257997
When the Internet Gateway is configured to use the content
T.61 subject as the MIME 'filename' a long T.61 subject can
cause a Segmentation Violation in unix.out.
CR: JAGae22536 SR: 8606258235
A badly formed RCPT TO: address of the form:
";"dept.acme.com
results in a looping unix.in process.
CR: JAGae23835 SR: 8606259517
This is a problem in B.07.00 only
When the IMAP_AUTOMATIC_MDN tweak is set to TRUE, the
server does not automatically generate read
acknowledgements.
PHSS_26278:
CR: JAGad84900 SR: 8606215723
The individual X.400 printable string attributes of a mail
address, of all ORNs within a message, are being truncated
to the size limits imposed by the X.400 Standard, by the
incoming Internet Gateway.
This can cause confusing and incomplete addresses in the
ORN, particularly in the fields holding the Internet
address.
CR: JAGad95079 SR: 8606226007
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation.
CR: JAGad97183 SR: 8606228125
When a Service Router rule is set up to REJECT a message
using the RECIPIENT-SERVICE-LEVEL criterion the
non-delivery notification (NDN) generated incorrectly
specifies the NDN reason as "Mailbox exceeds size limit".
The correct text should be:
"The message could not be delivered to the recipient as the
service level for their mailbox doesn't allow that
operation".
CR: JAGad97593 SR: 8606228536
With Portal Access enabled, when a duplicate username is
entered, the ICE Web Client 6.0 user program should display
the Duplicate Usernames page containing a list of
alternative names from which to pick the correct name.
When used with a Web Client 5.10 profile, this list of
alternative names is not displayed and the Duplicate
Usernames page stalls at this point: Please select an
alternative from:
At GR6, the Duplicate Usernames page is not even displayed
at all; the Logon page remains without any feedback that
something is amiss.
CR: JAGad98210 SR: 8606229157
general.cfg setting UAL_LOCAL_IGNORE_PASSWORD=TRUE does not
work with GR7. If set a password is still required for
local UAL clients (e.g omlist) that are run within the
mailbox user's unix logon.
CR: JAGae02798 SR: 8606233575
For some IMAP clients (e.g. Outlook Express) the date of
messages in a sub-folder is the date the message was copied
to the folder rather than the date the message was
received.
CR: JAGae03973 SR: 8606234784
There is a problem with omlogon and omlogoff on Linux.
If the omlogoff command is issued to terminate a user
session, followed by a omlogon command to start a new
session, the omlogon is not always successful. The omlogon
is able to recognise that there is no other user session
running, and so doesn't fail to start. However, it then
terminates the session which was starting, so that further
commands such as omlist expect a username and password to
be provided.
If the omlist is part of an autotest, the test will hang
until a password is manually provided.
The problem does not occur if a sleep is placed between the
omlogoff and the next omlogon.
CR: JAGae03977 SR: 8606234788
If a ualth.sck call is made followed by a omlogon, then the
omlogon call may fail.
This failure seems to be intermittent - 50% of the time
approx and only occurs on Linux RedHat 7.2. It is
predominently a timing problem which goes away if a sleep
is places between the 2 calls when part of an autotest.
CR: JAGae06468 SR: 8606237428
omdosur fails with the error message "(OM 24602) Cannot
create file"
CR: JAGae07450 SR: 8606238426
The first mailnode created on a system is not always made
the Primary Mailnode. Shown by absence of '**' in omshowmn
output.
Virtual Licensing assumes that this mailnode to be the
Primary Mailnode, which it needs to refer to.
As a result, Virtual License Server crashes, with
Segmentation Violation, when trying to grant licenses that
have been requested but not yet granted.
May occur during start-up if the request was made while the
system is shut down, or at the time of the request if
system is up.
PHSS_25648:
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: JAGad87535 SR: 8606218386
B.07: omtidyu -B alters the last signon time of the user.
In previous releases it did not.
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: JAGad88889 SR: 8606219749
IMAP: rereading messages with many attachments can result
in raw base64 encoded information being displayed.
CR: JAGad89888 SR: 8606220752
Signatures which include 8-bit text will appear corrupted
when added to the message body using the B.07.00 ICE
client.
CR: JAGad90057 SR: 8606220921
An Internet Ack which contains a NULL character will cause
unix.in to fail.
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 where the accented characters (e.g.
umlaute) are displayed incorrectly.
CR: JAGad90761 SR: 8606221627
Failure to check if enough memory is available before doing
a write results in the corruption of the shared memory used
by the notification server. The result of this is that
local delivery and UAL remote abort.
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: JAGad93317 SR: 8606224222
The audit log only contains entries for successful signons.
At B.06 unsuccessful signons (e.g. password wrong) were
logged to the audit file with an indication of the signon
error.
CR: JAGad94573 SR: 8606225486
When connecting to the OpenMail message store via the Web
Client 5.10 on a Virtual Vault machine with the portal
access disabled, the error message "cannot connect to the
specified host" is displayed.
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.
CR: JAGad95463 SR: 8606226394
This applies to B.06 and B.07 of the Openmail Server. See
also JAGad 94299, against the MAPI Service Providers.
With the outgoing internet tnef gateway configured to
convert rtf to text (tnefout.str), and with the
/var/opt/openmail/sys/general.cfg option
UXO_NO_RETAIN_IF_CONVERTED=TRUE set,
1) In Outlook/OpenMail begin to create a 'New Message'.
2) Add a Subject, an Exchange users name and some message
text to the body.
3) Save and close the message.
4) Open message; add some more text and send it to the
Exchange user.
5) The Exchange user receives a message with a blank
message body.
PHSS_24876:
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: JAGad49568 SR: 8606180347
Defining more than one sender name on the omtidyu
command-line makes omtidyu substitute the last defined name
as all defined names.
For example:
omtidyu -B -u "daniel wink" -R -T i -n -w "gren elliot" -n
-w "iain parker"
will return :
CRITERIA : Messages in the InTray NOT matching "iain parker
" in SENDER field AND NOT matching "iain parker " in SENDER
field.
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: JAGad69036 SR: 8606199850
WC6.0 and PAW corrupts the autoreply covering text in the
languages Japenese, Korean and simplified Chinese when the
rule is listed. The covering text is not corrupted when
viewed from within the auto-replied message.
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: JAGad70641 SR: 8606201465
During installation of patch PHSS_23491 the script vvice
attempts to create the directory
/var/opt/openmail/temp/vv_bkp_log and fails. The directory
/var/opt/openmail/temp has the sensitivity label "SYSTEM
INSIDE" and the vvice script is executed from within the
"SYSTEM" environment and therefore does not have
sufficient privileges to perform the operation.
During installation of the patch PHSS_23491, vvsync
attempts to copy the portal.daemon and kill.portal binaries
from /opt/openmail/bin to the CHROOTED bin directory and
fails. These binaries do not form part of the OpenMail
B.07.xx.xx components and therfore are not present in the
OpenMail bin directory.
During installation of the patch PHSS_23491, user
configurable settings are not retained in the general.cfg
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: JAGad71959 SR: 8606202785
Clear/signed S/MIME message sent into OpenMail via Internet
g/w cannot be browsed by IMAP client. The multipart/signed
part of the message is empty.
The message can be successfully read by the OMGUI client.
CR: JAGad74578 SR: 8606205403
Some messages that have come from the internet contain
attachments that cannot be opened when using an IMAP client
(eg. Internet Explorer or Netscape).
Typically these are messages that only contain an
attachment and no covering text, but other types of message
structure may also suffer from this problem.
The user typically sees a copy progress bar that just
stops, the transfer of the attachment does not complete.
The format of attachment within the MIME message is not
correct - it should be base64 and in fact the data is
unencoded.
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: JAGad75517 SR: 8606206344
The problem is seen on Linux with OM 7 only.
The problem is that issuing a valid IMAP command causes the
IMAP4 server to crash, which should not happen.
With the test mailbox, issuing the commands:
. login "username" "password"
. select inbox
. fetch 2 (BODY.PEEK[3.HEADER.FIELDS (Resent-Date)])
causes the crash.
CR: JAGad75975 SR: 8606206802
An address list, such as a TO: field, may be corrupted if
it contains a quote character ("). This occurs because of
the way that sendmail converts the address and OpenMail
subsequently parses it. In the following text, # is used to
represent the <backslash> character.
If an entry has the format #", then sendmail quotes it and
adds an extra <backslash> to the #" sequence.
So us#"er <user.local>, becomes to "us##"er" <user/local>,
OpenMail then splits up the address list using commas as
the separator. If a separator is in a quote, it is ignored.
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.
CR: JAGad80029 SR: 8606210842
OpenMail may fail to configure auxiliary child processes
correctly when using the omsetscv command. This results in
the child processes not terminating via the omshut command.
CR: JAGad83734 SR: 8606214543
This applies to B.07, when configured to allow duplicate
internet addresses in the directory. This is the default
for servers upgraded from an earlier version of OpenMail,
but not for new B.07 installations.
Using OMGUI to send a message, if an internet name is
entered that is in the OpenMail system directory twice and
the Dist. List is checked then a System Error 2 is
generated and the connection is lost (the UAL session is
terminated). This only occurs if individual name checking
is turned off.
This is caused by an error in the UAL Checklist command,
when attempting to return the duplicate entries as
alternatives. Note that, prior to B.07, UAL CheckList did
not actually return alternatives when searching on the
internet address field.
See also the related CR JAGad 83932, which is not planned
for fixing in the September 2001 Periodic Patch.
PHSS_23491:
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: 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: 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: 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: 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.
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: 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: JAGad45429 SR: 8606176189
When using PAW and Web Client 6.0 rule names may be
displayed incorrectly in Korean, Japanese and Simplified
Chinese versions. This may cause the browser to hang.
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: 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: 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: JAGad47713 SR: 8606178486
1) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
If a multibyte string contains an *, this is assumed to be
a wildcard.
2) Username incorrectly displayed if it contains TX fields.
The TX fields are concatenated to earlier field values.
This is also a problem with other address list attributes.
3) The -l option is not displayed.
This displays a list of the requested folders and should be
displayed in the full listing.
4) The error/usage string is not displayed if not options
are specified.
omtidyu either returns nothing, or prompts for the password
for the defult user.
5) The -q option does not work.
The -q option produce similar output to a full report, and
more information than a summary report.
6) The msg type selection is not output.
When a full report is requested, the information on each
item should include the message type.
7) The -f option no longer includes WB.
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: 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: JAGad52689 SR: 8606183476
This applies to omsmtpd in Release 7.
With heavy usage, the SMTP Relay port 25 listener
occasionally stops with a Select error - Bad File Number.
The omshowlog output contains:
ERROR SMTP Relay (SMTPD Relay
Pr) 03.02.01 13:34:27
[OM.DMON 2163] Failed in select.
Error: 'Bad file number'
Alternatively, after logging this error, omsmtpd may hang.
In this case, there will be more than one copy of omsmtpd
running, and the parent will be waiting for the child
processes, and vice versa.
Temporary Workaround:
Stop and restart the daemon.
Or, if Authorisation or Anti-spam features are not in use,
turn off the relay, and rely on sendmail & ommapsmtp to
route incoming messages correctly.
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: 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."
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.
CR: JAGad66344 SR: 8606197150
When installing OpenMail B.07.00, file
~openmail/release.sys/smtpd.cfg is updated to contain the
current domain name in place of the string %LOCALDOMAIN%.
This is also done whenever a new OpenMail instance is
created.
When a patch is installed, the patch scripts need to repeat
this edit.
This does not affect ~openmail/sys/smtpd.cfg which is
intended to be tailored by the OpenMail administrator. This
file is not changed during patch installation.
Defect Description:
PHSS_29066:
CR: JAGae59759 SR: 8606296148
A coding defect in the brw component ignores Asian
Interchange CharSets and limits itself to Latin ones only.
A design defect in the tfl component allows it be called
recursively when parsing the ORN of an NDN in an Asian
user's mailbox, thus overwriting and corrupting its state
memory.
CR: JAGae62810 SR: 8606299316
The checkinstall patch script was not checking for HP-UX
11.11 or later. In this case, a status of EXCLUDE should be
returned if OpenMail is not present.
CR: JAGae70969 SR: 8606307934
If a message contained the line "Content-Type: text/html;
charset=", and then an attempt was made to construct the
imapBodyStrc field, the processing of the NULL charset
value caused a corruption and the item browser failed to
return then requested data for that item.
CR: JAGae70977 SR: 8606307942
When attempting to construct the imapBodyStrc record, a
corrupt container can cause an error while attempting to
create the Distribution List.
This can happen if there is no distribution list. Rather
than returning the header information of an item without
the distribution list, an attempt is made to create it, and
when the item browser cannot find the distribution list in
the container, it fails and no header information is
returned.
CR: JAGae70980 SR: 8606307945
If an item contains a folder, then folder's data is stored
in a different container to rest of the data for that
message.
When attempting to construct the imapBodyStrc record, the
subject of the folder needs to be read in. When doing this,
the block was read in from the parent container instead of
the folder's container. The block being read either
contained either contained a value for the subject, which
meant that a corrupt subject was read in, or the block
contained no such value and the item brwoser failed to
return the message content.
CR: JAGae70984 SR: 8606307949
The IMAP daemon is looping when trying to process the
corrupt header of a message.
CR: JAGae70985 SR: 8606307950
The problem was caused by the UAL returning either no
Absolute reference value for the Delivery Acks, or a value
of 0. The IMAP fetch command does not display items with
such a UID.
The existence of such messages also means that UID values
were missing and Netscape 4.7 became confused.
CR: JAGae72697 SR: 8606309822
A coding defect in the GR7 signon component attempts to
convert an incorrect non-ASCII supplied password from the
user's Charset, given by LocalCharSet in OMGUI, to the
default Charset, ISO8859_1. Such a conversion is not
defined for Asian Charsets.
PHSS_28592:
CR: JAGab82932 SR: 8606110229
A coding defect in the incoming Internet Gateway fails to
take into account INTEL byte reversal of the integer field
used to signify an OLE object, which it tests in order to
determine whether to retain the object within the MAPI
properties or to split it out into a separate attachment.
CR: JAGae50393 SR: 8606286454
The Internet Gateway does not recognise these file types
and treats them as of type BINARY.
CR: JAGae52304 SR: 8606288373
The UAL_PUT_SYNC_CHANGES command fails on large messages
due to the buffer size used for processing the message
being exceeded. This means that the remote client reports a
serious error and fails to complete the UAL command.
CR: JAGae52624 SR: 8606288693
There were some missing closing quotes in awk statements in
the checkinstall script (only used during patch
installation on HP-UX). The missing quotes have been added.
CR: JAGae53719 SR: 8606289790
A coding defect in the brw component attempts to read twice
any subsequent MIME Content-Disposition headers, when it
reaches EOF.
PHSS_28157:
CR: JAGad93625 SR: 8606224537
The omshut command does not currently remove ice.user
processes which are still running.
CR: JAGae37593 SR: 8606273505
A coding defect, in the Incoming Internet Gateway, did not
decode encoded MIME filename parameters before looking up
their filetype mappings.
CR: JAGae41797 SR: 8606277728
The buffer used to hold a MIME header field is not big
enough to hold the amount of data read in if the MIME
header is garbled.
CR: JAGae41856 SR: 8606277792
A coding defect, in the Bulletin Board Server, waits on the
import queue for up to an hour, by default, once the import
queue is empty before it exports synchronization requests,
after having just read an even number of messages from the
queue. When it reads an odd number, it immediately finds
the queue empty and there is no delay.
CR: JAGae42370 SR: 8606278311
The checking carried out on the validity of the TNEF is
incorrect for some MAPI properties that exceed 512 bytes in
length and a legal TNEF file is treated as being corrupt.
An error is logged and the TNEF is converted to text to
preserve it for further investigation.
This binary file that is labeled as being textual can cause
problems for some clients (e.g. Netscape/IMAP).
CR: JAGae42811 SR: 8606278755
The problem message contain the PR_REPLY_RECIPIENTS_ENTRIES
property with names associated with the OpenMail Address
Book Provider. This information is unresolvable on the
Exchange system and causes the messages to be rejected.
To overcome this problem a new general.cfg option is
introduced: PM_STRIP_MAPI_REPLY_RECIPS=TRUE
Setting this option causes omcpoutu to strip out the MAPI
properties that cause the migration problem. This user can
then be restored and the message store copied to Exchange
via a PST.
CR: JAGae43470 SR: 8606279417
Forwarded DLs are always sent as MIME type
'application/x-openmail-1166' encoded as Quoted-Printable.
A coding defect, in the Incoming Internet Gateway, did not
decode the QP-encoded MIME part of type
'application/x-openmail-1166' before processing it.
CR: JAGae44306 SR: 8606280333
The sending email system sends out some application type
attachments, e.g. a .PDF file, under the MIME catch-all
Content Type, 'application/octet-stream', whereas the
Internet Gateway is only expecting a more specific Content
Type; 'application/pdf' in this case.
PHSS_27680:
CR: JAGad71050 SR: 8606201876
The only file attachment that OM recognises as of type text
are .TXT files.
It is not told that .CSV files need treating in the same
way with regard to newlines.
CR: JAGae07887 SR: 8606238864
The failure to merge folders whose names contain multibyte
data correctly was due to only the downgraded folder names
being compared for matches, ignoring any existance of T61
folder names.
CR: JAGae18540 SR: 8606254208
When sendmail is invoked from omredirtcp it is called with
the -bs option for single execution. When this option is
used the 'check-relay' functionality is not performed, so
connections from IP addresses that should be rejected are
allowed.
To overcome this deficiency in the omredirtcp environment
the -x option has been added to omredirtcp to allow a file
of IP addresses to be rejected to be specified. See the
omredirtcp MAN page for details.
CR: JAGae24659 SR: 8606260336
Although obscure and indirect, the directory path:
"/var/opt/openmail/dir/../is/"
is strictly correct and in fact necessary, due to the
possibility that "~openmail/dir" may be a symbolic link to
a completely different location, and "is/" is always within
the physical parent of the "~openmail/dir".
This needs pointing out to the user by rewording the man
page in 2 places.
However, understanding the location of the ISDB is simply
background information; it is not necessary for the use of
these commands.
CR: JAGae24724 SR: 8606260401
AIX 5.1L keeps the sendmail.cf files in /etc/mail. 8.9 is
no longer the latest version of sendmail.cf, so omrc is
changed to check certain file permissions for sendmail 8.9
or later.
CR: JAGae26104 SR: 8606261785
The problem is caused by omon failing to wait for the
Required state of a service to move from "disabling" to
"disabled" before attempting to start a service.
CR: JAGae27170 SR: 8606262840
The code that handles the delete of the item does not think
that the newly added item is within a Bulletin Board as a
this information has not been added to the transient record
that represents the item in the BB list.
CR: JAGae31209 SR: 8606266965
When omredirtcp fork/execs sendmail to handle an incoming
SMTP connection the sendmail process inherits the SMTP
socket. While the sendmail process is servicing this SMTP
connection the SMTP socket cannot be re-established (the
'bind' call will fail). Therefore if omredirtcp is killed
it cannot be restarted until all its sendmail children have
exited.
CR: JAGae32060 SR: 8606267820
The primary cause of the problem is the fact that the TNEF
file after decoding from the MIME encoding
(quoted-printable in this instance) is corrupt and contains
field length information that points beyond the end of the
TNEF data.
The secondary problem is that the quoted-printable encoding
of a TNEF attachment is illegal according to Microsoft's
rules for this type of attachment.
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting.
CR: JAGae32230 SR: 8606267991
A design defect, in the Mime Browser Controller, of
shutting down immediately on encountering a SIGPIPE signal
from any broken connections (client or child) out of its
many connections.
CR: JAGae32345 SR: 8606268107
The problems occur because ual.remote is built with thread
support, even though each logged-in user has a separate
copy. As similar problems could happen in the IMAP server,
the MIME browser and the item browser, these components
should be built without the use of threads.
CR: JAGae33094 SR: 8606268859
When the Sender name is examined the fact that it has a
comment means that it is treated as a non-null email
address. After stripping out the comments a null email is
left and this is then treated as a valid originator.
CR: JAGae33310 SR: 8606269075
The code does not differentiate enough between a TNEF
recipient and a MIME recipient to split the message and
allow different steering for the different types of
recipient.
As the fix for this problem will cause a change in
behaviour on systems that have different TNEF and MIME
steering files then the old (incorrect) behaviour can be
reinstated by setting the following general.cfg option:
UXO_OLD_TNEFOUT=TRUE
CR: JAGae33867 SR: 8606269632
When using PC Admin to create/modify PDLs the ommodpdln
command is used on the server. If the user being
added/modified has an INTERNET-ADDR (IA) attributed
configured in the directory then this attribute is supplied
in the entry. The presence of this IA attribute is causing
'ommodpdln' to report an error.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the df command lists an entry for a file
system called /proc. All the sizing parameters for this
file system are listed as hyphens. This confuses the
omdiskfull command which issues a message announcing a full
file system. The 'omeval omdf' command (for AIX) has been
changed to ignore this entry.
CR: JAGae36951 SR: 8606272845
The non-ASCII characters in the comment part of the ARPA
name confuse unix.out and it thinks that the name is
illegal and therefore refuses to process the name and
generates a NDN for the message.
It seems that only Outlook (under some circumstances)
preserves the comment field when generating a reply, other
clients discard the comment and therefore are not affected
by this problem.
PHSS_27062:
CR: JAGad38110 SR: 8606168832
Both Web Clients create workfiles in /var/tmp. The umask
system call should be invoked to ensure that the files are
neither world-readable nor world-writable.
CR: JAGae05328 SR: 8606236267
If a program loads a dynamic library which has been
compiled with threads enabled, then file I/O is unstable
within the dll unless there has been file I/O within the
calling program first. This appears to be a problem in
Linux Redhat 7.2.
CR: JAGae12028 SR: 8606245558
When an APPEND command is issued by an IMAP client the
OpenMail creator of the item being appended is not set to
be the Sender of the item. Neither is the OpenMail create
date set to be the IMAP internal date of the item. The
existing code does make the message Sender a FROM recipient
in the distribution list - this means that other IMAP
clients see the correct sender/creator, however non-IMAP
clients see an incorrect msg creator.
A new general.cfg option is introduced with the fix for
this problem:
IMAP_ALLOW_MOD_CREATOR=TRUE
will set up the OpenMail creator to be the message Sender -
this is the default.
IMAP_ALLOW_MOD_CREATOR=FALSE
will reinstate the old behaviour.
CR: JAGae12031 SR: 8606245561
The ICE session is terminated because the REMOTE_ADDR value
passed to the cgi program changes during the course of the
email session. The code expects this value not to change,
but there are circumstances when it does. It can happen
when web access is provided by an ISP.
In order to provide flexibility in this situation a new web
access and profile option will be provided to control the
behaviour of the web profile with respect to a changing
value of REMOTE_ADDR during a session.
The REMOTE_ADDR value can legitimately change if an ISP is
being used, so this behaviour is now contolled by the
option:
Allow-Remote-Addr-Change = 0 # REMOTE_ADDR value can't
# change (default and old
# behaviour)
Allow-Remote-Addr-Change = 1 # REMOTE_ADDR can change
# if SessId is in cookie.
Allow-Remote-Addr-Change = 2 # REMOTE_ADDR can change
# with no checking.
This option can be set at the individual profile level:
~openmail/omhmtl/<Profile_Name>/profile
or for all web profiles:
~openmail/omhtml/config
The individual profile setting (if set) will take
precedence.
An Allow-Remote-Addr-Change setting of 1 is recommended to
overcome any premature SESSION EXPIRED problems - this will
work if the web browser is using cookies to provide session
id hiding. A setting of 2 means that no checking of
REMOTE_ADDR is done at all and if cookies are not being
used then the session id information is passed within URLs
that are visible on the computer screen and could be used
from another web browser.
CR: JAGae17136 SR: 8606251070
The handling of the SIGCLD (SIGCHLD) interrupt has changed
from being ignored to being trapped ('reaped'). This change
has had some unforeseen side-effects.
CR: JAGae18238 SR: 8606253906
The code to check a new password against any password
composition rules was removed when the PAM mechanism was
incorporated in the B.07.00 code.
CR: JAGae19347 SR: 8606255018
Content Disposition of 'inline' should be configurable
without a 'filename' value. A new general.cfg option has
been added to allow this to be configured:
INET_INLINE_FILETYPES=nnnn
where 'nnnn' is an OpenMail filetype. Several filetypes can
be specfied by separating with commas, for example:
INET_INLINE_FILETYPES=2130,2133
will cause both RTF and HTML to be given a Content
Disposition of 'inline'.
The INET_INLINE_FNAME_ALLOWED=FALSE option should still be
set in general.cfg to suppress the 'filename'.
Additionally the ~openmail/sys/mimeout.str file should be
editted to uncomment the lines for 2130 and 2133 if the
multipart/alternative structure is not required for these
filetypes.
CR: JAGae22300 SR: 8606257997
The T.61 subject can become large when encoded as a MIME
string as each separate T.61 sub-string will be preceded by
a character set specification. This long string can then
overflow the buffer used to hold the MIME filename string
causing a Segmentation Violation.
CR: JAGae22536 SR: 8606258235
A coding defect, in the incoming Internet Gateway, of
failing to increment a loop count on encountering a NULL
X400 address, as occurs in this case, causes an infinite
loop.
CR: JAGae23835 SR: 8606259517
There is no test for whether read acknowedgements are
required when an IMAP message is read, and no attempt is
made to generate an acknowledgement if it is.
PHSS_26278:
CR: JAGad84900 SR: 8606215723
The incoming Internet Gateway normally truncates all X.400
printable string attributes, of all ORNs within a message,
to the size limits stipulated in the X.400 standard, just
in case the message is sent through the X.400 Gateway.
A new Tweak, INET_NO_TRUNC_X400_ATTS, has been introduced
to inhibit this truncation.
CR: JAGad95079 SR: 8606226007
The primary cause of the problem is the fact that the TNEF
file after decoding from the MIME encoding
(quoted-printable in this instance) is corrupt and contains
field length information that points beyond the end of the
TNEF data.
The secondary problem is that the quoted-printable encoding
of a TNEF attachment is illegal according to Microsoft's
rules for this type of attachment.
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting.
CR: JAGad97183 SR: 8606228125
The text in the message catalogue for the message rejection
due to a recipient user's 'service level' value is
incorrect. It describes this error as a mailbox size limit
violation.
CR: JAGad97593 SR: 8606228536
There is no code whatsoever in the Web ICE Client 6.0 to
cope with the %%SIGNONALTS%% markup in the Duplicate
Usernames page of the 5.10 profiles, which is significantly
different from the 6.0 profiles. It has no code of its own
to do all the extra work that the Web Client 5.10 does in
this case.
Also, at GR6, the Portal Access facility was not available
with the Web Client 5.10, and so when its profiles are used
with the ICE Client 6.0, it has no ability to display a
list of alternative names; the Duplicate Usernames page is
absent.
CR: JAGad98210 SR: 8606229157
Pluggable Authentication Modules (PAM) changes to GR7 have
accidently removed the UAL_LOCAL_IGNORE_PASSWORD option.
CR: JAGae02798 SR: 8606233575
The code of the in.imap41d program does not use the
'received date' information when retrieving the
INTERNALDATE attribute of a message.
CR: JAGae03973 SR: 8606234784
The problem was that omlogoff terminates while the omlogon
process is still running. If running another omlogon
immediately afterwards, the first omlogon would delete out
the user pipes which the second omlogon had just created.
Although this second omlogon appeared to have succeeded, it
was unable to process further requests - e.g. omlist. An
omlist call would then expect the username and password to
be entered manually. This caused various of the OpenMail
autotests to hang.
CR: JAGae03977 SR: 8606234788
The cause of the problem was the errno value being changed
when a successful accept() call was made. It is possible
for this to happen on Linux. The pcmonitor returns an error
condition to a calling function if the errno indicates an
error, even if the accept call was successful. This caused
omlogon to fail.
CR: JAGae06468 SR: 8606237428
The failure of omdosur was caused by trying to access files
in the live message store rather than those in the
alternative working directory which is specified when
omdosur is called.
Each time a Content Record is opened in omdosur a transient
flag is set to indicate that the alternative working
directory should be used when opening files. For IMAP
object file information this did not succeed as the Content
Record was reread unsetting this flag.
CR: JAGae07450 SR: 8606238426
A coding defect of an uninitiallised return parameter, in
the User Directory Access component, causes the return of a
spurious Primary Mailnode when none exists, in very rare
circumstances. The caller does not defend against this
condition.
Encountered only on Solaris 8, but could occur rarely
anyplace, anytime.
PHSS_25648:
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: JAGad87535 SR: 8606218386
In GR7 a session monitor daemon was introduced which does
some of the work of the UAL. One thing it does is to update
the user's signon information, and the functionality of
when to update the last signon time was not implemented.
Instead, the last signon time is always updated - which
does not correspond to the GR6 functionality when an admin
session or a session run by a trusted user is doing the
signon.
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: 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: JAGad89888 SR: 8606220752
An internal format error within TCL strings caused 8-bit
strings to appear corrupted.
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: JAGad90490 SR: 8606221356
Non-ascii NDN text from message catalogue is not given the
correct charset specification in the MIME header.
CR: JAGad90761 SR: 8606221627
One write to the shared memory used by the Notification
Server failed to check if enough space was available before
commencing the write.
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: JAGad93317 SR: 8606224222
PAM changes for B.07 cause unsuccessful signons to return
early without doing any audit logging.
CR: JAGad94573 SR: 8606225486
The tweaks DEFAULT-OMSERVER and OMSERVER where not honoured
if the portal access mechanism was disabled.
CR: JAGad94888 SR: 8606225815
At VV4.5 root does not have the required authorisation
level to execute the setlevel command.
CR: JAGad95463 SR: 8606226394
The cause appears to be the value of the PR_RTF_SYNC*
properties, in particular the PR_RTF_SYNC_BODY_COUNT.
These properties are correctly set when the message is
initially created. However, after the message has been
saved and re-edited, these properties are NOT updated
causing a mismatch between the properties and the actual
content of the sent message.
PHSS_24876:
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: JAGad49568 SR: 8606180347
Multiple sender names on the omtidyu command line were all
held in a single buffer resulting in the last senders name
to be registered for all the sender names.
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: JAGad69036 SR: 8606199850
The cause of the corrupted Korean, Japanese and Simplified
Chinese strings was due to an internal formating error.
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: JAGad70641 SR: 8606201465
The scripts vvice and vvysnc where not updated for OpenMail
B.07.00 periodic patches
CR: JAGad71090 SR: 8606201916
Hidden items within the message store were included within
the item count when listing the tray or folder areas.
CR: JAGad71959 SR: 8606202785
The mime browsing library only expects to be dealing with
message components in a serialised file. There are
occasions when the components of a message are not
serialised - when this is the case the browse of that item
returns nothing.
CR: JAGad74578 SR: 8606205403
The MIME header is slightly strange inasmuch as the value
is separated from the tag by two spaces. For example:
Content-Transfer-Encoding: base64
This causes the MIME generation routines (in some
circumstances) to misinterpret the MIME header field value.
In this particular case the MIME header has come in from
outside of OpenMail and is being retained in the
inetMessageHeader object file associated with the message.
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: JAGad75517 SR: 8606206344
The code that constructs the command output was erroneously
attempting to dereference a pointer whose value was NULL.
CR: JAGad75975 SR: 8606206802
In the following text, # is used to represent the
<backslash> character. 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 than 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.
CR: JAGad80029 SR: 8606210842
The child process IDs were corrupted within the process ID
configuration file due to incorrect file locking mechanisms
CR: JAGad83734 SR: 8606214543
UAL Checklist searches on the internet address field, and
records in the DL the entries with alternatives/duplicates.
Later it reprocesses the DL, re-searching to get the
alternatives in a new file, which is then appended to the
DL. However, the re-search is on the X400 attributes, not
on the internet address, and the alternatives file is not
created. But the attempt to append continued anyway, and
tried to open a non-existent file.
PHSS_23491:
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: 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: 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: JAGad41471 SR: 8606172211
A segmentation fault occures when parsing a blank line at
the top of the mnMapFile which is located in the
var/opt/openmail/sys directory.
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.
CR: JAGad43052 SR: 8606173797
The IMAP daemon was not converting MIME subject before
copying an item into the OpenMail message store.
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: JAGad45429 SR: 8606176189
When the rule name is read from the OpenMail Auto-Actions
file, tcl expects the format of the string to be UTF-8.
OpenMail does not store the rule names in UTf-8 format,
thus if the rule name is modified in anyway then it becomes
corrupted.
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: 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: 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: JAGad47713 SR: 8606178486
) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
The * character is assumed to be the wildcard character in
all cases. This may not be so for certain MB strings.
2) Username incorrectly displayed if it contains TX fields.
The display routine does not take the address group
separator 027 into consideration.
3) The -l option is not displayed.
This is an enhancement request.
4) The error/usage string is not displayed if not options
are specified.
A check to no parameters is not done.
5) The -q option does not work.
The reporting mechanism displays a full report if a SUMMARY
report is not requested, rather than if a FULL report is
requested.
6) The msg type selection is not output.
This is an enhancement request.
7) The -f option no longer includes WB.
In GR7, the -T w option is used to display the waste basket
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: 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: JAGad52689 SR: 8606183476
When the relay is heavily loaded, it creates one or more
child relay processes to share the incoming requests. The
child processes later stop when they have been idle for a
while (30 seconds by default). The select error can occur
when the parent is processing the Termination signal from
the child, if the signal is received between when the code
decides to look for input from the child (FD SET) and doing
the select.
After hitting this error, the code does not explicitly stop
the child relay processes, but does wait for them to die.
As the child processes may be waiting for instructions from
the parent, a hang can occur.
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: JAGad63387 SR: 8606194177
The cause of this failure was due to incorrectly parsing
the Content-Disposition response header which sometimes
resulted in corrupted memory.
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.
CR: JAGad66344 SR: 8606197150
~openmail/release.sys/smtpd.cfg was replaced by an
unconfigured file during patch installation. It is now
edited so it contains a domain name. This is similar to the
work done during initial B.07.00 installation.
Enhancement:
No
SR:
8606296148 8606299316 8606307934 8606307942 8606307945
8606307949 8606307950 8606309822 8606110229 8606286454
8606288373 8606288693 8606289790 8606224537 8606273505
8606277728 8606277792 8606278311 8606278755 8606279417
8606280333 8606201876 8606238864 8606254208 8606260336
8606260401 8606261785 8606262840 8606266965 8606267820
8606267991 8606268107 8606268859 8606269075 8606269632
8606271509 8606272845 8606168832 8606236267 8606245558
8606245561 8606251070 8606253906 8606255018 8606257997
8606258235 8606259517 8606215723 8606226007 8606228125
8606228536 8606229157 8606233575 8606234784 8606234788
8606237428 8606238426 8606214343 8606214723 8606214740
8606215716 8606215745 8606218386 8606218500 8606219531
8606219749 8606220752 8606220921 8606221356 8606221627
8606222161 8606224187 8606224222 8606225486 8606225815
8606226394 8606160818 8606162150 8606180347 8606196695
8606198411 8606199624 8606199850 8606200362 8606201464
8606201465 8606201916 8606202785 8606205403 8606205540
8606205863 8606206344 8606206802 8606209895 8606210842
8606214543 8606100957 8606102906 8606162348 8606165799
8606171299 8606172211 8606173711 8606173797 8606174784
8606176189 8606176209 8606176642 8606177205 8606177664
8606178486 8606178878 8606181602 8606183476 8606186206
8606187277 8606187413 8606188546 8606189626 8606194177
8606195023 8606195467 8606197150
Patch Files:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ADM
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMECAT
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEICE
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPAW
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPSS
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-APPL
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-BB
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSCAT
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSICE
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSPAW
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/PHSS_29066/ompatch.idx
/opt/openmail/patch/PHSS_29066/omunpatch
/opt/openmail/patch/filesets/OM-CORE
/opt/openmail/patch/ompatch
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DESK
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DSYNC
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGCAT
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGICE
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPAW
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPSS
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINCAT
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINICE
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINPAW
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FRECAT
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREICE
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREPAW
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERCAT
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERICE
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERPAW
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-IMAP4
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITACAT
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAICE
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAPAW
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORCAT
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORICE
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORPAW
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LC
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LDAP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-MAN
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPCAT
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPICE
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPPAW
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PMOVER
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-POP3
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBCAT
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBICE
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBPAW
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-RC
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SMS
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPACAT
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAICE
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAPAW
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWECAT
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEICE
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEPAW
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-UNIX
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-WEBADM
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-X400
what(1) Output:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ADM:
No what strings
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMECAT:
No what strings
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEICE:
No what strings
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPAW:
No what strings
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPSS:
No what strings
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-APPL:
No what strings
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-BB:
No what strings
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSCAT:
No what strings
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSICE:
No what strings
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSPAW:
No what strings
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CORE:
No what strings
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DESK:
No what strings
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DSYNC:
No what strings
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGCAT:
No what strings
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGICE:
No what strings
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPAW:
No what strings
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPSS:
No what strings
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINCAT:
No what strings
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINICE:
No what strings
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINPAW:
No what strings
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FRECAT:
No what strings
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREICE:
No what strings
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREPAW:
No what strings
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERCAT:
No what strings
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERICE:
No what strings
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERPAW:
No what strings
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-IMAP4:
No what strings
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITACAT:
No what strings
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAICE:
No what strings
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAPAW:
No what strings
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORCAT:
No what strings
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORICE:
No what strings
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORPAW:
No what strings
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LC:
No what strings
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LDAP:
No what strings
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-MAN:
No what strings
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPCAT:
No what strings
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPICE:
No what strings
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPPAW:
No what strings
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PMOVER:
No what strings
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-POP3:
No what strings
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBCAT:
No what strings
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBICE:
No what strings
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBPAW:
No what strings
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-RC:
No what strings
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SMS:
No what strings
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPACAT:
No what strings
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAICE:
No what strings
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAPAW:
No what strings
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWECAT:
No what strings
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEICE:
No what strings
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEPAW:
No what strings
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-UNIX:
No what strings
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-WEBADM:
No what strings
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-X400:
No what strings
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/ompatch:
$Header: sh_patch.gen /main/gr7_patch/4 2002/04/26 1
8:35:41 pl $
/opt/openmail/patch/PHSS_29066/omunpatch:
$Header: sh_unpat.gen,v
/opt/openmail/patch/PHSS_29066/ompatch.idx:
No what strings
cksum(1) Output:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2199554305 883133 /opt/openmail/patch/filesets/OM-ADM
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
4239652519 224616 /opt/openmail/patch/filesets/OM-AMECAT
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3014163872 17013 /opt/openmail/patch/filesets/OM-AMEICE
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
507117261 13847 /opt/openmail/patch/filesets/OM-AMEPAW
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2691884037 106418 /opt/openmail/patch/filesets/OM-AMEPSS
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2885037744 185481 /opt/openmail/patch/filesets/OM-APPL
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1675683637 85442 /opt/openmail/patch/filesets/OM-BB
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
410290493 124060 /opt/openmail/patch/filesets/OM-CHSCAT
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3839519727 17075 /opt/openmail/patch/filesets/OM-CHSICE
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2284743352 14132 /opt/openmail/patch/filesets/OM-CHSPAW
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
673614208 12097981 /opt/openmail/patch/filesets/OM-CORE
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
732831463 106337 /opt/openmail/patch/filesets/OM-DESK
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2801985225 176684 /opt/openmail/patch/filesets/OM-DSYNC
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2344308545 224622 /opt/openmail/patch/filesets/OM-ENGCAT
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
665478619 16988 /opt/openmail/patch/filesets/OM-ENGICE
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1384345074 13846 /opt/openmail/patch/filesets/OM-ENGPAW
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1939806516 106410 /opt/openmail/patch/filesets/OM-ENGPSS
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1744529186 252187 /opt/openmail/patch/filesets/OM-FINCAT
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2328571111 17096 /opt/openmail/patch/filesets/OM-FINICE
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1600422433 14249 /opt/openmail/patch/filesets/OM-FINPAW
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3043501573 251568 /opt/openmail/patch/filesets/OM-FRECAT
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1728362591 17040 /opt/openmail/patch/filesets/OM-FREICE
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3143310375 14173 /opt/openmail/patch/filesets/OM-FREPAW
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2182085603 252214 /opt/openmail/patch/filesets/OM-GERCAT
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1999957808 17063 /opt/openmail/patch/filesets/OM-GERICE
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1305879208 14088 /opt/openmail/patch/filesets/OM-GERPAW
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3057740483 84854 /opt/openmail/patch/filesets/OM-IMAP4
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2307490670 249990 /opt/openmail/patch/filesets/OM-ITACAT
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3306396668 17040 /opt/openmail/patch/filesets/OM-ITAICE
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1946172555 14057 /opt/openmail/patch/filesets/OM-ITAPAW
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
638476142 125613 /opt/openmail/patch/filesets/OM-KORCAT
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1226614991 17081 /opt/openmail/patch/filesets/OM-KORICE
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3368881228 14295 /opt/openmail/patch/filesets/OM-KORPAW
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3342671657 725586 /opt/openmail/patch/filesets/OM-LC
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3577101117 86068 /opt/openmail/patch/filesets/OM-LDAP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3739852844 10326 /opt/openmail/patch/filesets/OM-MAN
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1248056360 125739 /opt/openmail/patch/filesets/OM-NIPCAT
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
761780837 17121 /opt/openmail/patch/filesets/OM-NIPICE
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3139281632 14315 /opt/openmail/patch/filesets/OM-NIPPAW
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3235410751 66245 /opt/openmail/patch/filesets/OM-PMOVER
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3259986669 68164 /opt/openmail/patch/filesets/OM-POP3
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
4169900025 252354 /opt/openmail/patch/filesets/OM-PTBCAT
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
985441493 17059 /opt/openmail/patch/filesets/OM-PTBICE
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
68913776 14112 /opt/openmail/patch/filesets/OM-PTBPAW
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
608310118 481626 /opt/openmail/patch/filesets/OM-RC
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
764886667 208690 /opt/openmail/patch/filesets/OM-SMS
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
165239328 251074 /opt/openmail/patch/filesets/OM-SPACAT
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3835363625 17079 /opt/openmail/patch/filesets/OM-SPAICE
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2594012852 14111 /opt/openmail/patch/filesets/OM-SPAPAW
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2049316681 250061 /opt/openmail/patch/filesets/OM-SWECAT
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1647281191 17048 /opt/openmail/patch/filesets/OM-SWEICE
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
4154923831 14094 /opt/openmail/patch/filesets/OM-SWEPAW
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
615540948 130520 /opt/openmail/patch/filesets/OM-UNIX
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2274818286 775350 /opt/openmail/patch/filesets/OM-WEBADM
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3503968682 1018008 /opt/openmail/patch/filesets/OM-X400
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1357410443 26524 /opt/openmail/patch/ompatch
4120277454 11249 /opt/openmail/patch/PHSS_29066/omunpatch
3985583080 167805 /opt/openmail/patch/PHSS_29066/ompatch.idx
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_23491 PHSS_24876 PHSS_25648 PHSS_26278 PHSS_27062 PHSS_27680
PHSS_28157 PHSS_28592
Equivalent Patches:
PHSS_29065:
s700: 10.20
s800: 10.20
PFSS_17046:
sparcSUN: 5.6 5.7 5.8
PASS_17046:
AIX: 4.3 5.1
PLSS_17050:
intelLinux: RedHat7.0 RedHat7.1 RedHat7.2 RedHat7.3
Patch Package Size: 19990 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_29066
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_29066.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_29066. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
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_29066.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_29066.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_29066.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
SUBSYSTEM_SHUT
=================================================
PHSS_28592:
=================================================
CR: JAGae50393 SR: 8606286454
-------------------------------
For these file extensions to be recognised by OMGUI, the
following lines should be added to ~/sys/appmap and its
version number incremented so that it gets downloaded to
clients :
1743 B WN G '????' '????' '.DWG' // AutoCAD
2144 B WN G '????' '????' '.VSD' // Microsoft Visio
=================================================
PHSS_28157:
=================================================
CR: JAGae42811 SR: 8606278755
-------------------------------
The general.cfg option PM_STRIP_MAPI_REPLY_RECIPS=TRUE must
be set to activate this new behaviour.
=================================================
PHSS_27680:
=================================================
CR: JAGae33310 SR: 8606269075
-------------------------------
The old behaviour - not splitting the message when MIME
and TNEF recipients are present and a separate steering
file exists for these routes (~openmail/sys/mimeout.str
and ~openmail/sys/tnefout.str) - can be reinstated by
setting the general.cfg option: UXO_OLD_TNEFOUT=TRUE
=================================================
PHSS_27062:
=================================================
CR: JAGae12028 SR: 8606245558
-------------------------------
The old behaviour can be reinstated by setting the
IMAP_ALLOW_MOD_CREATOR=FALSE option in
~openmail/sys/general.cfg
CR: JAGae12031 SR: 8606245561
-------------------------------
To fix the problem of a premature SESSION EXPIRED error
when using web clients via an ISP web connection a new web
client configuration option has been introduced. This
option controls the behaviour of the ice.user program with
respect to the value of the REMOTE_ADDR environment
variable supplied by the Web server:
Allow-Remote-Addr-Change = 0 # not allowed (default and
# old behaviour)
Allow-Remote-Addr-Change = 1 # Remote Addr can change
# if SessId is in cookie.
Allow-Remote-Addr-Change = 2 # Remote Addr can change
# with no checking.
This option can be set at the individual profile level:
~openmail/omhmtl/<Profile_Name>/profile
or for all web profiles:
~openmail/omhtml/config
The individual profile setting (if set) will take
precedence.
An Allow-Remote-Addr-Change setting of 1 is recommended to
overcome any premature SESSION EXPIRED problems - this will
work if the web browser is using cookies to provide session
id hiding. A setting of 2 means that no checking of
REMOTE_ADDR is done at all and if cookies are not being
used then the session id information is passed within URLs
that are visible on the computer screen and could be used
from another web browser.
CR: JAGae19347 SR: 8606255018
-------------------------------
A new general.cfg option has been added to allow a
specified OpenMail filetype to have a MIME
Content-Disposition of 'inline':
INET_INLINE_FILETYPES=nnnn
where 'nnnn' is an OpenMail filetype. Several filetypes can
be specfied by separating with commas, for example:
INET_INLINE_FILETYPES=2130,2133
will cause both RTF and HTML to be given a
Content-Disposition of 'inline'.
The INET_INLINE_FNAME_ALLOWED=FALSE option should still be
set in general.cfg to suppress the 'filename' attribute.
Additionally the ~openmail/sys/mimeout.str file should be
editted to uncomment the lines for filetypes involved (2130
and 2133 in the example above) if the multipart/alternative
structure is not required.
=================================================
PHSS_26278:
=================================================
CR: JAGad84900 SR: 8606215723
-------------------------------
The incoming Internet Gateway normally truncates all X.400
printable string attributes, of all ORNs within a message,
to the size limits stipulated in the X.400 standard, just
in case the message is sent through the X.400 Gateway. A
new Tweak has been introduced to prevent this truncation :-
INET_NO_TRUNC_X400_ATTS
If set TRUE: The X.400 attributes of an ORN are never
truncated.
If set FALSE: The X.400 attributes of an ORN are truncated
to the limits set by the standard, as usual.
Default: FALSE
OpenMail does not need to be restarted for this option to
take effect.
CR: JAGad95079 SR: 8606226007
-------------------------------
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting (see
JAGac39658).
=================================================
PHSS_25648:
=================================================
CR: JAGad83534 SR: 8606214343
-------------------------------
The behaviour of the redirect rule can be controlled by the
directives EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT specified in the
/var/opt/openmail/omhtml/config file. The values these
directives can take are 0 or 1.
The directive EXECUTE_AA_ON_REDIRECT will force local
delivery to retain a copy of the message in the users
intray, thus allowing the auto-actions to be executed.
The directive DELETE_INTRAY_MSG_ON_REDIRECT will force
deletion of the message from the users intray after it has
been delivered and the auto actions have been executed.
=================================================
PHSS_24876:
=================================================
CR: JAGad75038 SR: 8606205863
-------------------------------
Directory entries that have been affected by the defect
should be rewritten with the correct values.
A way to force the republishing the FreeBusy info.
is for the user to do the following in Outlook:
Tools/Options/Preferences tab
- Calendar Options
- FreeBusy Options
- Set publish <n> months... to 0 and hit OK
- FreeBusy Options
- Set publish <n> months... to what is was
before (eg 2) and hit OK
This will cause the FreeBusy info to be rewritten to the
server.
NOTE: OpenMail must be shutdown before installing
this patch.
----------------------------------------------------------
This patch will need the following minimum disk
space requirements:
/opt/openmail/patch : 71 MB
NOTE: ServiceGuard Installations will need twice
this amount.
----------------------------------------------------------
-----End of Document ID: PHSS_29066------------------------------------------
Document ID: PHSS_29064
Date Loaded: 20030604
Title: s700_800 11.X OpenMail B.06.00 June 03 Periodic Patch
Patch Name: PHSS_29064
Patch Description: s700_800 11.X OpenMail B.06.00 June 03 Periodic Patch
Creation Date: 03/05/14
Post Date: 03/06/04
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-AMEWEB,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-CHSWEB,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-ENGWEB,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-FINWEB,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-FREWEB,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-GERWEB,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-ITAWEB,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-KORWEB,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-PTBWEB,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-SPAWEB,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-SWEWEB,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_29064
Symptoms:
PHSS_29064:
CR: JAGae59759 SR: 8606296148
When an Asian user on GR6 browses a NDN msg using an IMAP
client, the NDN is displayed in English, not in the user's
local language, with the non-delivered recipient name being
corrupted and truncated, as in :-
imaizumi-ma 15=;
and the following error is logged a few times to the
'fatal' log file:-
[OM 16130] Unable to open localised attribute tag file for
interchange character set ISO8859_1.
Additionally, if the user is on a mailnode with TTX
attributes, the Item Browser may go into a loop continually
logging many ERROR [OM 16130]'s. On GR6 this causes the
IMAP client to hang when the msg is viewed and the
mailstore filestore to fill up with work files.
For GR7, IMAP browsing is carried out using the newer Mime
Browser which does not exhibit this problem.
CR: JAGae62810 SR: 8606299316
If an attempt is made to install an OpenMail patch on a
system which does not have the base OpenMail product
installed, an ERROR status is returned in swagent.log. On
an HP-UX 11.11 system, it would be more appropriate to
return an EXCLUDE status.
CR: JAGae69195 SR: 8606306147
An inconsistency has been identified, on GR6 only, in the
code whereby a function is called with a structure
parameter when the function itself is expecting a pointer
to the structure.
This is very likely to cause untoward behaviour,
particularly on LINUX, where it could crash the UAL Remote
Client Interface, with an error like :-
SERIOUS ERROR Remote Client (U/I Access
) [OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 5930;
code = 0. Procedure trace follows:
...
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
-> sfl_OpenSfl
-> im_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_OpenItem
-> im_OpenItem
but could just as well affect other platforms.
CR: JAGae70969 SR: 8606307934
An item has the content line "Content-Type: text/html;
charset=" - i.e. is the character set value is NULL. The
following IMAP command is given.
". UID FETCH 1 (FLAGS)"
The flags are displayed correctly.
The further IMAP command is then given
". UID FETCH 1 (rfc822.size)"
This causes the response "NO some of the requested messages
no longer exist", and the size information is not
displayed. This also happens other requests of header
information.
CR: JAGae70977 SR: 8606307942
A user has a number of corrupt mail items. When the IMAP
command ". UID FETCH n (rfc822.size)" is issued for any one
of these items, the following response is given
"NO some of the requested messages no longer exist".
and so the mail item is not displayed.
However, these items can be displayed using other clients.
The only data displayed is the "subject", but a user is
then able to delete these items from their mail box.
It was also noticed that omscan does not detect these items
as being corrupt.
CR: JAGae70980 SR: 8606307945
When some mail items, containing a folder item, are viewed
from an IMAP client, the content is lost.
The item browser fails to return the requested message
content, and so the IMAP DAEMON responds with
"No some of the requested messages no longer exist"
when an IMAP "UID FETCH (BODY[1.MIME])" command is given.
CR: JAGae70984 SR: 8606307949
After some messages have become corrupt, the UAL
GET_OBJFILES command returns a corrupt object file. When an
attempt is made to create the body structure from the data
in this corrupt file, the IMAP daemon child process hangs.
The following response is given
"NO some of the requested messages no longer exist"
and only the messages up to the point of the corrupt one
are displayed.
CR: JAGae70985 SR: 8606307950
Sometimes the UAL returns no absolute value for delivery
acknowledgements. IMAP uses the absolute value to assign
the UID value, and is assigning a value of 0 in these
cases. Attempting to access an item with a UID value of 0
doesn't work, as the IMAP daemon see this as an invalid
value. So the following response is given
"NO some of the requested messages no longer exist"
and the mail item is not displayed.
As an example, if items 1 and 3 have UID values of 0, then
the IMAP command ". UID FETCH 1:4 (FLAGS)" processes items
2-4, whereas the command ". UID FETCH 1,2,3,4 (FLAGS)"
processes items 2 and 4. This is inconsistent.
The presence of items with 0 UID values can confuse clients
such as Netscape 4.7. This client seems to issue a fetch
command with a UID 2 greater than he actual value in the
above case.
PHSS_28590:
CR: JAGab82932 SR: 8606110229
When an Outlook created msg with embedded image, is sent
over the Internet, the image is no longer visible to a
recipient, on a non-Linux server, using Outlook. Instead,
it is replaced by a BINARY file "Untitled Attachment" which
is not executable, even if it is first saved as a file with
the correct extension. In fact it is not even in the
correct format for its application, Paintbox.
Also occurs with embedded .XLS spreadsheets and probably
any other type of file that can be embedded in the main msg
body. It does not seem to happen with embedded Word .DOCs,
probably because RTF is capable of representing these
entirely.
Problem does not appear when same msg is sent internally to
OM recipient over OpenMail SMINTFC gateway or sent over the
Internet to a recipient on a Linux server; the embedded
image is visible just like it was sent out from Outlook.
CR: JAGae49796 SR: 8606285855
When OpenMail is installed for the first time on a RedHat
system, file OMDATADIR/omhtml/portal.cfg may not be
created. In this case, the ICE client will fail with a
'System Error : [SYS 2] No such file or directory' message.
Some WAP and PAW configuration files may also not be
created (for example, profile.std should be copied to
profile).
CR: JAGae50393 SR: 8606286454
The ~/sys/mime.types has no filetype for *.vsd or visio.
The same problem for the AutoCAD file (.dwg).
CR: JAGae52304 SR: 8606288373
UAL PUT_SYNC_CHANGES command processes an action file which
is passed to it. If this action file contains records which
are larger than 4096 byes, then the remote client interface
may become corrupted.
A typical symptom of this corruption is that the rci hangs
and fails to return a reply.
CR: JAGae52624 SR: 8606288693
There are some missing quotes in the OpenMail patch
checkinstall scripts. All instances of the problem involve
calls to awk imbedded in a backtick execution, such as
`echo "$FSET_SIZES" | awk ' ... ... `
The shell expects the single quote after awk to be closed
before the backtick is closed. At the moment, the closing
backtick appears to end the awk sequence, so the scripts
execute properly. But the scripts do need to be repaired in
case the behaviour of the shell changes.
CR: JAGae53719 SR: 8606289790
The Item Browser goes into a loop on any message containing
a MIME body part with two (or more) non-consecutive MIME
Content-Disposition Headers.
This construct appears to be used by some emailers for
embedding graphics in the main body of the message. However
such constructs are at the very least ambiguous, and most
probably invalid. It is open to individual Browsers on how
they handle it, if at all.
On GR6 this causes any IMAP browser to hang when the msg is
viewed and the mailstore filestore to fill up with work
files.
For GR7, IMAP browsing is carried out using the newer Mime
Browser which does not exhibit this problem.
PHSS_28155:
CR: JAGad93625 SR: 8606224537
There is no mechanism within omshut to remove ice.user
sessions. This could cause problems for any process which
requires all OpenMail processes to have terminated before
continuing.
CR: JAGae37593 SR: 8606273505
The incoming Internet Gateway, on receiving a msg with a
MIME part with a non-ASCII filename, does not recognise the
filename. This happens while it is working out the mapping,
given in mime.types, from MIME contents-types to OM
filetypes.
The true filename is not lost, as it shows correctly in the
stored msg by all the browsers; it is just not used in the
filetype mapping, resulting in the MIME part being
incorrectly mapped to be BINARY filetype.
It works OK when the filename is in plain ASCII.
CR: JAGae41797 SR: 8606277728
A message coming into OpenMail via the Internet gateway
causes a segmentation violation and is put on the delayed
queue to be retried later and to fail again. Error in log:
SERIOUS ERROR Internet Mail (Incoming )
09.10.02 06:55:09
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 17922
Procedure trace follows:
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
<- ux_InParseCommandLine
-> GetMailText
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
<- ux_InParseCommandLine
-> GetMailText
<- GetMailText
-> StripCrNl
<- StripCrNl
-> ux_InParseCommandLine
CR: JAGae41856 SR: 8606277792
After reading and processing incoming Bulletin Board
messages, the BB Server waits unnecessarily and
inconsistently before exporting the resultant
synchronization requests to other servers, in 50% of cases
depending on the whether an even number of messages were
just read.
By default, this delay could be up to 1 hour.
CR: JAGae42370 SR: 8606278311
The incoming Internet gateway (unix.in) fails to decode the
valid WINMAIL.DAT attachment (TNEF) of some messages. The
TNEF is valid and should be converted at the Internet
gateway into MAPI properties.
These messages cause a warning to be logged:
WARNING Internet Mail (Incoming ) 09.06.02 09:07:45
[OM.UX 1546] MAPI property within TNEF attachment is too
big. The TNEF attachment may be corrupt.
The WINMAIL.DAT attachment is retained and converted into a
text attachment. This attachment seems to cause some
clients problems when browsing the message (e.g.
Netscape/IMAP hangs).
This problem only occurs when the general.cfg tweak
UX_PRE_5_20_COMPATIBILITY_MODE=FALSE is set (this is the
default on GR7).
CR: JAGae42811 SR: 8606278755
Some messages that originate from an OpenMail system cannot
be moved from a PST to an Exchange server. They produce a
"Can't move the items. The item could not be moved. It was
either already moved or deleted, or access was denied."
error.
CR: JAGae43470 SR: 8606279417
A forwarded DL, containing long lines, probably resulting
from comments in addresses and/or encoded non-ASCII char
sets, which is forwarded on its own via the Internet
Gateway, is corrupted at the recipient, with lines being
truncated in the middle of addresses.
The problem does not occur to the DL when the complete
message is forwarded.
CR: JAGae44306 SR: 8606280333
When attachments with common PC file extensions,
like .PDF, .PS, .FM, .MPP, .ZIP are received from the
outside Internet with unexpected, but not incorrect, MIME
Contents Types, they are not recognised as being their
correct filetype.
The are treated instead as the BINARY filetype and
therefore cannot always be selected from PC OMGUI and
associated with their corresponding PC application, e.g.
.PDF files are not always automatically passed on to Adobe
Acrobat.
CR: JAGae48115 SR: 8606284168
Cannot reply to the message which came from the local OM
user who has long user name (probably with TTX fields).
The reply generated contains a truncated name for the
original sender which cannot be mailed (address not
routable) or cannot be delivered (name not known).
PHSS_27678:
CR: JAGad71050 SR: 8606201876
Symptoms: Downloaded quoted-printable .CSV (Comma Separated
Values) file attachment to PC is missing carriage returns.
Despite it being perfectly acceptable to MS Excel.
Problem: OM does not know that .CSV files are really text
files and therefore they need their newlines uprated to
CRLF on PCs.
CR: JAGae07887 SR: 8606238864
omcpinu with the '-e' option fails to correctly merge
folders whose names contain multibyte data.
CR: JAGae18540 SR: 8606254208
The check_relay feature of sendmail does not work when
sendmail is invoked from omredirtcp.
CR: JAGae24659 SR: 8606260336
The "man" page for omupdtis etc. gives the directory path
containing the Item Structure Server database (default or
otherwise) as "OMDATADIR/dir/../is/" in 3 places.
Although this is correct, it is not clear to the reader
that the UNIX directory convention of "../" is being used
here to mean "the parent of".
This is confusing and prone to be misinterpreted.
CR: JAGae24724 SR: 8606260401
OpenMail does not support sendmail on AIX 5.1L. The
sendmail.cf file is in a different location compared with
AIX 4.x. In addition, omrc needs to check file permissions
when sendmail versions later than 8.9 are in use.
CR: JAGae24726 SR: 8606260403
omsendin does not recognize the sendmail.cf versions later
than 8.9 included with some releases of Solaris and AIX.
This does not occur with OpenMail B.07 or with OpenMail
B.06 on RedHat Linux.
CR: JAGae26104 SR: 8606261785
The autotests imap_JAGae15283.u and imap_JAGae12028.u fail
about 80% of the time on Linux because they run "StartSvc
imap" immediately after "StopSvc imap" and the imap daemon
fails to start.
On HPUX11, running omoff -s imap followed by omon -s imap,
several times in quick succession causes the state of the
imap to fail to start properly.
CR: JAGae27170 SR: 8606262840
When Bulletin Board changes are being synchronised - if a
basic item (i.e. message content rather than a whole
message) is added to a Bulletin Board and then deleted in
the same email client session the ADD will be synchronised
but the DELETE will not be.
CR: JAGae31209 SR: 8606266965
omredirtcp sometimes cannot be restarted. It either fails
silently or writes a "bind failed: Address already in use"
error message to the syslog.
CR: JAGae32060 SR: 8606267820
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation. (This is another example of the
problem described in JAGad95079.)
CR: JAGae33094 SR: 8606268859
A message with a "Mail from" command containing a
comment-only email address coming into OpenMail via the
Internet gateway causes a message with no originator to be
generated. If this message is routed via the X.400 gateway
it is rejected as an originator is a mandatory field.
CR: JAGae33310 SR: 8606269075
When the outbound Internet gateway processes a message that
contains recipients on both the TNEF and MIME routes the
steering file used may be either the MIME one
(~openmail/sys/mimeout.str) or the TNEF one
(~openmail/sys/tnefout.str) depending on the order of the
recipients. The message should be split in this case and
the appropriate steering file used for each type of
recipient.
CR: JAGae33867 SR: 8606269632
Using PC Admin new PDL members cannot be successfully
added. An OM16095 error is reported:
"Illegal attribute type within compound value."
The PDL member can be added successfully using the backend
OpenMail 'omaddpdln' command.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the omrc command may give incorrect '[OM
10350] Warning: File system is full' messages. The message
does not state which file system is meant to be full.
PHSS_27060:
CR: JAGad38110 SR: 8606168832
The Web Clients create temporary files under /var/tmp which
may have world-writable permissions, and always have
world-readable permissions.
CR: JAGae12028 SR: 8606245558
Using an IMAP client to copy/move a message from a local
folder to an OpenMail folder leaves the new message with
the user running the IMAP session as the message creator
and an incorrect received date.
This is only a problem if a non-IMAP client is subsequently
used to read the message.
CR: JAGae12031 SR: 8606245561
Using the ICE web client to log on to Openmail - as soon as
you select a button or click on something in the Main Menu
you get the logon page again with a SESSION EXPIRED error
message.
CR: JAGae15283 SR: 8606248886
There are 3 problems in B.06.00
1) The IMAP_AUTOMATIC_MDN general.cfg option is not always
being checked. This means that an acknowledgement may be
sent by the server when this option is not set to TRUE and
the client has not generated an acknowledgement.
This usually happens for the first user. See also
JAGac 78827.
2) Disposition notifications generated by Netscape are not
always detected as such. This means that a message appears
in the sending user's intray, rather than being recorded
against the saved copy of the message in the Pending Tray
being updated. See also JAGad 45462.
3) If an item requires an acknowledgement and
IMAP_AUTOMATIC_MDN is set to FALSE (default), then the item
is not marked as read when opened.
CR: JAGae17136 SR: 8606251070
Handling of the SIGCLD (SIGCHLD) interrupt changed at Dec.
2000 to make the code suitable for both SystemV and BSD
unix variants. However this change has caused some problems
now that the death of a child process is not ignored. These
problems include:
1. ual.remote zombie process accumulating.
2. scripts no longer executable from TCL within web client
page templates.
3. omredirtcp not invoking sendmail successfully in some
circumstances.
CR: JAGae19347 SR: 8606255018
It is not possible to configure the Internet gateway to
produce simple inline RTF content without associated
filename information. This filename info. often causes
email clients to treat the RTF as an attachment.
Configuration for this feature is possible when a
multipart/alternative MIME structure is being generated.
However a Content Disposition of 'inline' isn't
configurable for a simple (non-multipart/alternative)
content unless a 'filename' attribute is added as well.
CR: JAGae22300 SR: 8606257997
When the Internet Gateway is configured to use the content
T.61 subject as the MIME 'filename' a long T.61 subject can
cause a Segmentation Violation in unix.out.
CR: JAGae22536 SR: 8606258235
A badly formed RCPT TO: address of the form:
";"dept.acme.com
results in a looping unix.in process.
PHSS_26276:
CR: JAGad84900 SR: 8606215723
The individual X.400 printable string attributes of a mail
address, of all ORNs within a message, are being truncated
to the size limits imposed by the X.400 Standard, by the
incoming Internet Gateway.
This can cause confusing and incomplete addresses in the
ORN, particularly in the fields holding the Internet
address.
CR: JAGad95079 SR: 8606226007
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation.
CR: JAGad97183 SR: 8606228125
When a Service Router rule is set up to REJECT a message
using the RECIPIENT-SERVICE-LEVEL criterion the
non-delivery notification (NDN) generated incorrectly
specifies the NDN reason as "Mailbox exceeds size limit".
The correct text should be:
"The message could not be delivered to the recipient as the
service level for their mailbox doesn't allow that
operation".
CR: JAGad97593 SR: 8606228536
With Portal Access enabled, when a duplicate username is
entered, the ICE Web Client 6.0 user program should display
the Duplicate Usernames page containing a list of
alternative names from which to pick the correct name.
When used with a Web Client 5.10 profile, this list of
alternative names is not displayed and the Duplicate
Usernames page stalls at this point: Please select an
alternative from:
At GR6, the Duplicate Usernames page is not even displayed
at all; the Logon page remains without any feedback that
something is amiss.
CR: JAGae02798 SR: 8606233575
For some IMAP clients (e.g. Outlook Express) the date of
messages in a sub-folder is the date the message was copied
to the folder rather than the date the message was
received.
CR: JAGae06468 SR: 8606237428
omdosur fails with the error message "(OM 24602) Cannot
create file"
CR: JAGae07450 SR: 8606238426
The first mailnode created on a system is not always made
the Primary Mailnode. Shown by absence of '**' in omshowmn
output.
Virtual Licensing assumes that this mailnode to be the
Primary Mailnode, which it needs to refer to.
As a result, Virtual License Server crashes, with
Segmentation Violation, when trying to grant licenses that
have been requested but not yet granted.
May occur during start-up if the request was made while the
system is shut down, or at the time of the request if
system is up.
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.
CR: JAGad95463 SR: 8606226394
This applies to B.06 and B.07 of the Openmail Server. See
also JAGad 94299, against the MAPI Service Providers.
With the outgoing internet tnef gateway configured to
convert rtf to text (tnefout.str), and with the
OMDATADIR/sys/general.cfg option
UXO_NO_RETAIN_IF_CONVERTED=TRUE set,
1) In Outlook/OpenMail begin to create a 'New Message'.
2) Add a Subject, an Exchange users name and some message
text to the body.
3) Save and close the message.
4) Open message; add some more text and send it to the
Exchange user.
5) The Exchange user receives a message with a blank
message body.
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
An address list, such as a TO: field, may be corrupted if
it contains a quote character ("). This occurs because of
the way that sendmail converts the address and OpenMail
subsequently parses it. In the following text, # is used to
represent the <backslash> character.
If an entry has the format #", then sendmail quotes it and
adds an extra <backslash> to the #" sequence.
So us#"er <user.local>, becomes to "us##"er" <user/local>,
OpenMail then splits up the address list using commas as
the separator. If a separator is in a quote, it is ignored.
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 rel