Conference abbott::mailworks-vms

1552.0. "wrong title" by WOODY::FABBRI () Mon Mar 10 1997 09:24

	Hello,


A customer has a strange problem.


OpenVMS/AXP 6.2
DECMailworks V1.3A-3

4 users receive two different messages sended by a procedure.

2 of them receive the messages correctly and the two others receive them but
with the same title.

In fact with Teamlinks or with DMW vt, when they do DMW>dir , they see 2
messages with the same title


 Drawer: COURRIER        Folder: COURRIER

13 COSSIA MURIELLE (gg2  5-NOV-1996  DRM 1189/ITA 030
14 COSSIA MURIELLE (gg2  5-NOV-1996  DRM 1189/ITA 030


If we do a show header, the subject is different


DMW> show header 13

    #13                                                                COURRIER
 COSSIA MURIELLE (gg20263@AM@EXPCEN)      opened          5-NOV-1996 17:09:18.64
 Message         3 blocks
 From : COSSIA MURIELLE (gg20263@AM@EXPCEN)
 From Telephone:                      From Location:
 Subject : DRM 853/ITA 003
 This Recipient Read Receipt    : No          This Recipient Type : To
 This Recipient Reply Requested : No          Reply by :

 Priority    : First_Class              Sensitivity : Company_Confidential
 Importance  : Medium                   Expiry Date :

 IP MessageID  : 2017091705111996/A12093/CVAPWK/11AB2C491000
 UA Content ID : 11AB2C491000
 Message ID    : 2017091705111996/A12093/CVAPWK
 In Reply To   :
 Deliver Date  :  5-NOV-1996 17:09:18.64  Posted Date :  5-NOV-1996 17:09:17.20

 Originator requested read Receipt :         Full
 Originator requested delivery notification: Basic

-------------------------------------------------------------------------------
DMW> show header 14

    #14                                                                COURRIER
 COSSIA MURIELLE (gg20263@AM@EXPCEN)      opened          5-NOV-1996 17:14:52.24
 Message         3 blocks
 From : COSSIA MURIELLE (gg20263@AM@EXPCEN)
 From Telephone:                      From Location:
 Subject : DRM 1189/ITA 030
 This Recipient Read Receipt    : No          This Recipient Type : To
 This Recipient Reply Requested : No          Reply by :

 Priority    : First_Class              Sensitivity : Company_Confidential
 Importance  : Medium                   Expiry Date :

 IP MessageID  : 8650141705111996/A12107/CVAPWK/11AB2C4E3200
 UA Content ID : 11AB2C4E3200
 Message ID    : 8650141705111996/A12107/CVAPWK
 In Reply To   :
 Deliver Date  :  5-NOV-1996 17:14:52.24  Posted Date :  5-NOV-1996 17:14:50.86

 Originator requested read Receipt :         Full
 Originator requested delivery notification: Basic
                                                
.

I suppose that when we do a DIR we look in the .X4M and when we do a SHOW
HEADER, we look in the .X4H. So why is the info in the X4M bad ??
Is it possible to regenerate the .X4M ?


Does somebody have an idea ??


Michel

    Is the Automated Procedure that you mention running under just one
    account?  And can this procedure be run multiple times simultaneously?
    
    To put it another way - is there one account creating/sending these 
    messages at the same time?
              
    Arfon.
    
    

	Hello Arfon,

Is the Automated Procedure that you mention running under just one account? YES 
And can this procedure be run multiple times simultaneously? NO

The customer have done some more tests.

When he send messages manually using Teamlinks 2.1 or 2.5 (not using the
automated procedure), to the 4 addresses (VT users), 2 of them have the problem.
This appends not all the time.
So it seems that the problem is not coming from the procedure.
Also the 4 addresses are in typed in the to: field not in the cc: field

Any idea ??

Thanks 

Michel

    When using the VT component, SHOW HEADER and READ commands get the
    subject from the actual mail header, (xxxxxxxx.X4H,) file; the
    DIRECTORY command get the subject from a value that is stored in the
    file cabinet.  The value that is stored in the file cabinet may be
    modified; (MODIFY HEADER/TITLE=)
    
    >4 users receive two different messages sended by a procedure.
    >
    >2 of them receive the messages correctly and the two others receive them but
    >with the same title.
      I would recommend capturing the NBS file of the message and seeing
      what the value is as the message comes into the system.
    $ x4manager
    stop
    edit
    set internal_options leave_nbs
    set delivery_threads 1
    *exit*
    start
    $! reproduce the problem; check the nbs file...
    
    
    -diana