Conference iosg::all-in-1_v30

    Hi,
    
    	today I've played around this problem:
    Transfering a user from one MUPA system to another MUPA system works
    fine, but an important field "FROM_ADDRESS" is missing in the mails.
    
    I've checked all archivefiles for the field on both systems
    (sending/receiving) all are filled in correct.
    
    See details below.
    
    I think that the problem is 100% in TRANSFER_RESTORE function. But this
    I can't influence. If I'm right should I IPMT this bug???
    
    Best regards
    Charly_from_CSC_Vienna_hating_to_report_bugs...
    
    User OFFICE from Node TROJA (V3.0A) to Node VNOTSC (V3.0A)
    
    part of OFFICE1232000004.ARCHIVE;1
    
    !*
    !* ALL-IN-1 V3.0 Transfer File
    !*
    !* Start of main document
    FILENAME                                         OA$SHARE1:ZVDEHV06Z.WPL
                                   TRANSFER$AREA:OFFICE1232000004.ARCHIVE_BODY
    DR                                                NO
    RR                                                NO
    PRIORITY                                          EXPRESS
    FORWARDABLE                                       YES
    TO                                                office @a1 @troja
    SUBJECT                                           test auf die troja
    FROM_ADDRESS                                      EHRLICH@A1@VNOTSC
    FROM_DEPT                                         CSC
    
    The orignal mail on TROJA looks like (SH Show header)
    
    Subject:           test auf die troja
    Title:             test auf die troja
    Sender:            EHRLICH@A1@VNOTSC
    Senders Full Name: Karl Ehrlich
    Senders Tel No:    86630/2581
    
    ---> And after CSN to VNOTSC the mail looks like
    
    Subject:           test auf die troja
    Title:             test auf die troja
    Sender:            
    Senders Full Name: Karl Ehrlich
    Senders Tel No:    86630/2581
    
    See the Senderfield (FROM_ADDRESS) is empty! Terrible if user wants to 
    reply !!!
    
    
    
    
    
    

This problem occurs because FROM_ADDRESS is a protected field -
only certain parts of the filecab code, doing certain operations, are allowed
to modify it.  This is to prevent users changing the FROM_ADDRESS in mail
messages (and hence sending anonymous mail).

The transfer code therefore needs to take special action when writing
FROM_ADDRESS; at the moment (V3.0) it doesn't.  I believe it's fixed in a PFR.

Scott

    Hi Scott,
    
    	...fixed in a PFR. You know who the customer is, it's the CoV.
    They're doing also the FT of the PFR. I hope it's really fixed.
    
    By the way -> CoV transfers the user from MUPA to V2.4 system (no
    TRANSFER_RESTORE function) and then from V2.4 to the other MUPA system.
    This is only a 'wurg' around. They're transfering a lot of users now. 
    
    Your solution is hardcoded, if I'm right. So, If I'll escalate this through 
    normal channels may we get hold of the fix (I think about an ICF)
    
    Scott, what's your idea?
    
    Best regards and have a nice weekend!
    Charly

>> If I'll escalate this through normal channels may we get hold of the fix
>> (I think about an ICF)

As V3.1 is now in EFT, I don't know how much longer the support group will
be making patches for V3.0.  You'll have to ask them directly, as you say,
through the "normal channels" (whatever they are this week!)

Scott

    Good morning Scott,
    
    	yes, you're right. It's solved in the PFR. We've tested this.
    But we need the solution in the actual version. So I'll IPMT this
    today through normal channels.
    
    Happy Easter!
    
    Charly