Conference rocks::dec_edi

3108.0. "cannot recieve EDI files" by HGOSPS::MASCOTTANG () Fri Apr 25 1997 14:17

    My customer created an EDI connect-id profile, and then he sent mail to
his external users, his users can recieve his mails, but when his users reply
his mail, he cannot receive it on EDI. He checked that the reply mail was
recorded and was posted on MRX.log files, but he could not find the mail 
at EDI. Would any one has experience on it ?
 
    Customer keeps the NBS, X409 and MRX log files. I copied these files on 
HGOSPS decnet directory, My customer mail address in X400 format is:
c=HK/admd=ATTMAIL/prmd=MTLCS1/o=MTL/s=DECEDI

$dir hgosps""::*.nbs_lis,*.x409,mrx.log   
 
Directory HGOSPS""::DSA4:[FAL$SERVER]

MANUAL_REPLY_20855.NBS_LIS;1            OUTBOUND_20848.NBS_LIS;1
OUTBOUND_DR_20849.NBS_LIS;1             MANUAL_REPLY_20855.X409;1
OUTBOUND_20848.X409;1                   OUTBOUND_DR_20849.X409;1     
MRX.LOG;4833

file : OUTBOUND_20848.X409;1 - this file is in X400 file format which is 
                               my customer to send an EDI file to his external 
                               users.
file : OUTBOUND_DR_20849.X409;1 - this file is a confirmation mail that comes
                                  from EDI. My customer can read this reply on
                                  EDI.
file : MANUAL_REPLY_20855.X409;1 - His end users replied to EDI mails, but
                                   my customer cannot receive the replied mail 
                                   on EDI.  
                               
     I checked his MRX.log files, it seems the mail can deliver to X400 layers,
but I don't know why customer cannot read this file on EDI. Because I don't
know EDI, therefore I cannot judge what is problem on it ? Would anyone has
expereince on it ? Any advice should be appreciated.

     My customer is running DECNET/OSI V5.6B, VMS V5.5-2, MRX V2.3 with ECO 4, 
MR and MRGARE V3.3A.

    

    Hi
    
    check in @DECEDI$LOOK.
    the connection-ID information is case sensitive.
    
    If the message reaches DECEDI but does not match a conn-id, an error
    should be logged in the logfile.
    
    GJ