Conference forty2::mailbus_400

 Hi all,

 now it works with one problem left.
 we use Mailworks V 1.3A-3 VMS as Mailserver.
 we use "mts transfer protocol"
 we use "xmr$no_p1extensions  1"
 content type is {1 3 12 2 1011 5 5 0 1 22 1}
 eits are {1 3 12 2 1011 5 5 1 1 11}, {2 6 3 4 5}, {2 6 3 4 2},
               {1 3 12 2 1011 5 5 2 0 15}

 Attachments can be send and recognized correctly on both sides, but

 the Softswitch (MS Mail as agent) cannot reply or even use the X.400
 address the Mailbus sends. For example

 Originator address is
 "c=de;a=dbp;p=dbmail;o=dasa;ou1=lm; s=neumann;g=bernd"

 reply to this address only works if the administrator of MS Mail (?)
 adds a DDA field in the MS Mail (?) directory:

 DDA	Common | bernd neumann

 which is in fact the common name, dispite of the fact that the Softswitch
 admin said "I can only use "S=...;G=...", my system cannot use common name

 Without this DDA entry, a Routing Error (number 513) occurs.

 Does anyone has a hint ?

 reagrds, Erich

Hi Erich,

Very strange. I think you need to get the exact story from the Lotus support 
people.

I don't think it's possible to get the Digital products to support common name 
in this case. Mailworks is probably supplying the 1984 O/R address terms to 
Message Router, and XMR and the MTA will just pass these through without doing 
any lookups. 

Perhaps it's possible to add the DDA to the Mailworks addresses - do they come 
from DDS? I don't know enough about how Mailworks constructs its Originator 
addresses - maybe something's possible in this area.

grahame

 I made a typo in the "Personal Name" attribute

 best regards, Erich

 Hi all,

 after a little bit of testing the customer discovered that Wordperfect   
documents (V 5.*) cannot be transfered.
 WP docs attached to a mail arrive on both sides as "attach.dat"

 I expected the entries in the ext_def_boodyparts.ncl and the XMR
 default installation schould be enough to handle Wordperfect docs.
  
 What is missing ??

 regards, Erich

Hi Erich,

Things are beginning to get a little vague in this Note - perhaps you could 
describe the part of tyhe config which is causing a problem?

I assume you're sending WordPerfect to and from ALL-IN-1? Do you have the 
correct translation rule in the xmr bodypart table? Check the comments in 
the table, and make sure you've got the correct entry set up (or perhaps just 
try changing it and see if it helps?)

grahame

 Hi Grahame, 
 
 we use Mailworks/VMS as agent and TeamLinks V 2.5 Clients and
 Wordperfect V 5.* for Windows. 
 Wordperfect/ALL-IN-1 is also available ands was also used for testing.
 Target is Mailworks/VMS.
 The customer changed the oder of Group1 and Group2 in the XMR-table
 with no success, the wordperfect attachment isn't recognized .
 I found the X.400 Bodypart object identifier, described in the manual 

	1 3 12 2 1011 5 1 111 which is WP4 and
	1 3 12 2 1011 5 1 112 which is WP5

 also in the MTA_ext_def_bodyparts.ncl (on my system, MTA V 2.0 UNIX)
 I believe that the info is present and correct but not used. Maybe the agent
or Teamlinks use the wrong tagging ?

 regards, Erich

Hi Erich,

Sorry, I don't know what can cause this to happen. You'll probably get better 
help in the Teamlinks conference on Abbott.

Otherwise you could experiment with capturing the message at various parts of 
its journey, and see if you can see where the WP information is getting lost. 
In X.400 it should be an Externally Defined BP with the correct OID; in MR it 
should be (probably!) a DECBODY7 with the tag (format) which is recognised by 
MW and ALL-IN-1 and Teamlinks.

Cheers,

grahame

    As .17 says, make sure it is being encoded as a decbody7 with 
    appropriate imagproc/imagtyp values. Don't encode it as a decbody1,
    which is the bodypart the old ALL-IN-1/Wordperfect integration used.
    
    Dave