Conference iosg::all-in-1_v30

313.0. "Different NBS encodings ??" by JOCKEY::MARSHALLJ (Glad that the devil is red ......) Tue Mar 24 1992 15:57

Hi,

A customer has a custom-written UA for MAILbus and have just being testing the 
receipt of mail from a system running V3.0 (BL122).  This has uncovered some 
problems which are outlined below.

During interoperability testing (V2.n <--> V3.0) these problems aren't seen 
for reasons explained below.  However, as the UA manipulates the NBS files, 
these will cause major problems.


    1.      The FROM field contains the ALL-IN-1 profile name with
                'PAPER MAIL' appended on the end.
             
                e.g.  'BRADBROOKAPAPER MAIL'

                ALL-IN-1 displays the 'SENDER' field from the envelope
                not the 'FROM' in the content so the message header looks
                correct. Therefore curruption is not seen except in
                the NBS dump.

        2.      The message class field contains '!AS'  This is usually the
                result of a system service call to FAO with a null
                parameter in the place of the string to be inserted.

                ALL-IN-1 does not show this field anywhere. Only the NBS
                dump show this. All other versions of ALL-IN-1 set this
                field to a description of the user agent

                i.e.    'All-In-1 V2.3 BL8-4 Rev. ACC 20-Dec-1988'



        3.      WPSPLUS attachments encoded in Message Router format have
                various fields, one of which is the IMAGTY field (usually
                contains the Document Handling). This field is usually only
                15 spaces from other versions of ALL-IN-1, however, from
                version 3 it is 1024 spaces!!!!

                I'm sure this field should not be this long. What is the
                point of sending 1k of spaces for every attachment.

                The IMAGTY field of the WPSPLUS part of the E-mail is OK.
                only attachments are corrupted.


Any help would be immensely appreciatted !!

John.

    John,
    
    1. is easy because you haven't got DDS set-up properly.
       if at EM you do <GET OA$DDS_AREA_ROUTE you'll see it thinks
       your routing address is PAPERMAIL and not @A1@MBX.
    
       You need to rebuild your UA object and Subscribers as described in
       the Mail MAnagement Guide.
    
    2. !AS - you're right this appears to be an Introduced bug in v3.0
       and looks like it could cause some interworking problems. Hopefully
       a mail developer will stop by and assure that is fixed in a PFR
       (I'm running BL123 so no "fixed on BL123" answers please)
       Can you log a QAR?
    
    3. I always practice 'safe-editing' and avoid WPS-PLUS so i'll leave
       this to someone else.
    
    Regards,
    
    Andrew.D.Wicks

    Hi,
    
    2. Yes, well spotted.  It will definitely be fixed in a PFR!
    
    3. Well, my WPSPLUS attachments (on BL123) seem to have 15 spaces in
       the IMAGTY field. I doubt if anything changed between BL122 and BL123.
       Anyone else with a BL122 like to check it?
    
    Andy