Title: | DEC/EDI |
Notice: | DEC/EDI V2.1 - see note 2002 |
Moderator: | METSYS::BABER |
Created: | Wed Jun 06 1990 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3150 |
Total number of notes: | 13466 |
Between considerations between security aspects regarding the use of X400 fields defined in the PEDI gateway table (or connect-id's table - see note 1621.x) and a real need for a customer RALSTON/EVEREADY in its use of X400/PEDI support thru the VAN Allegro WE NEED: - more flexibility and the possibility to define in the SURNAME field (by extension in all the fields of the common name) a '*' entry to allow the partners to address DEC/EDI with 2 different surnames (ther's a restriction for the sender today to address RALSTON (2 entities) thru 2 DIFFERENT X400 OR adresses. here: P=RESE;O=RESE;S=DECEDI and P=RESE;O=RESE;S=DECEDI1 for instance _ i never understood why an user agent (DECEDI here) should have a mapping scheme of only one OR adrress in the X400 comms field; that as a product perspective restricts its use Jean-marie
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3120.1 | IJSAPL::DEWIJK | GJ from the Dutchlands | Thu May 01 1997 15:40 | 18 | |
Hi Jean-Marie, There are two different things. The PEDI parameters and MB400 routing. - MAILbus 400 allows you to deliver all kinds of addressed messages to the DECEDI useragent, It's just a matter of setting up the routing information properly. DECEDI does not check on the receipient of the incoming message against the PEDI parameters. So MB400 can be setup to rout the two or more X400 addresses to DECEDI. - The PEDI parameters are used on outbound messages. The originator field is used for that. It means that messages sent from your environment always have the same originator. ( the PEDI parameters ) Hope this helps GJ |